Loading…

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

Like this presentation? Why not share!

Agile intro module 3

on

  • 819 views

One day introduction to Agile and Scrum - Module 3 - Project Management

One day introduction to Agile and Scrum - Module 3 - Project Management

Statistics

Views

Total Views
819
Views on SlideShare
638
Embed Views
181

Actions

Likes
0
Downloads
6
Comments
0

1 Embed 181

http://www.improvementfocus.com 181

Accessibility

Categories

Upload Details

Uploaded via as Apple Keynote

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
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • Traditionele projecten <br /> - milestones zijn Req. rdy, Des. rdy, Coding rdy, Test rdy <br /> <br /> Agile projecten <br /> - milestones zijn Release planning, Iteration Planning, Daily Planning <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • Inspanning komt pas via Velocity in beeld <br /> Velocity = Story Point / Sprint <br /> Dus met een Velocity van 10, en Sprints van 2 weken en een team van 5 man, weet je dat de Inspanning (op dit moment) 1 dag is per Story Point <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • Eventueel in 2 teams. 1 team met eenvoudige Backlog, tweede team met feature/functional matrix. <br />
  • <br />
  • <br />
  • <br />
  • <br />
  • Cre&#xEB;er een &#x201C;sense of focus and abundance&#x201D; tijdens de sprint planning. <br />
  • Eventueel in 2 groepen: Sprint 1 en Sprint 2 <br />
  • <br />
  • <br />
  • <br />
  • Twee mogelijke uitvoeringen: <br /> - voor mij - wat moet ik met deze cursus starten/stoppen/doorgaan <br /> - voor de deelnemers - wat gaan zij morgen in hun werk doen <br /> Voorkeur voor de tweede vorm. <br />
  • Toepassing op planning: <br /> 1 <br /> - ga bij elkaar zitten tijdens release/sprint planning <br /> - leg uit wat je bedoelt met een requirement <br /> 2 <br /> - voor een sprint van 3 weken kan je veel details wel onthouden, documenteer alleen het noodzakelijke <br /> - snelle oplevering zorgt ook voor snelle leercurve voor schatten en plannen <br /> 3 <br /> - ga bij elkaar zitten ... <br /> 4 <br /> - elke nieuwe sprint kan iets volledig anders zijn dan vooraf gedacht <br />
  • Toepassing op Schatten en Plannen <br /> 1. Korte sprints, snelle feedback <br /> 2. Planning meeting - creeer gevoel van &#x201C;abundance&#x201D; <br /> 3. Technical debt <br /> 4. Prioritiseren - belangrijke zaken in vroege sprints <br /> 5. Team - self-org <br /> 6. Sprint review / retrospective, velocity <br /> 7. Continue feedback, daily-scrum, sprint review <br /> 8. Release planning / sprint planning <br /> 9. Sprint <br /> 10. Daily scrum / sprint planning <br /> 11. Self-org <br /> 12. Sprint plan, release plan, daily scrum, sprint review <br />

