4. The Agile Manifesto Process and tools Individuals and interactions Following a plan Responding to change Comprehensive documentation Working software Contract negotiation Customer collaboration over over over over Source: www.agilemanifesto.org Erin Beierwaltes | agileaction.blogspot.com
6. Why Scrum? Delivering the highest business value in the shortest time Working software every two to four weeks Business sets priorities, while teams self-organize for delivery of highest priority features Reprioritization every two to four weeks or option to release It’s better to have 80% 100% done, instead of 100% 80% done. Erin Beierwaltes | agileaction.blogspot.com
7. Requirements Game Get into teams of 2 Choose a Product Manager and a Developer Developers leave the room Product Managers write a “design document” for developers Words ONLY Developers come back in and try to follow written instructions Erin Beierwaltes | agileaction.blogspot.com
9. PMI’s View of Agile “There is no single best way to define an ideal project life cycle.” – PMBOK, p. 20 “The project manager, in collaboration with the project team, is always responsible for determining what processes are appropriate, and the appropriate degree of rigor for each process, for any given project.” – PMBOK, p. 37 www.pmi.org Erin Beierwaltes | agileaction.blogspot.com
11. Fixed Requirements Resources Time Plan Driven ValueDriven Estimated Resources Time Features www.dsdm.org Triple Constraints Erin Beierwaltes | agileaction.blogspot.com
45. The Sprint (Timeboxing) 2 to 4 weeks Time boxed Product Owner does NOT make changes mid sprint Team can request changes to the sprint based on burndown progress Erin Beierwaltes | agileaction.blogspot.com
56. Product Owner Defines the features of the products Decides on the release date and content Prioritizes features Accepts or rejects work results Erin Beierwaltes | agileaction.blogspot.com
57. ScrumMaster Responsible for Scrum values and practices Removes impediments Shields the team from external interferences Facilitates team decisions Erin Beierwaltes | agileaction.blogspot.com
58. Team 5-9 people (typically) Larger projects expand with multiple scrum teams (scrum of scrums) Cross-functional (developers, testers, documentation, ect) Full time membership Self organized Membership only changes between sprints Erin Beierwaltes | agileaction.blogspot.com
80. Product Backlog User Stories As a ____, I want ____, so that ____. Prioritized list of ALL desired work Owned and kept up to date by Product Owner Used during sprint planning Reviewed Reprioritized before the start of every sprint Sized with Story Points (by the team) Erin Beierwaltes | agileaction.blogspot.com
81. Sprint Backlog List of TASKS that make up the required work for each Backlog item in the CURRENT sprint Created and estimated by the TEAM Updated by the TEAM Data for the burndown chart Erin Beierwaltes | agileaction.blogspot.com
83. Release Burndown What happened here? Based on average velocity Velocity = number of story points COMPLETED during the sprint Erin Beierwaltes | agileaction.blogspot.com
84. Burndown Chart What happened here? Erin Beierwaltes | agileaction.blogspot.com
85. Waterfall vs. Scrum Waterfall Requirements Predictive Individuals Sequential Cost of change Agile/Scrum User Stories Empirical Teams Iterative Encouraged Change Philipjeffs.com Erin Beierwaltes | agileaction.blogspot.com
