AGILE SOFTWARE- ENTWICKLUNG BEI HP SOFTWARE€¦ · HP Software is Standardized on Quality Center 3...
Transcript of AGILE SOFTWARE- ENTWICKLUNG BEI HP SOFTWARE€¦ · HP Software is Standardized on Quality Center 3...
©2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice
AGILE SOFTWARE-ENTWICKLUNG
BEI HP SOFTWARE
Peter Vollmer
R&D Solution Architect - Distinguished Technologist
HP Software
26. September 2012
HP Software Development Context
Software characteristics
large portfolio of products and solutions
>20 platforms
internationalized
many integrations
huge products (xx mil. LOC)
release cycles (1 – 18 months)
long-term solutions (up to 15 years)
Different cultures
geographically
company cultures (from several acquisitions)
contractors
Software Type: Commercial of the Shelf Software (COTS)
Development Sites
2 ©2011 Hewlett-Packard Development Company, L.P.
HP Software is Standardized on Quality Center
3
• Started 2007 to align on one infrastructure and workflow
– migrated existing teams from other tools to QC
– migrated new acquisitions to QC
• HP Software is one of the biggest QC/ALM customers
– highly customized QC
– address organizational needs
– > 20.000 lines of workflow code
– various add-on tools (e.g. Agile Accelerator)
• Close relationship to QC Product Management and R&D
– feedback to current product
– feedback for missing functionality
– feedback for further innovation
ALM (Quality Center) Setup
Server farms (~ 60.000 setup Users on 3 farms)
• Centrally managed by HP IT
• Upgrade & Patches
• Stability & Performance
• Integration in IT landscape
4
ALM responsibilities are divided between HP IT and the HP Software team
Customization & Enhancements
• managed by the HP SW team (~ 4000 setup users)
• Processes & Workflow
• Add-on tools
• Support & Coaching
Reduce Waste – Increase Value
Pre-Game Mid-Game Post-Game
transferring market requirements and customer needs into features and
architecture
Planning & High-Level Design
Stabilization & Closure
Minimize Minimize Maximize
Construction
Release start Release end
Backlog line
Weekly backlogstack by severity
Release start Release end
Backlog line(scale on right side!)
Weekly In (red)Weekly Out (green)Scale on left side!
Agile Enterprise Big Picture
1/25/2011 6 ©2011 Hewlett-Packard Development Company, L.P.
Overview Release planning
Sprint management
Build cloud
Test cloud
Testing
Release monitoring
7 ©2011 Hewlett-Packard Development Company, L.P.
Sprint / Cadence
Backlog
As some projects can cope with multiple teams and manage the increasing number of user stories,
others loose overview, especially if a project gets bigger.
Managing everything on the granularity of user stories does not work very well any more.
Solution: Introduce other levels of abstraction Themes and Features.
RELEASE PLANNING - SIZE MATTERS
Playing with numbers … Assume a 6 month project with 100 engineers and 100 working days
10.000 Engineering Days [ED] Assumption: 1 User Story ~ 5 ED
2.000 User Stories
This is not really manageable in a flat structure.
Example
Theme 200 - 1000 ED (10.000/20 = 500)
Feature 1 - 50 ED
User Story 1 - 5 ED
Task few hours to days
Balance items so that you have 5-20 items on each level.
8 ©2011 Hewlett-Packard Development Company, L.P.
user story should have tangible value for a customer
SIZE MATTERS (2)
describe the release content with less than 20 themes
feature should have a major benefit to the customer
task are activities to achieve a user story
Balance items so that you have 5-20 items on each level. 9 ©2011 Hewlett-Packard Development Company, L.P.
Overview – Initial Macro Planning
The product backlog contains all known potential enhancements of the product. It’s hard to prioritize on that level as it can be very large.
Macro planning is the short and lightweight required pre-work to make sure we head into the right direction. Often this is just referenced as prioritizing the product backlog. For large products and programs in an enterprise environment this effort usually is much bigger!
transferring market requirements and customer needs into features and architecture
10 ©2011 Hewlett-Packard Development Company, L.P.
REQUIRED VIEWS
created during macro planning used for scope communication
ranking scope negotiation/cutline fulfillment tracking
Topological View Backlog View
11 ©2011 Hewlett-Packard Development Company, L.P.
Topological View
Theme
Feature
User Story Linked Defects and Tests
Various Filter & Configuration Options
Status Indicators
Efforts and Progress
Statistics
12 ©2011 Hewlett-Packard Development Company, L.P.
13 ©2011 Hewlett-Packard Development Company, L.P.
Backlog View
Same functionality as Topological View
Ranking via drag & drop
REPORTS & METRICS - RELEASE
Release Burn-up
Release Burn-down
State Transition (aka CFD)
Velocity
Release start Release end
Backlog line(scale on right side!)
Weekly In (red)Weekly Out (green)Scale on left side!
Release start Release end
Backlog line
Weekly backlogstack by severity
Release start Release end
Backlog line(scale on right side!)
Weekly In (red)Weekly Out (green)Scale on left side!
Defect Backlog Defect Flowrate Defect Resolution Time
14 ©2011 Hewlett-Packard Development Company, L.P.
HOW DO WE KNOW…
Test Agile
Defect Incident
Dashboard Information Engineering
HPSW Special Interest Groups (SIGs)
we use it ourselves perfect environment
part of a huge engineering organization charter to support these teams all kinds of development projects
from small to multi-site large scale development
frequent releases & fast feedback 33 releases in 18 months
(about every 2 weeks)
standardization driven by SIGs each SIG meets every 2-3 weeks representatives from all interested teams
… that what we implement makes sense?
HP Software – global development
15 ©2011 Hewlett-Packard Development Company, L.P.
Release Information
Story Summary View
Kanban-like visualization
Web Browser - platform independent
Links to various reports
Status changes via drag & drop
THE TASKBOARD
16 ©2011 Hewlett-Packard Development Company, L.P.
STORY SUMMARY
Backlog ordering via drag & drop
Effort & Progress QA & Documentation Status including open defects per User Story
blue bar represents original estimated effort
red background highlights blocked user stories
displays number of open defects by severity (Urgent/High/Medium/Low)
17 ©2011 Hewlett-Packard Development Company, L.P.
OWNER AND EFFORT VIEW
Owner View: View progress of each engineer
EffortView: • What did the engineer work on in the last x days? • What did s/he complete? • How much work is in progress at the same time?
18 ©2011 Hewlett-Packard Development Company, L.P.
CARDBOARD-LIKE VIEW
Create/Edit User Stories and Tasks Filter by Team/Owner/Status
Status changes via drag & drop
19 ©2011 Hewlett-Packard Development Company, L.P.
©2009 HP Confidential template rev. 12.10.09 20
REPORTS & METRICS - SPRINT
Sprint Burn-up
Sprint Burn-down
State Transition
20 ©2011 Hewlett-Packard Development Company, L.P.
Build Factory Services - from source code to installable products
21 ©2011 Hewlett-Packard Development Company, L.P.
Test Cloud
Test Cloud
# of virtual machines 1.000
# of configured templates 200
# of ESX servers 65
Avg VM's per host 15
Physical Server 180
Virtualization Rate > 80%
% of parallel running VM's 50%
Active Users 250
Users are from: Boeblingen, Bangalore, Yehud , Shanghai , Lohika
Reduce time for environment readiness
fully NAT-ed environments
- Virtual Environments Service
22 ©2011 Hewlett-Packard Development Company, L.P.
1
2
3
4
23 ©2011 Hewlett-Packard Development Company, L.P.
Test Factory
Build Factory
Test Automation
provide test environments as a service
build software automation orchestration
test automation tools automated test cases automated status collection and reporting
Build Factory
Test Automation
Test Factory
24 ©2011 Hewlett-Packard Development Company, L.P.
Build Factory
Test Automation
Test Factory
Unattended End-To-End Automation “lights-out technology”
25 ©2011 Hewlett-Packard Development Company, L.P.
Orchestration via Electric Commander
Automation Flow
(1) start build
Build Cloud
(1) build
(2) start static code analysis
(2) static
code analysis
Installable package
Code Analysis (3) acquire test environment
Test Cloud (3) acquire test
environment
(4) deploy software
(4) Deploy software
Test Workstation (QTP/EATE)
(6) trigger execution
QC
(6a) get tests
(6c) store results
(6b) execute tests
(5) make template/snapshot
Test Reports
Böblingen Unattended End - to - End Test Automation
(5) vm snapshot
Build Reports
End-To-End Automation
26 ©2011 Hewlett-Packard Development Company, L.P.
BI Based Reporting
27
• Business ScoreCard Healthiness KPIs for the SW products organization Senior Management
• TCE Cockpit
high level view on our Total Customer Experience Senior HP SW Management
• R&D ScoreCard Healthiness KPIs for the R&D organization Senior R&D Management
• R&D Project Console KPIs to monitor pre-release progress Development teams
A quarterly data validation process helps to assure data correctness.
BI Based ScoreCard
28 ©2011 Hewlett-Packard Development Company, L.P.
R&D BI Reporting Landscape
29 ©2011 Hewlett-Packard Development Company, L.P.
daily Updated
BTO Dashboard
Quality Center
ETL
ODS
Cubes
PRS SPARKS
Finance Data HR Data
Patents Data
…
Operational Data Store (ODS)
MS SSRS
Staging
ETL
ETL
updated every 20 min
Quixy/SOME
daily updated
R&D Dashboard
Provide consolidated and validated R&D data
Excel Pivot analysis/MDX clients
quarterly updated
MS SSAS
MS SSIS
Project Console BI Stack - Full automation of all metrics and reports.
SQL Clients
WHAT’S NEXT?
Application Lifecycle Intelligence (ALI)
31
ALI is a set of tools on top of ALM to support development.
1) ALI Dev provides plug-ins for various IDEs such as Eclipse, IntelliJ, MS
Visual Studio to read/write ALM entities directly from there.
2) ALI SCM provides the ability to link ALM Entities (Defects, Requirements)
to Source Code by adding
a) an auto generated check-in message and
b) adding this information to the QC Repository for further reporting and analysis. This
can also be done via the IDE.
3) Build Information integration: Connects build related information with
ALM entities.
E.g. Reports entity source code changes by build version
©2011 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice
Improve Traceability
32 ©2011 Hewlett-Packard Development Company, L.P.
Requirements/Fixes
ALI
Impact of Changes
©2011 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice
Improve Progress and Quality Monitoring with ALI
33
ALI - Data
What are we working on?
Where is currently the biggest turmoil?
Are we doing what we should do?
Progress by build version?
©2011 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice ©2012 Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice
Q&A
Peter Vollmer
R&D Solution Architect - Distinguished Technologist
HP Software
Contact: [email protected]
Q&A
BACKUP
Component vs Feature Team
37 HP Confidential
• Component team: Teams are organized around specific components or responsibilities.
• Features often impact various components.
team 1 sprint backlog
team 2 sprint backlog
team 3 sprint backlog
team 4 sprint backlog
New
Feature
A
New
Feature
B
Component vs Feature Team
38 HP Confidential
• Feature team: Teams are organized around specific features.
• Team members cover know-how of involved components.
team 1 feature backlog
New
Feature
A
New
Feature
B
team 2 feature backlog
team 3 feature backlog
Hybrid: Component & Feature Team
39 HP Confidential
• Both approaches are used within the same project.
• Very common setup for solution development and shared components.
New
Feature
A
New
Feature
B
team 1 feature backlog
team 2 feature backlog
team 3 feature backlog
team database sprint backlog