Agile intro   module 3 Agile intro module 3 Presentation Transcript

  • Agile Intro Module 3 Estimating & Planning 1
  • Sprint Backlog TO-DO IN WORK DONE Concepts Case Iteration Plan 2
  • Sprint Backlog TO-DO IN WORK DONE Concepts Case Iteration Plan 3
  • User Story Als een cursist Wil ik weten hoe planning in Agile projecten verloopt Omdat we zonder planning niet weten wat we moeten doen en niet weten hoe ver we zijn 4
  • Agile versus Plan-driven • Agile tegengesteld aan plan-driven? • Geen BPUF ! Maar heel veel planning. 5
  • Zes niveaus van planning strategy portfolio product release iteration day 6
  • Cone of Uncertainty grove, onnauwkeurige schatting preciese schatting 7
  • Drie niveaus van planning Op 31/10 moet de site live Release en gaat we onze applicatie verkopen As a user I want to pay Iteration with Visa card 8 Ik krijg die #$%@! Daily verbinding naar VISA niet aan de praat 8
  • Release planning • Release • >> Iteration • typically 3-6 months • date-driven or user story-driven 9
  • User story backlog Sprint 1 Sprint 2 Sprint 3 As a user ... As a user ... As a user ... 8 1 8 As a user ... As a user ... As a user ... 3 8 3 As a user ... As a user ... As a user ... 5 5 8 As a user ... 10 5
  • User story matrix Fully functional As a user ... As a user ... As a user ... 8 1 8 Fully featured As a user ... As a user ... As a user ... 1 5 3 As a user ... As a user ... As a user ... 5 5 8 As a user ... 11 5
  • User story matrix Fully functional As a user ... As a user ... As a user ... 8 1 8 Fully featured As a user ... As a user ... As a user ... 1 5 3 As a user ... As a user ... As a user ... 5 5 8 As a user ... 11 5
  • User story matrix Fully functional As a user ... As a user ... As a user ... 8 1 8 Fully featured As a user ... As a user ... As a user ... 1 5 3 As a user ... As a user ... As a user ... 5 5 8 As a user ... 11 5
  • Release planning iteration length? Release Estimate user velocity? Goal stories prioritise user stories 12
  • Story points • Waarde voor grootte / complexiteit, zonder dimensie • NIET voor inspanning / effort • Relatieve manier van schatten (x = 2y) • Meestal met (0), 1, 2, 3, 5, 8, 13, 20, 40, 100 • Start met enkele stories als baseline • Bouw een referentie-set op 13
  • Planning Poker • After story explanation, each team member picks a card • 1-2-3 turn cards • discuss High/Low • re-iterate 14
  • Sprint Backlog TO-DO IN WORK DONE Concepts Case Iteration Plan 15
  • Sprint Backlog TO-DO IN WORK DONE Concepts Case Iteration Plan 16
  • Sprint Backlog TO-DO IN WORK DONE Concepts Case Iteration Plan 17
  • User Story Als een cursist Wil ik wel eens pokeren Omdat dat wel ‘fun’ klinkt 18
  • Case - iPhone app • Stel een release planning op voor onze App • Sorteer de stories (belangrijkste links) • Definieer Release Goal • Schat story points in (voor de eerste 10-15) • Geef T-shirt maten voor de rest 19
  • Sprint Backlog TO-DO IN WORK DONE Concepts Case Iteration Plan 20
  • Sprint Backlog TO-DO IN WORK DONE Concepts Case Iteration Plan 21
  • Sprint Backlog TO-DO IN WORK DONE Concepts Case Iteration Plan 22
  • User Story Als een cursist Wil ik wel eens een Sprint Planning uitvoeren Omdat alleen theorie onvoldoende is om dit in onze organisatie toe te passen 23
  • Sprint Planning • Product Owner + Team + Experts • Create Sprint Goal • For each User Story in this iteration 1. PO clarifies story, team asks questions 2. Team (w/o PO) creates tasks, (re)estimates size (story or tasks) 24
  • Let’s practice ... • Voer een Sprint planning meeting uit 25
  • Scrum board To Do In Process Done As a user ... As a user ... As a user ... As a user ... As a user ... As a user ... As a user ... As a user ... 26
  • Sprint Backlog TO-DO IN WORK DONE Concepts Case Iteration Plan 27
  • Sprint Backlog TO-DO IN WORK DONE Concepts Case Iteration Plan 28
  • Retrospective Start doing Stop doing Continue doing 29
  • Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. 30
  • 12 principes Our highest priority is to satisfy the customer Working software is the primary 1 measure of progress. 7 through early and continuous delivery of valuable software. Agile processes promote sustainable Welcome changing requirements, even late in development. The sponsors, developers, 2 and users should be able to maintain a 8 development. Agile processes harness change for the customer's competitive advantage. constant pace indefinitely. Continuous attention to technical Deliver working software frequently, from a 3 excellence and good design enhances 9 couple of weeks to a couple of months, with a agility. preference to the shorter timescale. Simplicity--the art of maximizing the Business people and developers must work 4 amount of work not done--is essential. 10 together daily throughout the project. The best architectures, requirements, Build projects around motivated individuals. 5 and designs emerge from self-organizing teams. 11 Give them the environment and support they need, and trust them to get the job done. At regular intervals, the team reflects The most efficient and effective method of on how to become more effective, then 6 tunes and adjusts its behavior 12 conveying information to and within a development team is face-to-face conversation. accordingly. 31