View
4
Download
0
Category
Preview:
Citation preview
How do you measure success rate of large scale agile process?[BHAGEERATHI BAI]
2
About me..
Bhageerathi Bai, Software Quality Engineer at Intel India Pvt Ltd.
3
Our teams
Quality reviews and releases
Challenges
Solution
Success Measure
4
InternalHardware, Software,
System teams
Software and Hardware
Integrators
Third party Software and
Hardware Teams
ManufacturerComponent and Board
Manufacturers
Integration
Large Scale Agile Players…
5
A define/build/test component team
6
Large scale Agile teams distributed …
7
Our teams
Quality reviews and releases
Challenges
Solution
Success Measure
8
System1
Hardware team 1
Component 1.1
Component1.2
Software team 2
Component 2.1
Software team 3
Component 3.1
Component 3.2
Quality Assessments…
PSI Quality
9
Go/No-Go meetings..
10
Quality Assessments of Components – Pre-requisites
Define Goals/Criteria Collect Metrics Generate Assessments
capture quality trends
11
Milestone Candidate Quality review process –CUSTOMIZED
Initiate and collect data for
each criteria
Review against defined metric
for completeness
Generate Assessments
Milestone candidate
ready
ApproveAssessmen
ts
No
Raise Exceptions and track to
closure
Yes
12
Milestones
13
HW MS1 HW MS2 HW MS3 Production
Pre-prod1 Pre-prod2 Pre-prod3 Production
Hardware Milestones
Software and System Milestones
14
Our teams
Quality reviews and releases
Challenges
Solution
Success Measure
15
Customized Quality Assessments of
Individual components
16
Component Deliverables to customers in isolation
Unsynchronized release cycles
17
Our teams
Quality reviews and releases
Challenges
Solution
Success Measure
18
Tailoring large scale Agile …
19
How did we implement!!
20
Establish Common Quality
language – goals and
challenging metrics
Roll out Organization wide training plan
Mandated Common release review Process
Ensured Adoption by all the teams
21
Requirements management Feature Development Defects and customer escalations Third party Compliance Manufacturing checks Compatibility tests Customer scenarios In-house Deployment Tests Documentation … etc.
Common Quality Framework measured areas.. REVISED!!
22
Product release review process..
23
What Changed?… HW/SW Milestone Candidate Quality review process
Initiate and collect data for
each criteria
Review against defined metric
for completeness
Generate Assessments
Milestone candidate
ready
ApproveAssessmen
ts
No
Raise Exceptions and track to
closure
Yes
Criteria – Common Criteria Traction Defined Metric – More Stringent Metrics Exceptions – Close before next Milestone Milestone candidate – New Integration
Process to synchronize releases
24
HW/SW Milestone Candidate
System assessments
With latest component
releases
Milestone Declaration
Component Assessment
System wide Assessments
Ship release approval
Synchronize releases..
25
Hardware Milestones
Software and System Milestones
HW MS1 HW MS2 HW MS3 Production
Pre-prod1 Pre-prod2 Pre-prod3 Production
Dependencies were taken care…
26
Common Quality Framework ensures…
Establish Common Quality standards across organization
Prevent component team declaring release in isolation
Help ask “right” questions during ship decisions
Transparency across entire system
Central change control process
Consistency of business processes
Manage quality and risk of the product
Raise the quality bar to align with customer expectations
27
Our teams
Quality reviews and releases
Challenges
Solution
Success Measure
28
Results Stream line dependencies
and Release schedules
Team collaboration Improved
Improvement in the Quality Processes
Time to market was met as planned
Plan future releases with horizon of Predictability
Maintained zero critical exposure defects
Associated Finance Risks were in control
29
Limitations!
30
Conclusion
Delivering what customer wants
Open Communication with customer
Being trusted by customer
Synchronize Release cycles to show working software frequently
31
Questions ?
Recommended