Your SlideShare is downloading. ×
0
Lecture 10 scrum
Lecture 10 scrum
Lecture 10 scrum
Lecture 10 scrum
Lecture 10 scrum
Lecture 10 scrum
Lecture 10 scrum
Lecture 10 scrum
Lecture 10 scrum
Lecture 10 scrum
Lecture 10 scrum
Lecture 10 scrum
Lecture 10 scrum
Lecture 10 scrum
Lecture 10 scrum
Lecture 10 scrum
Lecture 10 scrum
Lecture 10 scrum
Lecture 10 scrum
Lecture 10 scrum
Lecture 10 scrum
Lecture 10 scrum
Lecture 10 scrum
Lecture 10 scrum
Lecture 10 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

Lecture 10 scrum

229

Published on

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

  • Be the first to like this

No Downloads
Views
Total Views
229
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
11
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. Mountain Goat Software, LLC
  • 2. An Introduction to Scrum Ghulam Yasin Mountain Goat Software, LLC
  • 3. Scrum in 100 words • Scrum is an agile process that allows us to focus on delivering the highest business value in the shortest time. (Limited Resources eg cost, schedule) • It allows us to rapidly and repeatedly inspect actual working software (every two weeks to one month). • The business sets the priorities. Teams self-organize to determine the best way to deliver the highest priority features. • Every two weeks to a month anyone can see real working software and decide to release it as is or continue to enhance it for another sprint. (module, phase) Mountain Goat Software, LLC
  • 4. Scrum has been used by: •Microsoft •Yahoo •Google •Electronic Arts •High Moon Studios •Lockheed Martin •Philips •Siemens •Nokia •Capital One •BBC Mountain Goat Software, LLC •Nielsen Media •First American Real Estate •BMC Software •Ipswitch •John Deere •Lexis Nexis •Sabre •Salesforce.com •Time Warner •Turner Broadcasting •Oce
  • 5. Scrum has been used for: • • • • • • • • Commercial software In-house development Contract development Fixed-price projects Financial applications ISO 9001-certified applications Embedded systems 24x7 systems with 99.999% uptime requirements Mountain Goat Software, LLC • Video game development • life-critical systems • Satellite-control software • Websites • Handheld software • Mobile phones • Network switching applications
  • 6. Characteristics • • • • • • Self-organizing teams Product progresses in a series of month-long “sprints/runs” Requirements are captured as items in a list of “product backlog/accumulation” (user stories / features) No specific engineering practices prescribed Uses reproductive rules to create an agile environment for delivering projects One of the “agile processes” Mountain Goat Software, LLC
  • 7. The Agile….. Individuals and Individuals and interactions interactions over Process and tools Process and tools Working software Working software over Comprehensive Comprehensive documentation documentation Customer Customer collaboration collaboration over Contract negotiation Contract negotiation Responding to change Responding to change over Following a plan Following a plan Mountain Goat Software, LLC
  • 8. Putting it all together Mountain Goat Software, LLC
  • 9. 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 beat Product is designed, coded, and tested during the sprint (SDLC phases) Mountain Goat Software, LLC
  • 10. Sequential vs. overlapping development Requirements Design Code Test Rather than doing all of one thing at a time... ...Scrum teams do a little of everything all the time Mountain Goat Software, LLC
  • 11. Scrum framework Roles •Product owner •ScrumMaster •Team Ceremonies •Sprint planning •Sprint review •Sprint retrospective •Daily scrum meeting Artifacts •Product backlog •Sprint backlog •Burndown charts Mountain Goat Software, LLC
  • 12. Scrum framework Roles •Product owner •ScrumMaster •Team Ceremonies •Sprint planning •Sprint review •Sprint retrospective •Daily scrum meeting Artifacts •Product backlog •Sprint backlog •Burndown charts Mountain Goat Software, LLC
  • 13. 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 Mountain Goat Software, LLC
  • 14. The ScrumMaster • • Represents management to the project • • Removes weaknesses • • Responsible for approving Scrum values and practices Ensure that the team is fully functional and productive Enable close cooperation across all roles and functions Safeguard the team from external interferences Mountain Goat Software, LLC
  • 15. The team • • • Typically 5-9 people Cross-functional: • Programmers, testers, user experience designers, etc. • May be exceptions (e.g., database administrator) Members should be full-time Mountain Goat Software, LLC
  • 16. The team • • Teams are self-organizing • Ideally, no titles but rarely a possibility Membership should change only between sprints Mountain Goat Software, LLC
  • 17. Scrum framework Roles •Product owner •ScrumMaster •Team Ceremonies •Sprint planning •Sprint review •Sprint retrospective •Daily scrum meeting Artifacts •Product backlog •Sprint backlog •Burndown charts Mountain Goat Software, LLC
  • 18. Sprint planning • Team selects items from the product backlog they can commit to completing • • Sprint backlog is created • Tasks are identified and each is estimated (1-16 hours) High-level design is considered Mountain Goat Software, LLC
  • 19. The daily scrum • Parameters • • • Daily 15-minutes Stand-up • • Whole world is invited Only team members, ScrumMaster, product owner, can talk • Not for problem solving • Helps avoid other unnecessary meetings Mountain Goat Software, LLC
  • 20. Everyone answers 3 questions What did you do yesterday? did you do yesterday? What will you do today? today? Is anything in your way? Mountain Goat Software, LLC 1 2 3
  • 21. The sprint review • 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 Mountain Goat Software, LLC
  • 22. Scrum framework Roles •Product owner •ScrumMaster •Team Ceremonies •Sprint planning •Sprint review •Sprint retrospective •Daily scrum meeting Artifacts •Product backlog •Sprint backlog •Burndown charts Mountain Goat Software, LLC
  • 23. Managing the sprint backlog • • • Any team member can add, delete or change the sprint backlog 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 Mountain Goat Software, LLC
  • 24. Scalability • • Scalability comes from teams of teams Factors in scaling •Type of application •Team size •Team dispersion •Project duration Scrum has been used on multiple 500+ person projects Mountain Goat Software, LLC
  • 25. Thank you very much Mountain Goat Software, LLC

×