1. Agile Project Management

2. An Informed Decision It is not a snap decision whether to use an agile approach or not, just like flying or driving somewhere on a trip The approach has to fit the culture, project, etc. at the organization to be successful. 2

3. Scrum According to the Scrum Alliance, Scrum is the leading agile development method for completing projects with a complex, innovative scope of work. (State of Scrum Report)Scrum AllianceState of Scrum Report 3

4. Scrum Ceremonies Sprint planning session Daily Scrum Sprint reviews Sprint retrospectives 4

5. Scrum Framework 5 Information Technology Project Management, Seventh Edition

6. Product Backlog From jazz.net

7. Sprint Planning and Backlog From www.scrumalliance.comwww.scrumalliance.com

8. Product vs. Sprint Backlog From msdn.microsoft.com ItemProduct BacklogSprint Backlog Level of detail Estimation units Document ownership Revised Duration Workbook

9. Burndown Chart

10. Agile, the PMBOK® Guide, and a New Certification The PMBOK® Guide describes best practices for what should be done to manage projects. Agile is a methodology that describes how to manage projects. The Project Management Institute (PMI) recognized the increased interest in Agile, and introduced a new certification in 2011 called Agile Certified Practitioner (ACP). 10

11. Agile Approach: JWD Consulting’s Project Management Intranet Site An agile project team typically uses several iterations or deliveries of software instead of waiting until the end of the project to provide one product. 11

12. Unique Scrum Activities by Process Group

13. Pre-Initiation and Initiation Pre-Initiation and Initiation major tasks  # of releases and functionality by release  Sprints in release  Charter  Stakeholder Register  Kick-off Meetings 13

14. Planning Similar to Traditional Process Groups  Scope Statement and can use a Gantt chart for the entire project schedule; other planning similar (risk, etc.) Differences: 14

15. JWD Intranet Site Project Baseline Gantt Chart Using Scrum Approach 15 3 releases vs. 1 release

16. JWD Product and Sprint Backlogs 16

17. Executing Similarities to Traditional Process Groups  Still produce products, lead people, etc. Differences: Information Technology Project Management, Seventh Edition 17

18. Monitoring and Controlling Similarities to Traditional Process Groups  Still check actual work vs. planned work Differences: Information Technology Project Management, Seventh Edition 18

19. Sprint Board 19

20. Figure 3-7. Burndown Chart Information Technology Project Management, Seventh Edition 20

21. Closing Similarities to Traditional Process Groups  Focus on acceptance of deliverables and reflection Differences : 21

22. Chapter Summary Project Management Process Groups Main activities of each process group mapped to knowledge areas Information technology project management methodologies JWD Consulting – Predictive vs. Agile  Biggest Difference: providing three releases of useable software versus just one 22