I'd like to share my view on this subject. Trisha started the topic with"IT workers need to think more broadly about how IT can work for their businesses"
which is very true by any means, and then we moved to direction of business skills, which is not necessarily direct implication of the statement above.
I think we as IT community should just
think broadly about how IT can work for their business. That actually doesn't necessarily means big upfront study of business skills. My framework for developers (as this term understood in Scrum):
1. Present the following http://alistair.cockburn.us/User+Manifes
to business and check whether this is what they need. Note, that this is first step from our side, this could be already a huge difference in the org you work.
2. Treat this contract as asset: if you suck in it, do it more. That will naturally lead to increase of knowledge
3. The question of how
to do it more I'll leave open for now.
I know many people from this list are also subscribed to CTO list so this actually could be a good topic for CTO meetup. There's though one thing that concerns me: knowledge
about how business work, business needs, best usage of IT in it, domain knowledge vs business skills.
IMHO those two different things just because they require different level of investment and commitment to get. But then you can ask whether knowledge without skills really worth anything?
On 11 October[masked]:09, Richard Conroy <[address removed]>
The article was interesting, and the quotes were solid, but the article was two-tone. I don't think the article was written as well as the quotes it cites.
I also think the articles basis, i.e. the stereotypical IT person who has no interest in the business at large outside of technical domains, is a fictional construct.
A better explanation is that silo-ing your IT department, for cost and change control reasons, creates conflicts of interest between satisfying the needs of end users and obeying the instructions that come down form on high. Also the vast proportion of the work done in IT is non-functional, and the non-functional element is proportionally higher the larger your IT infrastructure and the more consolidated it is.
This message was sent by Richard Conroy ([address removed]) from LJC - London Java Community.
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
To learn more about Richard Conroy, visit his/her member profile