• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
What is Scrum? Project Management beyond the promise.
 

What is Scrum? Project Management beyond the promise.

on

  • 3,028 views

What is Scrum? Principles, rules, roles, artefacts, timeboxes of Scrum.

What is Scrum? Principles, rules, roles, artefacts, timeboxes of Scrum.

Statistics

Views

Total Views
3,028
Views on SlideShare
2,767
Embed Views
261

Actions

Likes
3
Downloads
64
Comments
0

3 Embeds 261

http://bart.vermijlen.be 177
http://www.bartvermijlen.com 79
http://feeds.feedburner.com 5

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

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

    What is Scrum? Project Management beyond the promise. What is Scrum? Project Management beyond the promise. Presentation Transcript

    • What is Scrum?Project Management beyond the promise @bartvermijlen
    • Overview • introduction • roots • principles • a framework • roles • timeboxes • rules • artefacts • money for nothing and change for free
    • IntroductionA project has 4 fixed aspects• Time• Budget• Quality• Scope
    • IntroductionA project has 4 fixed aspects• Time (?)• Budget• Quality (?)• Scope (?)
    • IntroductionA project has 4 fixed aspects• Time• Budget• Quality (?)• ScopeA scrum project has 3 fixed aspects• Time• Budget• QualityScope is not fixed!
    • Scrum RootsAgile Software development:Individuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a plan(Agilemanifesto.org)
    • Scrum RootsAgile Software development:Individuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a plan(Agilemanifesto.org)
    • Scrum PrinciplesAgility = Responsiveness to changeTransparencyInspectionAdaptation
    • Scrum = a frameworkRoles • Team • Product Owner • Scrum MasterTimeboxes • Sprint • Sprint planning • Sprint review (+ retrospective) • Daily ScrumArtefacts• Product backlog• Sprint backlog (-> Scrumboard)• Burndown chart
    • Scrum RolesTeam • developers, testers, UX designers, SEO/Analytics,… • 2-7 • self organising • split product backlog into tasksProductowner • define & prioritise product backlog / user stories • negotiate definition of "Done"Scrum Master • guard scrum process • remove team impediments
    • Scrum TimeboxesSprint • 1-4 weeks • ends with potentially shippable products (working software)Sprint planning (SM, Team, PO) • 1-8 hoursDaily Scrum (SM, Team) • 15 mins • yesterday/today/impedimentsSprint review (SM, Team, PO) • 30 mins - 4 hours • Demo or Die • acceptance of user stories by POSprint retrospective (SM, Team) ! • lessons learned
    • Scrum Rules• Priorities never change during a sprint• Nobody (neither PO) must interfere during a sprint• Team can ask new user stories when finished early to PO• Team is self-regulating
    • Scrum artefactsProduct backlog • Managed & prioritised by PO • User storiesSprint backlog • Quantified tasks (derived from product backlog) • Managed by Team
    • Scrum artefacts - Burndown charthours/points s1 s2 s3 time
    • Scrum artefacts - Burndown charthours/points s1 s2 s3 time
    • Scrum artefacts - Scrumboard
    • Change for free= obviousPO can reorder priorities at every sprint planning
    • Money for nothinghours/pointspay back70% to Remove functionalitycustomer,Keep 30% s1 s2 s3 time
    • Further reading- agilemanifesto.org- scrumalliance.org- scrum.org/scrumguides- scrum.jeffsutherland.com- Ken Schwaber: “Agile Project Management with Scrum” (Microsoft Press)
    • @bartvermijlen