1. Agile PM Basics Dr. Vijay Kanabar © Boston University - 2012

2. Two Polar Opposites Waterfall – Water trickles down & it only goes away. – Strong managerial control over schedule and cost. Agile – Product, cost & schedule evolve – Periodic delivery based on business value and user input.

3. Which do you value? Old school of thought you will get some wrong. – Individuals and interactions vs. processes and tools – Working software vs. comprehensive documentation – Customer collaboration vs. contract negotiation – Responding to change vs. following a plan

4. Agile Manifesto Supplementing the Manifesto, the Twelve Principles further explicate what it is to be Agile.Twelve Principles Ref:http://www.agilealliance.org/the- alliance/the-agile-manifesto/the-twelve- principles-of-agile-software/http://www.agilealliance.org/the- alliance/the-agile-manifesto/the-twelve- principles-of-agile-software/

5. The Scrum Process Product Owner – Customer e.g., John Henry – Defines current requirements – Creates Product Backlog – List is sorted by functionality that delivers maximum value – Pareto Principle has to be true….so focus on the top 20%. Compare with Waterfall…we will do all! – Nice to have features can drain resources.

6. The Other Actors Team – Called Scrum Team is a group of 5-9 people who self-organize and have joint responsibility for the completed tasks. Project Manager – Scrum Master- the coach for the product management team and works to ensure the realization of the goals of the sprint.

7. Terminology Sprint: A 30-day effort moving the team toward fixed goal. Product Backlog: A constantly prioritized to-do list. Sprint Backlog: A list of the highest prioritized items from the product backlog.

8. Process: Creating a backlog The Product Owner and Team meet in order to discuss the priority and items on the Product Backlog. The Product Backlog, is a prioritized list of what is required for the project and is ranked with regard to importance.

9. Sprint Planning Meeting During the first phase of the meeting, the Product Owner & PM describes to the team the goals of the project and explains the Product Backlog. During the second phase, the Scrum Team will select the items to be completed during the sprint from those with highest priority on the Product Backlog.

10. Create Product Backlog Features Product Backlog

11. Create Schedule Once the items to be worked on have been selected, a potential Sprint schedule is constructed. The items in the Product Backlog are assigned and broken down into individual tasks. Once this occurs, this document is the Sprint Backlog.

12. Sprint vs. Scrum Scrum Sprint Day 1 15 to 30 daily Scrums

13. Sprint The Sprint lasts 15-30 days. During the Sprint, no other tasks are added to the sprint backlog.

14. Scrum The Daily Scrum is a 15 minute stand-up meeting where each member of the team gives a very brief report: What was accomplished since the last Daily Scrum What they hope to accomplish by next meeting Obstacles that have come up. Here, the Scrum Master will make note of issues and attempt to resolve them – after the meeting.

15. Scrum Sprint Scrum BacklogStart Sprint Sprint Review Sprint Finished

16. Sprint Review Sprint Review – once the Sprint ends, everyone gets together in a meeting to share what he or she accomplished during the sprint. The process begins again with a new list of prioritized tasks on the Product Backlog

17. Case Study Online Store (see Agile handout) – See list of features – See mid-course correction

18. Final Comments Role of PM – Has to relinquish control – Teams are totally empowered – X vs. Y Certifications – Workshop – Exam CSM, CSPO, CSD PMI – ACP (Ag

19. Discussions – Identify if you are agile enough. – Which projects lend to agile PM? Which don’t? – What about hybrid for some projects?