• Save
Being Agile - Doing Scrum
Upcoming SlideShare
Loading in...5
×
 

Being Agile - Doing Scrum

on

  • 1,340 views

Presentation for employees of XB Software Solutions, introducing Scrum. Duration 90 - 120 minutes.

Presentation for employees of XB Software Solutions, introducing Scrum. Duration 90 - 120 minutes.

Statistics

Views

Total Views
1,340
Views on SlideShare
1,336
Embed Views
4

Actions

Likes
3
Downloads
0
Comments
0

2 Embeds 4

http://www.linkedin.com 3
http://www.slideshare.net 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

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
  • NEXT SLIDE: AGILE MANIFESTO

Being Agile - Doing Scrum Being Agile - Doing Scrum Presentation Transcript

  • Being Agile – Doing Scrum XB Software Solutions
  • Agile Manifesto
    • Individuals and interactions over processes and tools
    • Working software over comprehensive documentation
    • Customer collaboration over contract negotiation
    • Responding to change over following a plan
  • Scrum?
    • Framework for creating your own agile process
    • Will help you fail in 30 days or less
    • Emergence: the beauty of letting go, and trusting
    • “ At the beginning of the project we’ll be more stupid about the project than we’ll ever be again”
  • SCRUM = ACTION On your feet!
  • The Ballpoints Game
    • Objective: score “ball points” as a whole team
      • Assign one person as the Starter and a different one as the Finisher. Place all balls in a box or similar container.
      • Pass balls, individually, from one person to another.
      • Each ball must have air time between passes.
      • You must not pass to your immediate neighbor.
      • Each ball must begin with the Starter who takes it from the box, and end with the Finisher, who places it back in the box.
      • Each ball that goes through a full pass of the team and ends back in the box counts as one point.
      • The team has one minute to plan and estimate how many points they will get.
      • The team has two minutes to score as many points as possible.
      • And iterate.
  • EXECUTE REFLECT PLAN
  • Scrum Foundations
    • Empiricism
    • Self Organization
    • Collaboration
    • Time Boxing
    • Prioritization
  • Feature Priorization & Emergence
    • Deliver the highest value early on
    • But don’t neglect the bigger picture
    • Design can emerge while still delivering value to your customer
  • User stories
    • Requirements:
      • As a <USER> I want <FUNCTION> so that <BUSINESS_VALUE>
    • Independent, Negotiable, Valuable, Estimable, Small, Testable
    • Scrum is easy!
    • Simple to understand
    • Implemented in a few days
    • Scrum is hard!
    • Confrontational at times
    • Micro manager’s hell
    • Requires commitment to agile principles on all levels
    • Need to break through established patterns
  • SCRUM = ACTION On your feet!
  • Scrum Roles
    • Team
      • Self managing, Cross functional, Autonomous, Accountable
    • Product Owner
      • Drives the product vision, Maintains and prioritizes the backlog, Accepts the working software
    • Scrum Master
      • Manages the process, Supports the team, Removes organization impediments
  •  
  • Scrum documents
    • Product Backlog
      • A living list of prioritized user stories
      • Represents the what of the system
      • Everyone can add, only product owner can prioritize
    • Sprint Backlog
      • List of tasks
      • Represents the how of the system
      • Owned and managed by the team
    • Impediment list
      • List of organizational and team impediments (with suggested solutions)
    • Definition of Done
      • Checklist of acceptance criteria for working software
  • Scrum Ceremonies
    • Story Time
      • Discuss high priority backlog items
      • Establish acceptance criteria
      • Estimate story point values
    • Sprint Planning
      • Team and product owner negotiate commitment
    • Daily Scrum
      • 15 Minutes team meeting
      • What did you do yesterday?
      • What will you do today?
      • What is getting in your way?
    • Sprint Demo and Review
      • At the end of sprint: demonstrate working software
      • Receive and discuss feedback
    • Sprint Retrospective
      • Inspect and adapt the process
      • Results in explicit improvement commitments
  • Scrum Process
  • From Scrum to Xrum
    • Scrum: Framework for creating your own agile process
    • Still busy finding our ‘XB’ way
    • Distributed teams?
    • Current project: B2B EOLv2 (Rens/Emiel/Den Bosch)
    • Current Project: B2B ChannelNet (MarcK/Jim/Almere)
  • Xrum Task Board
  • Xrum Definition of Done
    • Een user story is gereed zodra:
    • De Bamboo build er niet door gebroken wordt
    • Er een unit test is geschreven en passeert
    • Een screenshot, voor zover niet conform de mockup, is goedgekeurd door de Product Owner
    • De code en unit test zijn gereviewed door een teamcollega
    • Het de bestaande functionaliteit niet breekt
    • Het component design in Confluence is bijgewerkt
    • Het geïnstalleerd is op de Camel
    • Autorisatieniveau’s goed worden gecontroleerd
    • Bijbehorende installatiescripts beschikbaar zijn gesteld voor oplevering
    • Iemand van buiten het team met functionele kennis een functionele test heeft gedaan
    • Een user story is gereed zodra:
    • Deze volledig af is
    • De code compleet is
    • Er geen bugs bekend zijn
    • Deze is goedgekeurd door de Proxy Product Owner
    • Deze klaar is voor productie
  • Xrum Team Motivation
  • Quotes
    • Users don’t know what they want until they’re shown what they can get.
    • Fixed time and fixed price and fixed scope and high quality in any non-trivial project? Never happened. Never will happen.
    • Leaderless teams? Leaderfull teams!
    • Celebrate failure because you took a risk.
    • If you want better software, just ask .
  • ????? WHAT’S YOUR XRUM ?????
  • When is Scrum appropriate?
    • Anarchy space: research
    • Simple space: maintenance
    • Complex space: new product development and knowledge work
    • Scrum appropriate for problems in the complex space
  • Agile estimation
    • Assign ‘size points’ to the following countries:
    • England
    • Argentina
    • Russia
    • Japan
    • Monaco
    • Costa Rica
    • The Netherlands
    • Australia
    • Kazakhstan
    • Chad