• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Starting with Scrum
 

Starting with Scrum

on

  • 290 views

Presentation about how to start implementing scrum in projects. Explaining core concepts and artifacts

Presentation about how to start implementing scrum in projects. Explaining core concepts and artifacts

Statistics

Views

Total Views
290
Views on SlideShare
290
Embed Views
0

Actions

Likes
0
Downloads
2
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Starting with Scrum Starting with Scrum Presentation Transcript

    • Starting with Scrum Jimmy Campos
    • Agenda • SCRUM • Actors • Product Backlog • Sprint Backlog • Definition of Done • Daily Scrum Meeting • Sprint Review • Sprint Retrospective
    • What is? • Scrum is a simple framework for effective team collaboration on complex projects. • Is an agile methodology, it allows us deliver products more faster.
    • Product Backlog • Ordered list of ideas for the product • It is the single source from which all requirements flow • Product backlog usually doesn’t change
    • Product Backlog Meeting • Keeping the product backlog ordered • Removing or demoting items that no longer seem important • Adding or promoting items that arise or become more important • Splitting items into smaller items • Merging items into larger items • Estimating items
    • Sprint Backlog • Sprint Duration: 2-4 week • Plan what item of the product backlog we will work, estimate it and split it in tasks
    • Definition of Done • When the product increment is delivered, it needs to be "done" according to a shared understanding of what "done" means. This definition is different for every Scrum team, and as the team matures the Definition of Done will expand and become more stringent.
    • What is Done? • All code is finished? • Code is finished and tested? • Code is deployed? • Client approval?
    • Daily Scrum Meeting • Time boxed meeting (15 minutes) where all the team talk about – What I have accomplished yesterday? – What I plan to accomplish today? – What (if anything) is impeding my progress? • This can be at 9am
    • Sprint Review • At the end of the sprint, the Scrum team and stakeholders review the sprint's output. • Time box: Recommended 1 hour per week of sprint duration.
    • Sprint Retrospective • Review how things went in terms of the process, relationships among people, and the tools. • What went well and what didn't go so well, and it identifies potential improvements
    • Q&A
    • Thanks!