Sprints Sprint planning Sprint execution Copyright 2012 by

Sprint Planning What are we trying to accomplish in sprint planning? • Goal for the sprint • PBI’s aligned with that goal Realistically deliverable in the sprint • Plan to complete chosen PBI’s Copyright © 2012 by Mark J. Sebern

Timing When do we do sprint planning? At the beginning of each sprint, in order to leverage the best possible information How long should it take (for a full-time team)? 4 -8 hours for a full-time team Copyright © 2012 by Mark J. Sebern

Participants Who is involved in sprint planning? Who does what? • Product owner •

Planning Inputs Input Description Product backlog Topmost PBI’s groomed to Ready state Team velocity Constraints Indicator of how much work is practical to complete (units? ) Business or technical Team member skills and availability capabilities Initial sprint goal Product Owner’s business goal for the sprint Copyright © 2012 by Mark J. Sebern

Planning Approaches Two related activities • Choosing what to do • Planning how to do it How can these activities be arranged? • Choose all items in backlog, plan all, repeat till done • Choose one item at a time, plan it, repeat till done Copyright © 2012 by Mark J. Sebern

Capacity A measure of the team’s capacity to do work • Taking into account “task hours” available • Allowing for planning, review, retrospective • Don’t forget time off, holidays, etc. Copyright © 2012 by Mark J. Sebern

Measuring Capacity What units? • Story points (PBI size) [velocity? ] • Effort hours (task size) How do we determine team capacity? • What adjustments might be needed? • PTO, other projects, tech support, travel/education Copyright © 2012 by Mark J. Sebern

Selecting PBIs Seems obvious: choose topmost PBIs! • But what about the PO’s sprint goal? • Why can’t the PO align priorities? Rule: start only what you can finish • Why? Copyright © 2012 by Mark J. Sebern

Sanity Check PBIs Total Copyright © 2012 by Mark J. Sebern Tasks Effort hours

Role-Based Thinking l a • What does the “testing expert” do c i n h before there is anything to test? c e t m a d e • Work together in rapid increments? o t o a g s i ! g y n • Develop (by practice during s t i i l e s i c b i Uexecution) i t wider range of team skills? s c n a r o p p • Replace “individual” emphasis with s e r ongoing team collaboration Copyright © 2012 by Mark J. Sebern

Daily Scrum Daily, 15 -minute (time boxed) activity • How does this translate to a course project? Don’t forget the three questions! • Also: identify “blocking” items that need attention Copyright © 2012 by Mark J. Sebern