Download
software engineering process i n.
Skip this Video
Loading SlideShow in 5 Seconds..
Software Engineering Process I PowerPoint Presentation
Download Presentation
Software Engineering Process I

Software Engineering Process I

113 Vues Download Presentation
Télécharger la présentation

Software Engineering Process I

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Software Engineering Process I • SE-2800-14 • Sprint review and retrospective

  2. Sprint Review & Retrospective • Two “end of sprint” activities • Sprint review • Sprint retrospective How do they differ?

  3. Review Participants

  4. Review Preparation • Sprint review prework • Identify participants (specific people) • Set the schedule (when, duration) • Confirm sprint work is done (DONE)

  5. Review Preparation Same time each sprint? • Sprint review prework • Identify participants (specific people) • Set the schedule (when, duration) • Confirm sprint work is done (DONE)

  6. Review Preparation • Sprint review prework • Identify participants (specific people) • Set the schedule (when, duration) • Confirm sprint work is done (DONE) • What is the definition of DONE? • Who decides? • When is the decision made? (at end? JIT during sprint?) • Granularity of the decision? (per PBI?)

  7. Sprint review prework • Identify participants – specific people • Set the schedule (when, duration) • Confirm sprint work is done • Prepare for demonstration – ceremony level • Decide who does what (facilitator, demo?)

  8. Review Overview Review • Sprint backlog items (or sprint goal) • Potentially shippable product • Groomed product backlog • Updated release plan • Present sprint goal, PBIs, actual achievements • Explain any discrepancies • Demonstrate what actually got built • What if it cannot be demonstrated? (Really??) • Discuss state of the product, future direction of the project • Implicit/explicit backlog grooming

  9. Sprint Retrospective • Why?

  10. Sprint Retrospective More meetings? • Why?

  11. Sprint Retrospective More meetings? • Why? When am I supposed to get some work done?

  12. Sprint Retrospective How about now? More meetings? • Why? When am I supposed to get some work done? The New York Times

  13. Retrospective Participants

  14. Retrospective Participants In particular, probably no managers.

  15. Retrospective Structure • How much time? • Location? • Facilitator? • ScrumMaster • Other team member • Outsider (other ScrumMaster?)

  16. Overview • Improvement actions • Insight backlog • Improved team spirit • Focus • Exercises (or prep) • Objective data • Subjective data • Insight backlog Retrospective • Set atmosphere • Establish shared context • (common perspective from individual ones) • Identify insights (see following slides) • Determine actions • Close the activity

  17. Insights • What worked well, or not? • Improvement ideas? • Organize insight backlog • Cards on wall A B C D E F

  18. Insights • What worked well, or not? • Improvement ideas? • Organize insight backlog • Cards on wall B D E F • Silent grouping • Pre-existing categories? A C

  19. Actions • Select insights from new backlog • “Dot voting” • Consider timeframe for changes • Decide on actions • Specific task items • General changes B D E F A C

  20. Follow Through • Sprint tasks • Include tasks to implement chosen actions • Not a separate “improvement” effort • Integrate into the next sprint’s work

  21. Retrospective Issues • Not doing one (or not well) • Superficial, not addressing real issues • Watch out for the elephant! (safety?) • Poor execution: facilitation, blame/complain • Too ambitious (or miss ongoing improvements) • Lack of follow-through

  22. What Else? • What else did you learn about sprint reviews and retrospectives? • What questions do you have?