Your SlideShare is downloading. ×
Being Agile - Doing 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

Being Agile - Doing Scrum


Published on

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.

  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide
  • Transcript

    • 1. Being Agile – Doing Scrum XB Software Solutions
    • 2. 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
    • 3. 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”
    • 4. SCRUM = ACTION On your feet!
    • 5. 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.
    • 7. Scrum Foundations
      • Empiricism
      • Self Organization
      • Collaboration
      • Time Boxing
      • Prioritization
    • 8. 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
    • 9. User stories
      • Requirements:
        • As a <USER> I want <FUNCTION> so that <BUSINESS_VALUE>
      • Independent, Negotiable, Valuable, Estimable, Small, Testable
    • 10.
      • 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
    • 11. SCRUM = ACTION On your feet!
    • 12. 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
    • 13.  
    • 14. 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
    • 15. 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
    • 16. Scrum Process
    • 17. 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)
    • 18. Xrum Task Board
    • 19. 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
    • 20. Xrum Team Motivation
      • 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 .
    • 22. ????? WHAT’S YOUR XRUM ?????
    • 23. 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
    • 24. Agile estimation
      • Assign ‘size points’ to the following countries:
      • England
      • Argentina
      • Russia
      • Japan
      • Monaco
      • Costa Rica
      • The Netherlands
      • Australia
      • Kazakhstan
      • Chad