1 / 17

Software Engineering Process I

This comprehensive guide explores essential techniques for successful sprint execution in software engineering, focusing on practices such as swarming, flow management, and regular daily scrums. Discover how to enhance team collaboration, prioritize tasks effectively, and address dependencies. Learn the significance of burndown charts and the role of experts in the agile process. By improving team skills and replacing individual task focus with collective effort, you can achieve more in less time. Ideal for teams aiming for efficient agile project management.

shiela
Télécharger la présentation

Software Engineering Process I

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Software Engineering Process I • SE-2800-13 • Sprint Execution

  2. Sprint Execution • Sprint execution planning • Didn’t we just do sprint planning? • Flow management • Parallel work (multitasking) • Swarming • Mini-waterfall

  3. What is swarming? This?

  4. Swarming This? This?

  5. Swarming This? Or this?

  6. Swarming This? • Can’t just help after all your own work is done. • Can’t play bunchball: everyone do same story. Or this?

  7. Which Work To Start • Next highest-priority item? • PBI/task • What if there are dependencies? • Inter-task • Special skills

  8. 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. Daily Scrum • Daily, 15-minute (time boxed) activity • How does this translate to a course project? • Don’t forget the three questions!

  10. 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. 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. Technical Practices

  13. Task Board

  14. Burndown Chart Can be remaining hours, story points, or both; how would they be used?

  15. Burndown Chart Can be remaining hours, story points, or both; how would they be used?

  16. Sprint Report

  17. Review • Sprint execution • Swarming • Role of experts • Why not use waterfall model? • Daily scrum • 3 questions • Technical practices • Tracking: burndown, sprint report

More Related