Your SlideShare is downloading. ×
0
88908872 scrum
88908872 scrum
88908872 scrum
88908872 scrum
88908872 scrum
88908872 scrum
88908872 scrum
88908872 scrum
88908872 scrum
88908872 scrum
88908872 scrum
88908872 scrum
88908872 scrum
88908872 scrum
88908872 scrum
88908872 scrum
88908872 scrum
88908872 scrum
88908872 scrum
88908872 scrum
88908872 scrum
88908872 scrum
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

88908872 scrum

715

Published on

Published in: Sports, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
715
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. SCRUM in Brief1 All Rights Reserved © Alcatel-Lucent 2012
  • 2. Agile Manifesto – Philosophy www.agilemanifesto.org Individuals and over Process and tools interactions Comprehensive Working software over documentation Customer over Contract negotiation collaboration Responding to over Following a plan change All Rights Reserved © Alcatel-Lucent 2012
  • 3. SCRUM – The Framework3 All Rights Reserved © Alcatel-Lucent 2012
  • 4. Sprints• Scrum projects make progress in a series of “sprints” • Analogous to Extreme Programming iterations• Typical duration is 2–4 weeks or a calendar month at most• A constant duration leads to a better rhythm• Product is designed, coded, and tested during the sprint All Rights Reserved © Alcatel-Lucent 2012
  • 5. Scrum framework Roles •Product owner •ScrumMaster •Team Ceremonies •Sprint planning •Sprint review •Sprint retrospective •Daily scrum meeting Artifacts •Product backlog •Sprint backlog •Burndown charts All Rights Reserved © Alcatel-Lucent 2012
  • 6. Scrum framework Roles •Product owner •ScrumMaster •Team Ceremonies •Sprint planning •Sprint review •Sprint retrospective •Daily scrum meeting Artifacts •Product backlog •Sprint backlog •Burndown charts All Rights Reserved © Alcatel-Lucent 2012
  • 7. Product owner• Define the features of the product• Decide on release date and content• Be responsible for the profitability of the product• Prioritize features according to market value• Adjust features and priority every iteration, as needed• Accept or reject work results All Rights Reserved © Alcatel-Lucent 2012
  • 8. The ScrumMaster• Represents management to the project• Responsible for enacting Scrum values and practices• Removes impediments• Ensure that the team is fully functional and productive• Enable close cooperation across all roles and functions• Shield the team from external interferences All Rights Reserved © Alcatel-Lucent 2012
  • 9. The team• Typically 5-9 people• Cross-functional: • Programmers, testers, user experience designers, eventually product owner etc.• Members should be full-time • May be exceptions (e.g., database administrator)• Teams are self-organizing • Ideally, no titles but rarely a possibility• Membership should change only between sprints All Rights Reserved © Alcatel-Lucent 2012
  • 10. Scrum framework Roles •Product owner •ScrumMaster •Team Ceremonies •Sprint planning •Sprint review •Sprint retrospective •Daily scrum meeting Artifacts •Product backlog •Sprint backlog •Burndown charts All Rights Reserved © Alcatel-Lucent 2012
  • 11. Team Sprint planning meetingcapacity Sprint prioritization Product • Analyze and evaluate product Sprint backlog backlog • Select sprint goal goalBusinessconditions Sprint planning • Decide how to achieve sprint goal (design) Current • Create sprint backlog (tasks) from Sprint product product backlog items (user stories / backlog features) • Estimate sprint backlog Techno- logy All Rights Reserved © Alcatel-Lucent 2012
  • 12. Sprint planning• Team selects items from the product backlog they can commit to completing• Sprint backlog is created and put on taskboard • Tasks are identified and each is estimated (1-16 hours) • Collaboratively, not done alone by the ScrumMaster• High-level design is considered As a vacation Code the middle tier (8 hours) planner, I want to Code the user interface (4) see photos of the Write test fixtures (4) hotels. Code the foo class (6) Update performance tests (4) All Rights Reserved © Alcatel-Lucent 2012
  • 13. The sprint goal• A short statement of what the work will be focused on during the sprint Life Sciences Support features necessaryDatabase Application for population genetics studies.Make the application run on SQLServer in addition to Oracle. Watermill - Hercules Fix Rollout and implement backward compatibility with Aurora release. All Rights Reserved © Alcatel-Lucent 2012
  • 14. The daily Scrum• Parameters • Daily • 15-minutes • Stand-up• Not for problem solving • Whole world is invited • Only team members, product owner, can talk• Helps avoid other unnecessary meetings All Rights Reserved © Alcatel-Lucent 2012
  • 15. Everyone answers 3 questions 1 What did you do yesterday? 2 What will you do today? 3 Is anything in your way? • These are not status for the ScrumMaster • They are commitments in front of peers All Rights Reserved © Alcatel-Lucent 2012
  • 16. The sprint review (demo)• Team presents what it accomplished during the sprint• Typically takes the form of a demo of new features or underlying architecture• Informal • 2-hour prep time rule • No slides• Whole team participates• Invite the world All Rights Reserved © Alcatel-Lucent 2012
  • 17. Sprint retrospective• Periodically take a look at what is and is not working• Typically 15–30 minutes• Done after every sprint• Whole team participates • ScrumMaster • Product owner • Team • Possibly customers and others All Rights Reserved © Alcatel-Lucent 2012
  • 18. Start / Stop / Continue• Whole team gathers and discusses what they’d like to: Start doing Stop doing Continue doing All Rights Reserved © Alcatel-Lucent 2012
  • 19. Scrum framework Roles •Product owner •ScrumMaster •Team Ceremonies •Sprint planning •Sprint review •Sprint retrospective •Daily scrum meeting Artifacts •Product backlog •Sprint backlog •Burndown charts All Rights Reserved © Alcatel-Lucent 2012
  • 20. Product backlog • The requirements • A list of all desired work on the project • Ideally expressed such that each item has value to the users or customers of the product • Prioritized by the product owner • Reprioritized at the start of each sprint This is the product backlog All Rights Reserved © Alcatel-Lucent 2012
  • 21. Sprint backlog • Individuals sign up for work of their own choosing • Work is never assigned by a person to another person • Estimated work remaining is updated daily • Any team member can add, delete or change the sprint backlog • Work for the sprint emerges • If work is unclear, define a sprint backlog item with a larger amount of time and break it down later • Update work remaining as more becomes known All Rights Reserved © Alcatel-Lucent 2012
  • 22. Burndown Charts Release burn-down chart after each sprint closure 140 120 121,5 100 101,5 88,5 80 71,5 Initial release burndown 60 55,5 Actual release burndown 45,5 40 20 22,5 0 -10,5 -20 Sprint1 Sprint2 Sprint3 Sprint4 Sprint burn-down chart 250 200 Remaining Hours 150 100 50 0 15-Dec 16-Dec 17-Dec 18-Dec 21-Dec 22-Dec 23-Dec 4-Jan 5-Jan 6-Jan 7-Jan 8-Jan 11-Jan 12-Jan 13-Jan 14-Jan 15-Jan 18-Jan 19-Jan 20-Jan 21-Jan 22-Jan 25-Jan 26-Jan22 All Rights Reserved © Alcatel-Lucent 2012

×