How do you measure success rate of large scale agile process? [BHAGEERATHI BAI]

Size: px
Start display at page:

Download "How do you measure success rate of large scale agile process? [BHAGEERATHI BAI]"

Transcription

1 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. 2

3 Our teams Quality reviews and releases Challenges Solution Success Measure 3

4 Large Scale Agile Players Internal Hardware, Software, System teams Third party Software and Hardware Teams Manufacturer Component and Board Manufacturers Integration Software and Hardware Integrators 4

5 A define/build/test component team 5

6 Large scale Agile teams distributed 6

7 Our teams Quality reviews and releases Challenges Solution Success Measure 7

8 Quality Assessments System1 Hardware team 1 Software team 2 Software team 3 PSI Quality Component 1.1 Component 1.2 Component 2.1 Component 3.1 Component 3.2 8

9 Go/No-Go meetings.. 9

10 Quality Assessments of Components Pre-requisites Define Goals/Criteria Collect Metrics Generate Assessments capture quality trends 10

11 Milestone Candidate Quality review process CUSTOMIZED Initiate and collect data for each criteria Review against defined metric for completeness Generate Assessments Approve Assessmen ts Yes Milestone candidate ready No Raise Exceptions and track to closure 11

12 Milestones 12

13 Hardware Milestones HW MS1 HW MS2 HW MS3 Production Software and System Milestones Pre-prod1 Pre-prod2 Pre-prod3 Production 13

14 Our teams Quality reviews and releases Challenges Solution Success Measure 14

15 Customized Quality Assessments of Individual components 15

16 Unsynchronized release cycles Component Deliverables to customers in isolation 16

17 Our teams Quality reviews and releases Challenges Solution Success Measure 17

18 Tailoring large scale Agile 18

19 How did we implement!! 19

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 20

21 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

22 Product release review process.. 22

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 Approve Assessmen ts Yes Milestone candidate ready Criteria Common Criteria Traction Defined Metric More Stringent Metrics Exceptions Close before next Milestone Milestone candidate New Integration Process to synchronize releases No Raise Exceptions and track to closure 23

24 Synchronize releases.. HW/SW Milestone Candidate System assessments With latest component releases Milestone Declaration Component Assessment System wide Assessments Ship release approval 24

25 Hardware Milestones HW MS1 HW MS2 HW MS3 Production Software and System Milestones Pre-prod1 Pre-prod2 Pre-prod3 Production Dependencies were taken care 25

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 26

27 Our teams Quality reviews and releases Challenges Solution Success Measure 27

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 28

29 Limitations! 29

30 Conclusion Delivering what customer wants Open Communication with customer Being trusted by customer Synchronize Release cycles to show working software frequently 30

31 Questions? 31