1. Agile Project Management PMI Metrolina PDD Saturday September 27, 2014 UNCC Uptown Mike Ryan

2. 28/5/2015Copyright: Mike Ryan Objectives What is Agile? What is the Agile Manifesto? What are the Principles of the Agile Manifesto? What is Scrum? What are the Foundations of Scrum? How does Scrum work?

3. 38/5/2015Copyright: Mike Ryan Sticky Notes ( 5 minutes) Meet your tablemates by introducing yourself. yourself. Chat amongst your team. Discuss some questions about Agile that your team would like to have answered before we finish today. Document your questions, one question per Post it note. Each team should read their most compelling question. Display your questions prominently at the front of the room.

4. 48/5/2015Copyright: Mike Ryan How have we done? The Chaos Summary, a 2009 survey by the Standish Group, indicated that only 32% of all projects succeeded: Source: The Standish Group Succeeded ( delivered on time, on budget, with required features and functions ) 32% Challenged ( late, over budget and/or with less than required features and functions ) 44% Failed (cancelled prior to completion or delivered and never used) 24%

5. 58/5/2015Copyright: Mike Ryan What is Agile? Agile software development is a group of software development methods in which requirements and solutions evolve through collaboration between self-organizing, cross functional teams. Source: Wikipedia

6. 68/5/2015Copyright: Mike Ryan Agile Manifesto Source: www.agilemanifesto.org

7. 78/5/2015Copyright: Mike Ryan 1.Customer satisfaction by rapid delivery of useful software 2.Welcome changing requirements, even late in development 3.Working software is delivered frequently (weeks rather than months) 4.Close, daily cooperation between business people and developers 5.Projects are built around motivated individuals, who should be trusted 6.Face-to-face conversation is the best form of communication (co- location) 7.Working software is the principal measure of progress 8.Sustainable development, able to maintain a constant pace 9.Continuous attention to technical excellence and good design 10.Simplicity—the art of maximizing the amount of work not done—is essential 11.Self-organizing teams 12.Regular adaptation to changing circumstances Agile Manifesto Principles Source: www.agilemanifesto.org

8. 88/5/2015Copyright: Mike Ryan 1.Scrum 54% 2.Scrum/XP Hybrid 11% 3.Custom Hybrid 9% 4.Scrumban 7% 5.Kanban 4% Top 5 Agile Methodologies Key Takeaway: The Scrum methodology dominates. Source: Version One State of Agile

9. 98/5/2015Copyright: Mike Ryan Foundations of Scrum TransparencyInspectionAdaptation

10. 108/5/2015Copyright: Mike Ryan Transparency Transparency in Agile means all steps, inputs, and outputs of the development process are visible. An example of transparency would be the burn down chart.

11. 118/5/2015Copyright: Mike Ryan Inspection Inspection provides an opportunity for feedback on the product. A great example of this is the Sprint demo.

12. 128/5/2015Copyright: Mike Ryan Adaptation Adaptation allows for making changes to the processes or procedures. The Sprint Retrospective is a great example of this.

13. 138/5/2015Copyright: Mike Ryan Why Use/Be Agile? Key Takeaway: Agile provides faster speed to market, more readily allows for change, and satisfies the customer. Source: VersionOne State of Agile Survey

14. 148/5/2015Copyright: Mike Ryan The Penny Game Instructions: 1.The game has three runs. 2.The workers job is to flip the pennies he/she receives as fast as he/she can and then pass them on to next station. 3.The Department managers job is record how much time their worker spends from the first to the last coin flipped. 4.The CEO takes total time from the first coin to the last. 4.The CEO takes total time from the first coin to the last.

15. 158/5/2015Copyright: Mike Ryan The Ball Game Instructions: Everyone is part of a team. Each ball must have “air time” Balls cannot be passed to your direct neighbor to your immediate left or right. Each ball must return to the same person who introduced it into the system. Sequence of events: Planning Session (2 minutes): Plan and design your process Provide estimate Iteration 1 (2 minutes) Pass as many balls as possible Perform a retrospective (2 minutes): Review your design and plan looking toward improving Iteration 2 (2 minutes) Pass as many balls as possible

16. 168/5/2015Copyright: Mike Ryan Does Agile Work? Source: 2013 VersionOne State of Agile Survey Key Takeaway: It works Key Takeaway: It can work.

17. 178/5/2015Copyright: Mike Ryan Estimated Plan Driven Value Driven TimeBudget Features Fixed TimeBudgetFeatures Key Takeaway: Value driven approaches such as Agile allow for adjusting the Features (scope), which Plan Driven doesn’t easily allow. Project Management Methodologies

18. 188/5/2015Copyright: Mike Ryan Continual Grooming Key Takeaway: There are iterations at multiple points in the framework. Source: www.mountaingoatsoftware.com Source: www.mountaingoatsoftware.com

19. 198/5/2015Copyright: Mike Ryan The Roadmap Key Takeaway: This is the long term plan for the product and the Product Owner is the steward of the roadmap.

20. 208/5/2015Copyright: Mike Ryan The Backlog Key Takeaway: Stories which have not been completed and have value to the customer. The backlog should be regularly prioritized, groomed and include “acceptance criteria”. If a story is not properly groomed it should not be pulled into sprint.

21. 218/5/2015Copyright: Mike Ryan Sprint Planning Key Takeaway: This is a planning session where you determine what is to be pulled in from the backlog for the next sprint. If the story is not properly groomed it should not be pulled into the sprint.

22. 228/5/2015Copyright: Mike Ryan The Daily Scrum Key Takeaway: This is a 15 minute stand up meeting where you communicate what was done yesterday, what will be done today and any impediments

23. 238/5/2015Copyright: Mike Ryan Build High Value First High Value Low Complexity High Value High Complexity Low Value Low Complexity Low Value High Complexity Complexity V a l u e Key Takeaway: Get the “low hanging fruit” first 12 34

24. 248/5/2015Copyright: Mike Ryan Timeboxing Who remembers “Parkinson’s Law”? Sprints are a way of “timeboxing” and we know that “timeboxing” works.

25. 258/5/2015Copyright: Mike Ryan Burndown Charts Burndown charts are valuable because they graphically tell you how much you are ahead or behind and anyone can understand them. Source: Wikipedia

26. 268/5/2015Copyright: Mike Ryan Cumulative Flow A Cumulative Flow diagram tells you how much is Not Started, Started and Completed Anything else it tells you?

27. 278/5/2015Copyright: Mike Ryan Why do Agile projects fail? Source: Version One State of Agile Survey

28. 288/5/2015Copyright: Mike Ryan Some Pros and Cons of Agile Quicker delivery of valuable functionality Highly flexible Regular prioritization Quicker feedback cycles and bug identification Fewer defects in final product Effective where goals are “ill defined” or evolving Highly interactive and collaborative Hard to predict cost Time consuming Requires “culture change” Requires significant management support Does not provide “instant gratification” Requires reinforcement not to fall back to Waterfall. Documentation may be incomplete + -

29. 298/5/2015Copyright: Mike Ryan Let’s Finish Up Let’s check out those Sticky notes and answer any questions we have not covered.

30. 308/5/2015Copyright: Mike Ryan Contact Information Mike Ryan mikeryan722@hotmail.com 980-267-4509