2 Comments
In the last few weeks I’ve met with a number of organisations that have reported similar problems in the implementation of Agile. Typical examples include: lack of control over solutions, timescales, cost and risk; teams working as silos; no standard Agile process; and no standard way of monitoring/reporting on work.
I believe that most if not all of these are related to Team in a Room mentality i.e. the assumption that a focused Agile team working with an on-site customer can achieve its objectives in isolation. This approach can and frequently does work, however it can also fail, sometimes spectacularly.
The solution to the issue is, as I have said before, appropriate governance. The good news is that I’m now beginning to sense that there is a recognition of this within the Agile community as it matures. If Agile is to flourish in complex environments, and particularly in Government, then a broad recognition of the need for Governance, and practical success stories will be invaluable.
---
See also:
Today's highly competitive and rapidly changing markets that see the rise and fall of the likes of Nokia and MySpace places business imperatives on companies. In particular, companies need to be innovative, introducing new products, updating others to react to changes in the market (or predicting or even creating these market changes).
Comments
08 Jul 2011 15:04
"Governance" isn't an anything. What are you really suggesting? That might make for a good blog post.
reply11 Jul 2011 11:52
Thanks for your feedback Joseph. You're right, of course. I wrote the blog in response to a rather frustrating discussion in which I was told that standard show-and-tell sessions provide sufficient and control and there's no need for additional governance.
I'll put some blog posts together over the next few weeks detailing how I would approach governance. Hopefully this will be useful.
replyPost new comment