1 1 Agile Using QC

Supporting agile development with QualityCenter 9.
2
Using HP Quality Center with Agile Practices
Using QC 9.2 with agile practices

Agile fundamentals, SCRUM Agile development in HP Tool expectations for agile support Using QC 9.2 for agile product development Experiences, conclusions
November 2008
HP Test User group, Copenhagen
Page 1
HP test user group Copenhagen - Denmark
November 2008
The agile manifesto
Source: http://www.agilemanifesto.org
3 November 2008 HP Test User group, Copenhagen
Agile methods and

xP FDD Scrum DSDM ASD Lean
Crystal
Page 2
November 2008
practices
Scrum
Self-directed and self-organizing teams Each iteration (Sprint) scope is totally frozen Daily stand-up (the Scrum meeting) 30-calendar-day iterations Demo to external stakeholders at the end of each iteration
XP
Whole team Pair programming Constant refactoring Test-driven development
Agile terminology
Sprint
Velocity Chicken
Test driven development

Pig Backlog
Lean-agile
Burn down Daily Scrum Retrospective Scrum Master
http://www.netobjectives.com/glossary
Constant refactoring
Product owner
Pair programming
Page 3
November 2008
Agile terminology roles

Sprint Velocity Test driven development Pig Backlog Lean-agile Burn down Daily Scrum Retrospective Product owner Pair programming
Chicken
Scrum Master
Agile Terminology work to be done

Sprint Velocity Chicken
Test driven development

Pig Backlog
Lean-agile
Burn down Daily Scrum Retrospective Scrum Master
Product owner
Pair programming
Page 4
November 2008
Backlog unit
November 2008
Backlog management
Top Priority
Sprint Backlog Result
Release Backlog Product Backlog In- Out Borderline
Low Priority
10
November 2008
Page 5
November 2008
Backlog management
Top Priority
Product Backlog
Low Priority
11
November 2008
Backlog management
Top Priority
Release Backlog Product Backlog In- Out Borderline
Low Priority
12
November 2008
Page 6
November 2008
Backlog management
Top Priority
Sprint Backlog Release Backlog
Product Backlog In- Out Borderline
Low Priority
13
November 2008
Backlog management
Top Priority
Sprint Result Release Backlog
Product Backlog In- Out Borderline
Low Priority
14
November 2008
Page 7
November 2008
Scrum overview
Scrum is used widely in HP since years
15
November 2008
Agile development within HP

More than 21% of HP projects use agile approaches Several methods in use: xP, Scrum, lean, ..
Rapidly growing community Sponsored by HP corporate

Training curriculum set up and available across the company Experience sharing: forums, webinars and reports
Data from HP agile sig (2006)
16
November 2008
Page 8
November 2008
Disclaimer
The following material elaborates
one possibility
how to develop agile with QC There are
other ways
to do this in QC depending on the needs of agile teams
17
November 2008
Tool expectations for agile

Must support key agile practices Can be tailored to team needs Can be used by all members of agile team Must provide progress and value reporting
based on iterations
based on release
18
July 15, 2008
Page 9
November 2008
QC releases and cycles
Product Release Cycle (Sprint)
19
November 2008
QC releases and cycles details
20
November 2008
Page 10
November 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
21
November 2008
Product backlog
22
November 2008
Page 11
Unique Backlog Order
November 2008
User Story definition
A user story is a software system requirement formulated as one or two sentences in the everyday language of the user.
User stories are used for the specification of requirements together with acceptance tests in the software engineering method Extreme Programming (XP) Less than 3 week of work
Wikipedia May 15, 2006

User Story how we use it
A user story is used to organize all development activities that are required in order to produce the desired product. It can be
A product requirement E.g.: Console runs with Mozilla Firefox web browser An internal deliverable E.g.: Investigate use of technology X A container for any kind of tasks E.g.: Integrate all component tests into the build .
Each user story is broken down into tasks A user story must be small enough that it can be completed in one cycle
November 2008 HP Test User group, Copenhagen
24
Page 12
November 2008
User Story key properties

Name
meaningful to give an idea what the user story is about
Description
understandable by all project members leaves no ambiguity about the customers expectations and the exact result of the implementation
Fit Criteria (Acceptance Test):

describes a precise scenario to show that the User Story is working
Owner:
responsible to manage the user story, ensure its properties are set correctly, it is broken down into tasks and tasks are assigned to owners
Original estimated effort:

macro level estimate that is done before it is broken down into tasks
Tasks:
list of tasks that are necessary to create what is described in the user story
25
November 2008
User Story - details
Modeled as a requirement type
High level user story estimate
26
November 2008
Page 13
November 2008
Two level planning (at least)

User story size
27
November 2008
Cycle planning top down
High level initial estimates based on user stories before the Sprint begins
Task size
Before Sprint
Within Sprint
User story estimates
28
November 2008
Page 14
November 2008
Task key properties

