1 / 12

SCRUM

Learn about the history and principles of SCRUM, from its origins in manufacturing to its application in today's software development projects. Explore key components such as daily stand-ups, sprint planning, backlog management, and the role of the Scrum Master in ensuring project success.

shannonbernard
Download Presentation

SCRUM

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. SCRUM COMP 319

  2. SCRUM history • In 1986, Hirotaka Takeuchi and Ikujiro Nonaka • More an observation of good practise in manufacturing (e.g. cameras, photocopiers, PCs) than an theoretical invention • Team covers all aspects of development • Product requirements • Hardware engineers • Software engineers • Production engineers • Move from relay approach to COMP319

  3. Scrum process COMP319

  4. Daily Scrum • 15 minute meeting (start of day) • Progress since yesterday • Planning to do today • What stops you completing todays work? COMP319

  5. Product backlog • Maintained throughout the project • Shows what’s outstanding • Description of all features • Features are prioritized • Each item is time/cost estimated COMP319

  6. Sprint planning • Deciding what work to be done • Customer, prioritizes work from work backlog • Customer reviews current backlog (may decide to drop some features or add new ones) • Deciding what work goes into the new Sprint backlog COMP319

  7. Sprint backlog • All tasks for current sprint • Each task should be doable in typically 4-16 hours • Developers sign up for tasks (not assigned) COMP319

  8. Sprint • Iteration of 1 to 4 weeks • Produces a deliverable user testable version of the product • Time boxed • If function not completed/tested, it shouldn’t be presented in product • Sprint burn down • Indication of Sprint progress COMP319

  9. Sprint burn down COMP319

  10. Release burndown COMP319

  11. Scrum meetings • Sprint review meeting • What was completed? • Demonstration of product • Review product backlog COMP319

  12. Scrum master Builds the release plan Controls what is allowed into the sprint (checks for over-commitment) Manages daily scrum (removes obstacles) Acts as project manager providing all communication between the team and the management COMP319

More Related