Being a BA on a BADgile Project
You’ve heard stories from friends and colleagues - their agile project has gone “BADgile,” heading off the tracks while driving people to frustration and don’t know what to do next. Agile was supposed to solve all our problems. So why are delivery, backlog prioritization, and reducing defects so difficult? Even worse, BADgile delivery twisted the Manifesto to say "no documentation or requirements". With shorter delivery cycles, managing requirements as an asset is even more important in Agile than in Waterfall because you don't have time to define everything upfront. Agile Transformations have been going on for a couple of decades, so you would think companies late to the party would learn from best practices or their predecessors’ mistakes. This session will help you:
Learning Objectives
- Learn the real issue Agile was trying to solve
- Recognize the signs of a BADgile project
- Understand how communication can help get your project back on track
To register, please use the link below.
About the Facilitator
Steve is a passionate analyst and BA manager with more than 20 years of experience in improving processes, services, and software, working across all aspects of software development lifecycle, product management, business change and business analysis. He is an IIBA CBAP®, Six Sigma Green Belt and holds a MS in Information Management and Communications.
He was a 2022 IIBA Volunteer of the Year finalist and is the current VP of Education for the IIBA Hartford Chapter.