Being Agile – Doing Scrum XB Software Solutions
Agile Manifesto <ul><li>Individuals and interactions  over processes and tools </li></ul><ul><li>Working software  over co...
Scrum? <ul><li>Framework for creating your own agile process </li></ul><ul><li>Will help you fail in 30 days or less </li>...
SCRUM = ACTION On your feet!
The Ballpoints Game <ul><li>Objective: score “ball points” as a whole team </li></ul><ul><ul><li>Assign one person as the ...
EXECUTE REFLECT PLAN
Scrum Foundations <ul><li>Empiricism </li></ul><ul><li>Self Organization </li></ul><ul><li>Collaboration </li></ul><ul><li...
Feature Priorization & Emergence <ul><li>Deliver the highest value early on </li></ul><ul><li>But don’t neglect the bigger...
User stories <ul><li>Requirements: </li></ul><ul><ul><li>As a <USER> I want <FUNCTION> so that <BUSINESS_VALUE> </li></ul>...
<ul><li>Scrum is easy! </li></ul><ul><li>Simple to understand </li></ul><ul><li>Implemented in a few days </li></ul><ul><l...
SCRUM = ACTION On your feet!
Scrum Roles <ul><li>Team </li></ul><ul><ul><li>Self managing, Cross functional, Autonomous, Accountable </li></ul></ul><ul...
 
Scrum documents <ul><li>Product Backlog </li></ul><ul><ul><li>A living list of prioritized user stories </li></ul></ul><ul...
Scrum Ceremonies <ul><li>Story Time </li></ul><ul><ul><li>Discuss high priority backlog items </li></ul></ul><ul><ul><li>E...
Scrum Process
From Scrum to Xrum <ul><li>Scrum: Framework for creating your own agile process </li></ul><ul><li>Still busy finding our ‘...
Xrum Task Board
Xrum Definition of Done <ul><li>Een user story is gereed zodra: </li></ul><ul><li>De Bamboo build er niet door gebroken wo...
Xrum Team Motivation
Quotes <ul><li>Users don’t know what they want until they’re shown what they can get. </li></ul><ul><li>Fixed time  and  f...
????? WHAT’S YOUR XRUM ?????
When is Scrum appropriate? <ul><li>Anarchy space: research </li></ul><ul><li>Simple space: maintenance </li></ul><ul><li>C...
Agile estimation <ul><li>Assign ‘size points’ to the following countries: </li></ul><ul><li>England </li></ul><ul><li>Arge...
Upcoming SlideShare
Loading in …5
×

Being Agile - Doing Scrum

738
-1

Published on

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

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

No Downloads
Views
Total Views
738
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide
  • NEXT SLIDE: AGILE MANIFESTO
  • Being Agile - Doing Scrum

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

    ×