17
Copyright © 2012-2014 by Mark J. Sebern Software Engineering Process I SE-2800-13 Sprint Execution
| Date post: | 30-Dec-2015 |
| Category: |
Documents |
| Upload: | anissa-mckinney |
| View: | 215 times |
| Download: | 1 times |
Copyright © 2012-2014 by Mark J. Sebern
Software Engineering
Process ISE-2800-13
Sprint Execution
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
Copyright © 2012-2014 by Mark J. Sebern
What is swarming?
This?
Copyright © 2012-2014 by Mark J. Sebern
Swarming
This?
This?
Copyright © 2012-2014 by Mark J. Sebern
This?
Swarming
Or this?
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.
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
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”)
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!
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?
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?
Copyright © 2012-2014 by Mark J. Sebern
Test-driven developme
ntRefactoring Simple
design
Pair programmi
ng
Continuous integration
Collective code
ownership
Coding standard Metaphor
Technical Practices
Copyright © 2012-2014 by Mark J. Sebern
Task Board
Copyright © 2012-2014 by Mark J. Sebern
Burndown Chart
Can be remaining hours, story points, or both; how would they be
used?
Copyright © 2012-2014 by Mark J. Sebern
Burndown Chart
Can be remaining hours, story points, or both; how would they be
used?
Copyright © 2012-2014 by Mark J. Sebern
Sprint Report
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
