Your SlideShare is downloading. ×
Scrum Presentation Version 8
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

Scrum Presentation Version 8

309

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
309
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
2
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. Commander’s Intent To convey a big-picture view of Agile development
  • 2. Why was change needed?
  • 3. Define Project Success
    • On time
    • Within budget
    • With all planned features
  • 4. Project Score Card (ca 2000) Failed 23% Challenged 49% Succeeded 28%
  • 5. Agile Central Idea “ Software development is like new product development not like manufacturing. This difference is revolutionary, and it leads to a completely new way of thinking about what software is and how to build it. ” Ken Schwaber Agile Software Development with Scrum 2001
  • 6. Manifesto for Agile Software Development (2001) That is, while there is value in the items on the right, we value the items on the left more. Signatures to the manifesto Individuals & interactions over Processes & tools Working software over Comprehensive documentation Customer collaboration over Contract negotiation Responding to change over Following a plan
  • 7. When I think of Agile Development
  • 8. Self-managing, Cross-functional Teams— What are they?
  • 9. Requirements User Stories—What are they?
  • 10. Scrum—What is it?
  • 11. Milestones Inch Pebbles
  • 12. Ensuring What Gets Built Delivers Value Sometimes 16% Often 13% Features and Functions Used in a Typical System Never 45% Rarely 19% Always 7% Always or Often Used – 20% Never or Rarely Used – 64%
  • 13. Scrum Process Flow Product Backlog Sprint Backlog 24 Hours 2–4 Weeks Daily Scrum Meeting Potentially Shippable Product Increment Sprint
  • 14. The Scrum Cycle Planning Meeting Sprint Review Sprint Retrospective Planning Meeting Daily Scrum Daily Scrum One sprint

×