Upload
others
View
3
Download
0
Embed Size (px)
Citation preview
1 September 2009
Mature agile development using HP Quality Center
Gerald Hellersoftware process optimization
Vivit TQA webinar
September 22, 2009
Using QC with agile practices
2September 2009 Copyright © 2009 Gerald Heller
Agile fundamentals
Expectations & challenges
Quality Center for agile product development
Experiences & conclusions
2 September 2009
The agile manifesto
3 September 2009 Copyright © 2009 Gerald Heller
Source: http://www.agilemanifesto.org
Agile methods
4September 2009 Copyright © 2009 Gerald Heller
LeanFDD
DSDMASD
Crystal
Scrum
xP
3 September 2009
Agile terminology
5September 2009 Copyright © 2009 Gerald Heller
Lean-agile
Sprint
BacklogDaily Scrum
Scrum Master
Constant refactoring
Test driven development
Pair programming
Velocity
Burn down
Retrospective
Chicken
Pig
http://www.netobjectives.com/glossary
Product owner
Agile terminology – roles
6September 2009 Copyright © 2009 Gerald Heller
Lean-agile
Sprint
Backlog
Constant refactoringDaily Scrum
Test driven development
Pair programming
Velocity
Burn down
Retrospective
http://www.netobjectives.com/glossary
Scrum Master
Chicken
Pig
Product owner
4 September 2009
Lean-agile
Sprint
Daily Scrum
Scrum Master
Constant refactoring
Test driven development
Pair programming
Velocity
Burn down
Retrospective
Chicken
Pig
Product owner
Agile terminology – work to be done
7September 2009 Copyright © 2009 Gerald Heller
http://www.netobjectives.com/glossary
Backlog
Backlog unit
8September 2009 Copyright © 2009 Gerald Heller
5 September 2009
Backlog management
9September 2009 Copyright © 2009 Gerald Heller
Top Priority
Low Priority
ProductBacklog
ReleaseBacklog
In- Out Borderline
Backlog management
10September 2009 Copyright © 2009 Gerald Heller
Top Priority
Low Priority
ProductBacklog
ReleaseBacklog
Sprint Backlog
In- Out Borderline
6 September 2009
Backlog management
11September 2009 Copyright © 2009 Gerald Heller
Top Priority
Low Priority
ProductBacklog
ReleaseBacklog
Sprint Result
In- Out Borderline
Scrum overview
12September 2009 Copyright © 2009 Gerald Heller
Scrum is the most dominant agile method
7 September 2009
Expectations for agile
• Focus on highest customer value
• Be able to work on incomplete information
• Travel light
• Incremental delivery
• Visibility into progress for all parties
• Quality results as early as possible
13September 2009 Copyright © 2009 Gerald Heller
Agile development – state of practice
• Experimentation phase comes to an end
• Signals of maturity
−Siemens Nokia Networks, SAP, HP, AOL, …..
• Standardization initiative: IEEE 1648
− recommended practice for agile development
• More and more tools support agile
• Agile merged with existing practices
14September 2009 Copyright © 2009 Gerald Heller
8 September 2009
Tool expectations for agile
• Support key agile practices
• Can be tailored to needs of all stakeholders
• Provide progress and value reporting
−Based on iterations
−Based on release
• Span entire development lifecycle
15September 2009 Copyright © 2009 Gerald Heller
QC releases and cycles
16September 2009 Copyright © 2009 Gerald Heller
Product
Release
Cycle (Sprint)
9 September 2009
QC releases and cycles – details
17September 2009 Copyright © 2009 Gerald Heller
Structure of an agile project
18September 2009 Copyright © 2009 Gerald Heller
Multi-backlog management to enable Scrum-of-Scrum
First level showsbacklog and cycle folders
Items are assigned to a specific Release and Cycle
10 September 2009
Product backlog
19September 2009 Copyright © 2009 Gerald Heller
Uniq
ue B
ack
log O
rder
User Story – definition
• A User Story is a software system requirement formulated as one or two sentences in the everyday or business language of the user
− User stories are used with Agile software development methodologies for the specification of requirements
− A User Story must be small enough to be completed in one cycle
− A User Story is an informal statement of the requirement as long as the correspondence of acceptance testing procedures is lacking
20September 2009 Copyright © 2009 Gerald Heller
Wikipedia July, 2009
11 September 2009
User Story – sample properties• Name
− Meaningful to give an idea what the User Story is about
• Description− Short, understandable by all team members
− Supplied with acceptance criteria
• Priority− Supplied by backlog position
• Owner− Responsible to manage the User Story, ensure it’s properties are set
correctly, it is broken down into tasks and tasks are assigned to owners
• Estimated effort− Macro level estimate that is done before it is broken down into tasks
• Status− Describes the current situation of the User Story
22September 2009 Copyright © 2009 Gerald Heller
User Story - details
23September 2009 Copyright © 2009 Gerald Heller
High-level userstory estimate
Modeled as arequirement type
12 September 2009
Two level planning (at least)
24September 2009 Copyright © 2009 Gerald Heller
Task
siz
eUse
rst
ory
siz
eBefore Sprint Within Sprint
Cycle planning – top down
Initial high-level estimates based on User Stories prior to Sprint start
25September 2009 Copyright © 2009 Gerald Heller
User story estimates
13 September 2009
Task – sample 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).
26September 2009 Copyright © 2009 Gerald Heller
Task – in QC
27September 2009 Copyright © 2009 Gerald Heller
Task modeled as requirement type
14 September 2009
Cycle planning – bottom up
Detailedestimatesbased on tasksduring Sprint
28September 2009 Copyright © 2009 Gerald Heller
Detailed estimates based on tasks sum up to 17
High-level User Story estimate at 15 hours
Effort estimation and calculation
29September 2009 Copyright © 2009 Gerald Heller
Original Estimated Effort: Manual EntryCurrent Estimated Effort: Calculated (sum of Tasks)Actual Spent Effort: Calculated (sum of Tasks) Remaining Effort: Calculated (sum of Tasks)
Story Level
Original Estimated Effort: Manual EntryCurrent Estimated Effort: Calculated (sum of User Stories)Actual Spent Effort: Calculated (sum of User Stories)Remaining Effort: Calculated (sum of User Stories)
Cycle Level
Original Estimated Effort: Manual EntryCurrent Estimated Effort: Calculated (sum of Cycles)Actual Spent Effort: Calculated (sum of Cycles)Remaining Effort: Calculated (sum of Cycles)
Release Level
Original Estimated Effort: Manual EntryCurrent Estimated Effort: Manual EntryActual Spent Effort: Manual EntryRemaining Effort: Calculated
Task Level
15 September 2009
Effort aggregation
30September 2009 Copyright © 2009 Gerald Heller
Aggregated effort for estimates and remaining work
All items are assigned to a specific release and cycle
Sprint burn-up
31September 2009 Copyright © 2009 Gerald Heller
Available via Integrated QC Excel Reporting and QC BTO Project Dashboard.
Effort to burn down
Sprint Start Sprint End
16 September 2009
User stories to test
32September 2009 Copyright © 2009 Gerald Heller
Check filter capabilites for
best results
A) Create test from User Story B) Link test to User Story
User stories
33September 2009 Copyright © 2009 Gerald Heller
17 September 2009
Built-in coverage by cycle
34September 2009 Copyright © 2009 Gerald Heller
2 Filters need to be aligned!Coverage and View Filter
Quality User Story – fixing defects
35September 2009 Copyright © 2009 Gerald Heller
18 September 2009
Experiences
• Tool customization must match team’s experience with agile
• Team experience with agile has a strong impact on required tool customization
−Start simple
−Grow structure and process
• Harmonize across teams
• QC provides a solid base for agile development
• QC customization is prerequisite for agile success
36September 2009 Copyright © 2009 Gerald Heller
QC customization for agile• Easy
− Requirement types: User Story and Task
− Custom attributes
− Role support
− Sprint support
• Medium− Reporting
• Sprint Burn-down, burn-up
• Release Burn-down, burn-up
• Effort per engineer
• Effort calculation
• Challenging− Backlog organization
• Ordering based on unique priority
• Automatic inheritance of values from container object
• Aggregation of data
• Scrum of scrum
37September 2009 Copyright © 2009 Gerald Heller
need for thoroughdesign of
customizedsolution
increases
19 September 2009
Thank you!
Questions, feedback: contact me
Further information & news: agileQC.net
Gerald Hellersoftware process [email protected]
September 2009 38Copyright © 2009 Gerald Heller