This document discusses Agile vs Waterfall methodologies and different levels of planning in Agile projects. It notes that while Agile stresses iterative cycles over upfront planning, teams do still plan by creating release plans, iteration plans, daily plans, and maintaining backlogs. The document includes a case study example of an automated publishing project completed over 14 sprints with planning at the sprint, daily, and backlog levels.

1. {
Pittsburgh PMI – Duquesne PMA
Joe DiFalco
PMP, PMI-ACP, CSPO, Systems Engineer
Profile: CVShout.com/joedifalco
Resources:www.jdifalco.com(Resourcestab)
Contact: joe@jdifalco.com
Dispelling an Agile myth…
yes, Agile teams do plan
Tuesday, April 8, 2014

2. Agile VS Waterfall
What is Agile?
• Framework for managing projects
• Stresses iterative cycles
• Not better or worse than other (Waterfall)
• Not one size fits all

3. Agile VS Waterfall
Waterfall
• Planning up front
• Design up front
• Cost of change
• Feedback loop

4. Agile VS Waterfall
Agile
• Continuous planning
• Continuous design
• Cost of change
• Feedback loop

5. Six Levels of Planning
Team
Focus

6. Release Plan
Automated Publishing
Features
• Select from a list of Pubs
• Manually configure
• Format exactly
• Publish
Stories – Select
• User tab for selecting
• Search by Pub ID
• Sort by Name or ID
• Compound sort

7. Iteration Plan
Automated Publishing
Story
• User Tab for Selecting
Tasks
• User Interface design
• Database query
• Table of selections

8. Daily Plan
Automated Publishing
Three questions:
1. What did you finish
2. What will you finish today
3. What would stop you from finishing?

9. Plan – YES!
Case Study
• Benefits of short delivery cycles
• Plan? …Yes, plan often. Follow the plan? …Not always

10. Agile Methodology – Case Study
Sprint
Backlog
2-4 weeks
Daily
Review
Stakeholders
Retrospective
Project
Funding
$300M market
Automated publishing
100 days
Sprint 1
• Select Publication
Product
Backlog
Value or Risk
Product
Backlog
Value or Risk

11. Agile Methodology – Case Study
Sprint
Backlog
2-4 weeks
Daily
Review
Stakeholders
Retrospective
Project
Funding
$300M market
Automated publishing
100 days
Sprint 2
• Configure Manually
Product
Backlog
Value or Risk

12. Agile Methodology – Case Study
Sprint
Backlog
2-4 weeks
Daily
Review
Stakeholders
Retrospective
Project
Funding
$300M market
Automated publishing
100 days
Sprint 3-14
• Configure automatically
• Format closely
• Assemble
Value or Risk
Product
Backlog

13. Pittsburgh PMI – Duquesne PMA
Dispelling an Agile myth…
yes, Agile teams do plan
Tuesday, April 8, 2014

14. Pittsburgh PMI – Duquesne PMA
Dispelling an Agile myth…
yes, Agile teams do plan
Tuesday, April 8, 2014
Joe DiFalco
Profile: CVShout.com/joedifalco
Resources:www.jdifalco.com(Resourcestab)
Contact: joe@jdifalco.com