1. Copyright © 2012-2014 by Mark J. Sebern Software Engineering Process I SE-2800-13 Sprint Execution

2. Copyright © 2012-2014 by Mark J. Sebern Sprint Execution Sprint execution planning Didn’t we just do sprint planning? Flow management Parallel work (multitasking) Swarming Mini-waterfall

3. Copyright © 2012-2014 by Mark J. Sebern What is swarming? This?

4. Copyright © 2012-2014 by Mark J. Sebern Swarming This?

5. Copyright © 2012-2014 by Mark J. Sebern This? Swarming Or this?

6. Copyright © 2012-2014 by Mark J. Sebern This? Swarming Or this? Can’t just help after all your own work is done. Can’t play bunchball: everyone do same story.

7. Copyright © 2012-2014 by Mark J. Sebern Which Work To Start Next highest-priority item? PBI/task What if there are dependencies? Inter-task Special skills

8. Copyright © 2012-2014 by Mark J. Sebern Danger of Role-Based Thinking What does the “testing expert” do before there is anything to test? Work together in rapid increments? Develop (by practice during execution) a wider range of team skills? Replace “individual” emphasis with ongoing team collaboration (not “my tasks”)

9. Copyright © 2012-2014 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!

10. Copyright © 2012-2014 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! What did I accomplish? What do I plan to work on? What is preventing me from making progress?

11. Copyright © 2012-2014 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! Identify “blocking” items that need attention What did I accomplish? What do I plan to work on? What is preventing me from making progress?

12. Copyright © 2012-2014 by Mark J. Sebern Test-driven development Refactoring Simple design Pair programmin g Continuous integration Collective code ownership Coding standard Metaphor Technical Practices

13. Copyright © 2012-2014 by Mark J. Sebern Task Board

14. Copyright © 2012-2014 by Mark J. Sebern Burndown Chart Can be remaining hours, story points, or both; how would they be used?

15. Copyright © 2012-2014 by Mark J. Sebern Burndown Chart Can be remaining hours, story points, or both; how would they be used?

16. Copyright © 2012-2014 by Mark J. Sebern Sprint Report

17. Copyright © 2012-2014 by Mark J. Sebern Review Sprint execution Swarming Role of experts Why not use waterfall model? Daily scrum 3 questions Technical practices Tracking: burndown, sprint report