Agile / Scrum Training Lean Software Development Agile Organizational Metrics Executive Coaching Improved Team Dynamics Improved Efficiency

Transcription

1 Agile / Scrum Training Lean Software Development Agile Organizational Metrics Executive Coaching Improved Team Dynamics Improved Efficiency Sprint Planning #BecomingAgile Webinar Series

2 Webinar Guidelines Presentation to last approximately 45 minutes All participant lines will be muted during the presentation At the conclusion of the presentation questions will be taken through the chat feature of WebEx Any unanswered questions will be captured and responses provided to attendees within 1 week Session is being recorded and will be posted for review THANK YOU FOR ATTENDING!

3 Today s Presenter Agile Coach & Trainer Davisbase Consulting dan.moody@davisbase.com Product Owner background 10 years of software development experience Spearheaded Agile transformation at large #BecomingAgile! #agile! Connect on LinkedIn: linkedin.com/in/danielrmoody

4 Today s Topics 1. Sprint Planning Overview 2. Tasking stories 3. Task assignment 4. Sprint Planning gone wrong

5 Sprint Planning Overview What is Sprint Planning? #BecomingAgile

6 Scrum Guide Sprint Planning Answers the following: 1. What can be delivered in the Increment resulting from the upcoming Sprint? 2. How will the work needed to deliver the Increment be achieved? Source:

7 Sprint Planning Sequence

8 The Goal ü Prioritized Sprint Backlog accepted for the Sprint ü All stories are tasked ü All tasks are estimated ü All tasks have an owner ü The team is confident they can accomplish all tasks by the demo Elaborated Stories Definition of Ready Sprint Planning Tasks

9 Prerequisites to Sprint Planning Prioritized backlog Release Plan Customer/Product Owner ready to discuss story details Tool preparation Agree to the definition of done Agree on sprint cadence Create a definition of ready

10 Sprint Plan: a Commitment? Is the team committing to the work in the Sprint, or is it just a plan? If we follow this agile principle... Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.... should it matter?

11 Sprint Plan: a Commitment? Team commits to work on a set of stories for the Sprint. Team believes stories can be completed within the Sprint After Sprint Planning is complete, no other stories will be added to the Sprint After Sprint Planning is complete, stories cannot be re-prioritized Team doesn t commit to complete all stories with 100% certainty (i.e. no death marches )

12 Managing Expectations The best way to make authentic commitments and set realistic expectations is to UNDERSTAND YOUR CAPACITY Be realistic Factor in inefficiency Account for vacation Be transparent about calculation Communicate Eliminate waste More on capacity when we discuss task assignment

13 Who Participates? All Team Members Product Owner Scrum Master (as facilitator) Executives and management

14 Tasking Stories Detailed plan for a Sprint #BecomingAgile

15 Best Practices for Tasking Stories Task stories such that tasks are between 1 and 6 hours ( right-sized ) can be done by one person (unless pairing or meeting) are understood by every team member After tasking, review tasks versus the Definition of Done Consider tasking stories in pairs or groups and comparing results

16 SMART Tasks Bill Wake (INVEST for User Stories) says tasks should be: Specific: A task needs to be specific enough that everyone can understand what involved in it. Measurable: The key measure is, Can we mark it as done? Achievable: The task owner should expect to be able to achieve a task. Relevant: Every task should be relevant, contributing to the story at hand. Timeboxed: A task should be timeboxed (limited to a specific duration) Source: scaledagileframework.com/tasks

17 Manage Flow & Morale with Smaller Tasks Smaller tasks help flow; give sense of accomplishment Story Not Started In Process To Verify Done Story A Task 6 Task 3 Task 4 Task 2 Task 1 Task 5 Story B Task 4 Task 3 Task 2 Task 1 Task 5 Story C Task 1 Task 2 Task 3

18 Estimating Tasks Estimate tasks in ideal hours Estimate in whole hours Round up Don t over-think the estimate Avoid comparisons of planned vs actual for performance management Use retrospectives to discuss consistent patterns in estimation errors to help the team be more successful

19 Post Planning Task Discovery During a sprint, the team may discover tasks that were missed initially, or may uncover that additional tasks are necessary Discovering some tasks during a sprint is normal Discovering many or most tasks during a sprint is likely a symptom of poor planning or story refinement Discovered tasks don t necessarily imply the team won t finish all stories committed for the sprint

20 Task assignment Self-managing capacity #BecomingAgile

21 Who Assigns Tasks? Who assigns tasks to the team members? THE TEAM CHOOSES THEIR TASKS Trust the team Allow team members to build new skills by taking on different tasks Encourage collective ownership Encourage swarming Foster buy-in

22 Determining Capacity Example: 2 Week Sprint Work Days [8 hours x 10] 80 Inefficiency [20% x 80] (16) Maximum Available Time 64 80% Allocation to Team [(100%-80%) x 64] (13) Sprint Ceremonies (13) Actual Capacity 38

23 Visualize Capacity Use Visual Tools Ensure folks are filling time Fight against over-commitment Paper Clip exercise: Distribute paper clips for each hour available Give up clips when task commitments are made No more clips, no more commitments

24 Sprint Planning Gone Wrong Common Sprint Planning Pitfalls #BecomingAgile

25 Common Sprint Planning Pitfalls Doing story refinement during sprint planning Tech lead tasks stories and assigns the tasks to team members User stories are too small basically tasks Inaccurate estimates used in performance reviews Only certain people can do certain tasks Focusing on your tasks

26 The Next #BecomingAgile Webinar Daily Planning Thursday, February 5, :00pm ET #BecomingAgile

27 Claim Your PMI PDUs Self report your PDUs on PMI.org Provider/REP #4095 This event is worth 1 PDU #BecomingAgile

28 Thank You! STAY CONNECTED! Davisbase Consulting #BecomingAgile - Blog - Webinar Series - Newsletter Daniel R. Moody dan.moody@davisbase.com