No matter how attractive it seems to just dive in and get started, it still makes sense sometimes to pause first and make sure it is the right thing to do.
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.
At the Agile2010 conference in Orlando the International Institute for Business Analysis (IIBA) released a draft of the Agile Extension to the Business Analysis Body of Knowledge (BABOK) — introducing how business analysis on agile projects changes from traditional/waterfall approaches.
How can we be sure that the projects and activities in which we’re involved actually grow our organisations in the direction they need. The incremental adjustments towards an organisation’s goals are termed business value — and in order to understand this, how we can plan to improve it, and measure that we have — we must first define it.
This article reviews a conversation on business value, and ends with a recommended definition that covers most scenarios.
Show your support of the agile manifesto by becoming a signatory. I did (#6671) and so can you too, it’s easy … read on.