In October 2014 I shared how I would start work on the second edition of Agile Project Management in easy steps. The last few months have been hectic, with my MBA studies, and starting a new job; but finally, last week, we got the final edits completed and the manuscript files have been handed over to the publishers. We’re just waiting for them to finish proofreading and giving a green light before we can announce the publication date, but it looks certain to be in May 2015.
When we start out on a venture, of any kind, we hope things will run smoothly, we expect the ‘happy path’ / ‘sunny day’ scenario to be true. In designing our software, though, we know that we need to allow for alternate paths and exceptions. In the same way, when thinking about our projects, we should expect to be hit from left-field with surprises, and have ways of coping with those.
This talk, which followed my article ‘Bringing sexy back to governance‘, was presented at the 2012 BA Development Day conference, and covers what we mean by governance, what the fifty shades are, and what we can all do about it – in short, this is a call to action for lean governance.
As I have worked on the ‘Agile Extension to the Business Analysis Body of Knowledge‘ over the last year, I have repeatedly come across the assertion–by many agile practitioners–that we no longer need gate meetings on projects. From my experience in leading project governance this confused and concerned me, so I have looked into this and believe I have discovered why this perception has arisen, and more importantly have concluded that gates and governance are vital and need defending.