Bruk av HP Quality Center med smidige utviklingsmetoder Kjell Lillemoen HP Sofware Norge
QC og smidige metoder Agenda Smidig terminologi Smidig metoder og verktøy Hvilke krav bør vi stille QC med Scrum 2 4 February 2009
The agile manifesto 3 July 15, 2008 Source: http://www.agilemanifesto.org
Agile Methods xp Backlog Lean DSDM Crystal Scrum ASD 4 July 15, 2008
Smidig Terminologi Sprint Test driven development Velocity Chicken Pig Backlog Lean-agile Burn down Daily Scrum Constant refactoring Retrospective Product owner Pair programming Scrum Master 5 July 15, 2008 http://www.netobjectives.com/glossary
Metodikk Scrum Selvstyrt og selvorganiserte grupper Hver iterasjon (Sprint) med tilhørende omfang blir totalt frosset Daglig stand-up (Scrum-møte) 30-kalenderdagers iterasjoner Demo til mottaker/kunde ved slutten på hver iterasjon 6 July 15, 2008
Forventninger ved bruk verktøy med smidige metoder Må støtte sentrale praksiser i forhold til smidige metoder Mulig å tilpasse til en gruppes behov Bør kunne brukes av alle i gruppen Må gi rapportering på progresjon og øyeblikksbilde basert på iterasjoner basert på release 7 July 15, 2008
Backlog unit 8 July 15, 2008
Backlog management Top Priority Sprint Backlog Result Product Backlog Release Backlog In- Out Borderline Low Priority 9 July 15, 2008
Scrum overview Scrum er i senere år mye brukt i HP R&D 10 July 15, 2008
Hva trenger vi for å kunne støtte Scrum Entiteter Product backlog Requirment Sprint backlog Tasks Aktiviteter Backlog managment Bryte ned krav til tasks Overgang fra product til Sprint backlog Rapportering Release Burn-up/Burndown graf Sprint Burn-up/Burn-down testdekning Ekstra Smidighet Fleksibilitet Nødvendige beslutninger Hvor skal produk og sprint backlog plasseres Hvordan strukturere produkt release og sprint Hva er påkrevde felt for hver entitet Hva er påkrevd funksjonalitet/oppførsel Beste oppsett for nødvendige rapporter
QC Agile Støtte for HP Software Introduserer entitetene: User Story og Task Effort calculation Backlog organsiering Automatisk arv av nøkkelverdier i en trestruktur via drag & drop backlog sortering Rapporter (project dashboard & Excel report generator) Efforts pr. utvikler Sprint Burn-up graf Release Burn-up burn-down Cycle progresjon Release progresjon Mulighet for støtte av story points real efforts scrum of scrum (multi-team utvikling) 12 July 15, 2008
QC releases and cycles Product Release Cycle 14 July 15, 2008
Structure of an Agile Project Multi-Backlog handling for enabling Scrum-of-Scrum First Level contains Backlogs and Cycles All items are assigned to a specific Release and Cycle Aggregated Effort for Estimates, Actuals and Remaining 15 July 15, 2008
Product backlog Unique Backlog Order 16 July 15, 2008
Two Level Planning (at least) Before Sprint User story size Task size Within Sprint 17 July 15, 2008
Cycle planning top down High level initial estimates based on user stories before the Sprint begins User story estimates 18 July 15, 2008
User Story Example User story modellert som en requirement type 19 July 15, 2008
Cycle planning bottom up Detailjerte estimater er basert på tasks i løpet av en Sprint Overordnet user story estimat på 40 timer Detailjert estimate basert på tasks blir summert til 56 20 July 15, 2008
Task in QC Task modellert som requirement type 21 July 15, 2008
Effort estimat og kalkulasjon Release Level Original Estimated Effort: Current Estimated Effort: Actual Spent Effort: Remaining Effort: Manual Entry Calculated (sum of Cycles) Calculated (sum of Cycles) Calculated (sum of Cycles) Cycle Level Original Estimated Effort: Current Estimated Effort: Actual Spent Effort: Remaining Effort: Manual Entry Calculated (sum of User Stories) Calculated (sum of User Stories) Calculated (sum of User Stories) Story Level Original Estimated Effort: Current Estimated Effort: Actual Spent Effort: Remaining Effort: Manual Entry Calculated (sum of Tasks) Calculated (sum of Tasks) Calculated (sum of Tasks) Task Level Original Estimated Effort: Current Estimated Effort: Actual Spent Effort: Remaining Effort: 22 July 15, 2008 Manual Entry Manual Entry Manual Entry Calculated
Effort aggregering All items are assigned to a specific target Release and Cycle 23 July 15, 2008 Aggregated Effort for Estimates, Actuals and Remaining
Sprint Burn-up Effort to burn down Available via Integrated QC Excel Reporting and QC Sprint Start BTO Project Dashboard. 24 July 15, 2008 Sprint End
Release Burn-Up Effort [ED] added to backlog removed from backlog current estimated effort Spent effort for this cycle actual spent effort Sprint 1 25 July 15, 2008 Spent effort for all previous cycles Remaining Estimated Effort Sprint 2 Sprint 3 Sprint 4
Effort Per Engineer 26 July 15, 2008
Testdekning pr. Sprint (cycle) 27 July 15, 2008
Suksesskriterier Start smidig - i det små med en piliot Kontinuerlig Intern forbedring/leveranse støtte coaching og consulting Rammeverkstilnærming Mest Støtte (Bruk det du trenger) mulig testautomasjon fra HP Software med partnere
HP Software Services Agile Blueprint PPM PPM Manage enterprise level resources and time management Manage the portfolio strategy Manage the projects Summary Reporting Process enforcement Center Quality Quality Center 29 Manage the requirements Manage user stories and tasks Manage the backlog Reporting (burn down charts etc ) Testing - definition and execution Defect management Manage Sprints / Iterations
HP Software Services Agile Deployment QC Services Fields and Attributes Customization PPM Services Implement Proposal Process Implement Resource Management Custom Requirements Types Module Data Storage Structures Implement Time Management Release and Cycle Management for SPRINT support Implement MAC Integration with SM and QC Requirements User Role Configuration Custom Workflow and Field Transition Rules Custom Reports
Oppsummering Datamodell og workflow tilpasning Supplerende Bruk rapportering av malprosjekt Integrert løsning med test og defect managment Verdi på løsningen: Kombinasjon av verktøy tett involvering fra brukere, forbedringer og coaching Smidige metoder kan brukes på mange forskjellige måter QC må reflektere den enkeltes organisasjon implementering f.eks Scrum
Spørsmål & Svar