On a waterfall project, the bulk of the value is delivered at the end of the project. On an agile project, value is delivered incrementally through iterative cycles with the highest-value items prioritized, increasing customer satisfaction. Backlogs serve as the mechanism for clarifying priority on projects carried out by agile teams, allowing them to put the customer’s highest priorities first. How can waterfall teams achieve a similar effect?
Many organizations with traditional, or waterfall, teams struggle to transform to Agile. The struggle could happen for many reasons:
First Steps Toward Agility:
Incorporating Agile Practices in a Waterfall Environment
When: Multiple Dates
Fees for KCPMI, Atlanta, and SeminarsWorld vary. Visit pages for details.
Earn: 7 PDUs / SEUs / Contact Hours
Duration: 1 day
Description: Both traditional (Waterfall) methodology and Agile methodology have pros and cons and can be effective ways to structure a project. For teams that are not practicing Agile, there are still Agile practices that can benefit them. Daily standups, retrospectives, and many other key Agile practices and ceremonies can benefit even a Waterfall team.
For many, the most arduous part of transitioning to Agile in a waterfall environment happens at the beginning—in the uncertainty of how to put the initiative into motion. In this course, strategies and best practices to begin incorporating Agile practices are revealed. Real-world experiences working with existing project teams to begin incorporating Agile practices and ceremonies are shared. By initiating practices, teams start to understand Agile principles and mindset and become better prepared to take the next steps on their Agile journey. Specific Agile practices, and how to adapt each one to a traditional environment, are covered.