How do you measure success rate of large scale agile process? [BHAGEERATHI BAI]
About me.. Bhageerathi Bai , Software Quality Engineer at Intel India Pvt Ltd. 2
Our teams Quality reviews and releases Challenges Solution Success Measure 3
Large Scale Agile Players… Hardware, Internal Software, System teams Software and Third party Hardware Teams Component Manufacturer and Board Manufacturers Software and Integration Hardware Integrators 4
A define/build/test component team 5
Large scale Agile teams distributed … 6
Our teams Quality reviews and releases Challenges Solution Success Measure 7
Quality Assessments… System1 Hardware Software Software team 1 team 2 team 3 PSI Quality Component Component Component Component Component 1.1 1.2 2.1 3.1 3.2 8
Go/No-Go meetings.. 9
Quality Assessments of Components – Pre-requisites Generate Assessments Define Goals/Criteria Collect Metrics capture quality trends 10
Milestone Candidate Quality review process – CUSTOMIZED Yes Initiate and Review against Milestone Approve Generate collect data for defined metric candidate Assessmen Assessments each criteria for completeness ready ts No Raise Exceptions and track to closure 11
Milestones 12
Hardware HW MS1 HW MS2 HW MS3 Production Milestones Software Pre-prod1 Pre-prod2 Pre-prod3 Production and System Milestones 13
Our teams Quality reviews and releases Challenges Solution Success Measure 14
Customized Quality Assessments of Individual components 15
Unsynchronized release cycles Component Deliverables to customers in isolation 16
Our teams Quality reviews and releases Challenges Solution Success Measure 17
Tailoring large scale Agile … 18
How did we implement!! 19
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 20
Common Quality Framework measured areas.. REVISED!! Requirements management Feature Development Defects and customer escalations Third party Compliance Manufacturing checks Compatibility tests Customer scenarios In-house Deployment Tests Documentation … etc. 21
Product release review process.. 22
What Changed?… HW/SW Milestone Candidate Quality review process Yes Initiate and Review against Milestone Approve Generate collect data for defined metric candidate Assessmen Assessments each criteria for completeness ready ts No Criteria – Common Criteria Traction Raise Exceptions Defined Metric – More Stringent Metrics and track to closure Exceptions – Close before next Milestone Milestone candidate – New Integration Process to synchronize releases 23
Synchronize releases.. System assessments HW/SW Milestone Milestone With latest Candidate Declaration component releases Component System wide Ship release Assessment Assessments approval 24
Hardware Milestones HW MS1 HW MS2 HW MS3 Production Software Pre-prod1 Pre-prod2 Pre-prod3 Production and System Milestones Dependencies were taken care… 25
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 26
Our teams Quality reviews and releases Challenges Solution Success Measure 27
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 28
Limitations! 29
Conclusion Delivering what customer wants Open Communication with customer Being trusted by customer Synchronize Release cycles to show working software frequently 30
Questions ? 31
Recommend
More recommend
