In an agile world do we still need requirements? How do requirements change in a world of agile development methods? What skills and tools do business analysts need to thrive in this space?
Agile methodologies have gained a lot of traction in recent years. Better risk mitigation and increased visibility into development have converted many waterfall aficionados. Unfortunately, many agile pundits have singled out requirements as the source of bloat and inflexibility in the software development life-cycle, and some recommend not writing requirements at all.
The real goal of project managers, business analysts, developers, and users is project success. How, then, can business analysts work within agile methodologies and help them succeed? What do requirements look like without all of the overhead? What is the right balance between agility and rigidity? This presentation will answer these questions and provide tips and techniques analysts can use to add value in an agile world.
1. Participants will learn specific techniques used to solve common problems with requirements in agile development cycles.
2. Participants will have a better understanding of the benefits and common problems with agile approaches.
3. Participants will leave the session with an understanding of the differences between a traditional requirements approach and agile approaches.
** Eligible for PDUs, CDUs. **
Joy Beatty, VP
Candase Hokanson, Senior Product Manager
FEATURED SPONSOR: International Requirements Engineering Board (IREB)
Getting A Handle On Productivity
API quota exceeded. You can make 500 requests per day.Buy Stamps Online
Tips For Turning “Lessons Learned” Into “Best Practices”
Your Efforts Or Lack Of Will Be Recognized!
Productivity Tools Can Productively Hinder Productivity – And What to Do About It