Name
meaningful to describe the task
Description
if the name is not self descriptive, explain here in more detail what the task is about
Owner
responsible to implement the task
Effort Estimates
Original Estimated Effort: detailed original estimate for the task, will never be updated once set Current Estimated Effort: overall effort estimate for the task; initially set to the original estimated, but is updated as the owner learns more about the tasks
Actual Spent Effort: how much is already spent on the task, should be updated daily
Remaining Effort: is calculated
Origin:
How was the task added? As part of the task breakdown of the user story (Planned) or discovered during the work on the user story (Discovered).
29
November 2008
Task in QC
Task modeled as requirement type
30
November 2008
Page 15
November 2008
Cycle planning bottom up

Detailed estimates are based on tasks during Sprint
High level user story estimate at 40 hours
Detailed estimates based on tasks sum up to 56
31
November 2008
Effort estimation and calculation

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:
Manual Entry Manual Entry Manual Entry Calculated
Page 16
November 2008
Effort aggregation
All items are assigned to a specific target Release and Cycle
Aggregated Effort for Estimates, Actuals and Remaining
33
November 2008
Sprint burn-up
Effort to burn down
Available Start Sprint via Integrated QC Excel Reporting and QC BTO Project Dashboard.
Sprint End
34
November 2008
Page 17
November 2008
Release burn-up
35
November 2008
Built in coverage by cycle
2 Filters need to be aligned! Coverage and View Filter
36
November 2008
Page 18
November 2008
Quality user story fixing defects
Work left
37
November 2008
Experiences
Team experience with agile has a large impact on the tool customization
Start simple Grow structure and process
Quality Center has a solid base to start agile Quality Center allows flexible adaptations
38
November 2008
Page 19
November 2008
QC agile support for HP Software

Introduced types: User Story and Task Effort calculation Backlog organization
automatic inheritance of key values in tree via drag & drop backlog reordering Reports (project dashboard & Excel report generator) Efforts per Engineer Sprint Burn-up graph Release Burn-up burn-down Cycle progress Release progress
Framework supports
story points real efforts scrum of scrum (multi team development)
39
November 2008
Summary: QC agile support

Must support key agile practices E.g. Scrum: Sprint, Backlog, User story Can be tailored to team needs Tasks, estimation, planning, spent hours Can be used by all members of team Product manager, project engineers, system tester Must provide progress and value reporting Project and sprint progress via burn-up charts, coverage
40
November 2008
Page 20
November 2008
Thank you!
Q&A
41
November 2008
Supporting agile development with QualityCenter 9.2

Gerald Heller, HP Software, gerald.heller@hp.com December 1st, 2008: gerald.heller@swq4all.de
Page 21
November 2008
Backlog cycle planning and tracking

1. 2. 3. 4. 5.
Initially estimate effort based on User story Add tasks to User story Add details to tasks Estimate the tasks (original estimate) Track spent effort on task level
43
November 2008
Page 22
November 2008

1 1 Agile Using QC

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1 1 Agile Using QC

Uploaded by

Copyright:

Available Formats

Supporting agile development with QualityCenter 9.

Using QC 9.2 with agile practices

HP Test User group, Copenhagen

HP test user group Copenhagen - Denmark

The agile manifesto

Agile methods and

HP test user group Copenhagen - Denmark

Test driven development

HP test user group Copenhagen - Denmark

Agile terminology roles

Agile Terminology work to be done

Test driven development

HP test user group Copenhagen - Denmark

HP Test User group, Copenhagen

Sprint Backlog Result

Release Backlog Product Backlog In- Out Borderline

HP Test User group, Copenhagen

HP test user group Copenhagen - Denmark

HP Test User group, Copenhagen

Release Backlog Product Backlog In- Out Borderline

HP Test User group, Copenhagen

HP test user group Copenhagen - Denmark

Sprint Backlog Release Backlog

Product Backlog In- Out Borderline

HP Test User group, Copenhagen

Sprint Result Release Backlog

Product Backlog In- Out Borderline

HP Test User group, Copenhagen

HP test user group Copenhagen - Denmark

Scrum is used widely in HP since years

HP Test User group, Copenhagen

Agile development within HP

Rapidly growing community Sponsored by HP corporate

Data from HP agile sig (2006)

HP Test User group, Copenhagen

HP test user group Copenhagen - Denmark

HP Test User group, Copenhagen

Tool expectations for agile

July 15, 2008

HP test user group Copenhagen - Denmark

QC releases and cycles

Product Release Cycle (Sprint)

HP Test User group, Copenhagen

QC releases and cycles details

HP Test User group, Copenhagen

HP test user group Copenhagen - Denmark

Structure of an agile project

First Level contains Backlogs and Cycles

All items are assigned to a specific Release and Cycle

Aggregated Effort for Estimates, Actuals and Remaining

HP Test User group, Copenhagen

HP Test User group, Copenhagen

HP test user group Copenhagen - Denmark

Unique Backlog Order

User Story definition

Wikipedia May 15, 2006

User Story how we use it

HP test user group Copenhagen - Denmark

User Story key properties

Fit Criteria (Acceptance Test):

Original estimated effort:

HP Test User group, Copenhagen

User Story - details