Scrum
Upcoming SlideShare
Loading in...5
×
 

Scrum

on

  • 4,528 views

An introduction to scrum software development methodology. Happy scrumming =)

An introduction to scrum software development methodology. Happy scrumming =)

Statistics

Views

Total Views
4,528
Views on SlideShare
4,102
Embed Views
426

Actions

Likes
24
Downloads
289
Comments
1

9 Embeds 426

http://noly.co 254
http://ianjseath.wordpress.com 135
http://www.google.com 25
https://twitter.com 4
http://www.linkedin.com 4
http://pulse.me&_=1374283446826 HTTP 1
http://pulse.me&_=1374305280138 HTTP 1
http://cloud.feedly.com 1
http://www.bing.com 1
More...

Accessibility

Upload Details

Uploaded via as Adobe PDF

Usage Rights

CC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike LicenseCC Attribution-NonCommercial-ShareAlike License

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…
  • how to download this ppt? its downloading a pdf,,
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Scrum Scrum Presentation Transcript

  • SCRUM Next Big Thing
  • Traditional models ? Waterfall
  • Requirements Design Implementation Verification Maintenance effect
  •   here
  •   !! and
  •   here
  •   too
  •   !! change
  •   here
  •   ?
  • Waterfail Pros: • Very logical • Think before you build • Follow a plan • Keep things organized Cons: Humans are involved !!
  • Requirement not clear
  • Good ideas come along the way
  • First time you touch the product, You immediately think of 20 ways to make it better
  • We are bad at predicting future
  • Use documents as main communication channel
  • Waterfail = Misery
  • Agile
  • • Get hands on quickly • cross-functional team empowered to make decision • rapid iteration / incremental • continuous customer input • Just do it ? ...not exactly Agile
  • Scrum
  • Scrum Roles
  • Product Owner
  • Product Owner • One person • Define features • Prioritizing list • Provide feedback • Accept/Reject results • ≈ Customer
  • The Team
  • The Team • provide ideas to PO on how to make product great • 7 ± 2 people • Cross-functional • Self-organizing
  • Scrum Master
  • Scrum Master • Help Team learn and apply Scrum • Does whatever to help Team & PO • Should be full-time • Team member is ok but not PO
  • Product Owner Team Members Scrum Master Managers Users Marketing
  • Starting Scrum
  • Product Backlog • Value / Feature of product (High level) • describe as User Story • Owned by Product Owner • Estimated by Team • not perfect (expected to change)
  • Product Backlog
  • As a user I want functionality ( So that benefit )
  • As a librarian I want to be able to search for books by publication year So that I can keep track of books of certain year Search books byYear 8
  • Sprints
  • Sprints • Cycles of work • time-boxed • 1 - 4 weeks • never extended
  • Sprint Planning
  • Sprint Planning pt.1 • PO + Team + (SM) • High priority items on Product Backlog • Context + Def. of done • What PO wants
  • Sprint Planning pt.2 • Team + (PO + SM) • focus on the How • How much effort we have? • How many items we could do? • Sprint Backlog • Volunteer for one task at a time
  • Definition of Done • Introduce earlier • To avoid 90% syndrome • Usually physical / tangible • Works great with ex. TDD
  • Sprint Backlog
  • Daily Scrum
  • Daily Scrum What I did since last meeting? What I will do until next meeting? What things are in my way?
  • Daily Scrum • Only Team talks ( to coordinate only) • No problem solving ! • Max 15 mins .. so .. standup !
  • Update Sprint Backlog
  • Low-tech / High touch
  • Product Backlog Refinement • lesser known but valuable • 5% of sprint time (Team + PO) • Req. analysis / Splitting items / (re)Estimation • Workshop near end of sprint • if not? Sprint Planning = confusion, discovery..
  • Ending Sprint
  • Sprint Review
  • Sprint Review • Needs preparation but informal • No slides • 1-2 hours/sprint/week • Show complete features • Accept or Reject
  • Sprint Retrospective
  • Sprint Retrospective What to Start doing What to Stop doing What to Continue doing
  • More Release Sprint Release Planning
  • Sites www.ScrumAlliance.org www.Scrum.org www.MountainGoatSoftware.com www.AgileSoftwareDevelopment.com www.noop.nl
  • Sources • The Scrum Primer v1.2 (pdf) • The Zen of Scrum (Slideshare) Link: http://www.slideshare.net/jurgenappelo/the-zen-of-scrum-10