Agile projects cannot be                                                               successful without                 ...
Upcoming SlideShare
Loading in …5

Agile projects cannot be successful without Business Analysts


Published on

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Agile projects cannot be successful without Business Analysts

  1. 1. Agile projects cannot be successful without business analysts It is a myth that Agile projects are not requirements driven. The Agile Manifesto is all about bringing business and technology closer through creating a co-located single team environment where requirements can be tested with limited overhead. This does not negate the need to wrap the project with structured requirements or the reality that enterprise systems live well beyond the project teams that deploy them. In many instances, we see hastily assembled Agile teams where business stakeholders and developers are expected to immediately and productively start developing systems. This approach didn’t work before business analysts (BAs) and it won’t work now. BAs remain the vital bridge between business and IT stakeholders – able to interpret business requirements and consider how technology enabled solutions can support them. THE BSG (UK) APPROACH BSG advocates that BAs supplement the role of a product owner on an Agile team. This means that BAs continue to have responsibility for structured specification of requirements. BAs are then responsible for clarification and documentation of requirements as part of the design process. Practically, they will be involved in creating and updating the product backlog, burndown chart, highlight reports and requirements documentation (at whatever level of detail is agreed). BENEFITS OF THE BSG (UK) APPROACH • BAs are experts in delivering benefits. Software projects deliver new or improved capability within an organisation. The capability will be part of a broader change, justified by benefits specified within a business case. In order to realise these benefits, there are typically many other considerations around how the software is to be adopted and operationally embedded. This requires consideration outside of the build of the new software. BAs are well positioned to act as the bridging role between the software delivery team and the broader project. • Agile projects still require documentation. BSG’s approach to Agile projects allows for a reasonable level of documentation to be completed in parallel. This ensures that there is an audit trail for improvement, growth and repairs if needed at a later stage. This also allows for the flexibility required by Agile to outline, create, approve and implement changes quickly. • It allows business stakeholders to maintain appropriate focus. Agile projects can be very time demanding. By reducing the documentation overhead on business stakeholders, they can focus time on both their project and, where appropriate, business-as-usual activities. The Agile Manifesto - www.bsgdelivers.comFor more information about our service offering, +44 20 7390 8674please visit our website or contact us Business Systems Group (UK), Registered in England No. 6150570, 230 City Road, London, EC1V2TT