Business Analysis: The Agile Approach

In years past, the business analysis discipline has been largely associated with the traditional project management (waterfall) approach, whereby the needs of the customer where gleaned by the business analyst well in advance of solution design and development. Traditional (waterfall) approaches are predicated on defining everything up front, with the mindset that the customer can definitively know all their needs and wants (i.e. scope) from the start, and that those requirements will not change during the project implementation. Of course, the world does not remain fixed while a project team is busy; the business needs of the customer can oftentimes vary. Traditional (waterfall) approaches can be considered “plan-driven”, whereas agile approaches are looked at as a “change-driven” approach.

Plan Driven

This approach to analyzing & delivering business requirements is driven by the need for predictability and delivery according to plan. It is effective in cases where the outcomes of a project can be perfectly articulated, requirements can be fully defined and remains fixed during the project, and project execution has to be managed as one delivery rather than incrementally.

Change Driven

This approach is driven by the need for adaptability and delivery according to business value. It is effective in cases where outcomes are not explicitly articulated up front, there are changing customer preferences, and project execution is more focused on time-to-market.

On projects that follow the “change-driven” approach, there is far more emphasis for the business analyst to value:

• Individuals and interaction over process and tools - business analysis activities occur througout the life of the project
• Working software over comprehensive documentation – focus is on a working, viable solution
• Customer collaboration over contract negotiation – the relationship with the customer is on collaboration and insight, not sign-offs between phases
• Responding to change over following a plan – gathering feedback on deliverables earlier so as to apply that feedback to later releases