There is currently a wave sweeping our industry to adopt agile practices for software projects that are time and cost constrained. Businesses want solutions and they want them fast.
Most agile practices are historically developer centric and provide little guidance for the business on how to successfully prepare for an agile project. In addition agile projects, by their nature, require active ongoing participation from the business to be successful. This ongoing participation of key business resources can easily overload already busy operational business teams.
The Business Analyst plays a critical role supporting the Sponsor, Owner and Business Representatives as they attempt to successfully catch the agile wave and then survive the ensuing ride. This presentation will use relevant examples and case studies from recent Equinox software development projects and consulting assignments to highlight the importance of the business analyst on an agile project.
Learning Objectives
- Understand why agile projects welcome changing business requirements
- Explore what constitutes 'appropriate' agile business requirements
- Review how traditional requirements management is impacted by adopting agile practices
|
Pete Tansey
Senior Consultant
Equinox Limited
Pete Tansey is a Senior Consultant with Equinox, and is based in Wellington, New Zealand. Pete has over 25 years experience working with software solutions and has been involved in all areas of the software development lifecycle. In particular, Pete has extensive experience in business analysis, requirements management, and iterative development approaches. He writes and speaks on these topics. Pete is also a certified instructor and plays a key role in Equinox’s training business, Equinox Learning. Pete has taken a lead role in the development of agile consulting services and agile training programmes for Equinox. For the past year Pete has worked with a New Zealand Government organisation leading their adoption of agile approaches.
|
