Get to CMMI ML3 Using Agile Development Processes for Large Projects. Catherine Clark, Business Solutions Architect

Transcription

1 Get to CMMI ML3 Using Agile Development Processes for Large Projects Catherine Clark, Business Solutions Architect

2 Can CMMI and Agile complement each other? 2

3 Can CMMI and Agile complement each other? Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. 3

4 Can CMMI and Agile complement each other? Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. 4

5 Can CMMI and Agile complement each other? Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. 5

6 Can CMMI and Agile complement each other? Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. 6

7 Waterfall Method Project Lifecycle Correction 7

8 Waterfall Method Project Lifecycle Correction Bug Reports Release Notes Requirements Traceability Matrix 8

9 Agile Method Project Lifecycle 9

10 Agile Method Project Lifecycle 10

11 Agile Method Bug Reports Bug Reports Bug Reports Project Lifecycle 11

12 Agile Method Bug Reports Bug Reports Bug Reports Release Notes Release Notes Release Notes Project Lifecycle 12

13 Agile Method Requirements Traceability Matrix Bug Reports Bug Reports Bug Reports Release Notes Release Notes Release Notes Project Lifecycle 13

14 Can CMMI and Agile complement each other? How can this be achieved while still being Agile and keeping the developers focused on: Individuals and interactions Working software Customer collaboration Responding to change 14

15 Two parts of the CMMI appraisal process Evidence Direct Indirect Affirmations/Interviews 15

16 Two parts of the CMMI appraisal process Evidence Affirmations/Interviews 16

17 Affirmations/Interviews Interviews are fashioned to fill in any blanks that the evidence didn t show, or was unclear Daily scrums are critical in ensuring all of the teams are aware of the process 17

18 Two parts of the appraisal process Evidence Interviews 18

19 How do you generate evidence while keeping the team actively engaged in producing working software? Use the tools they are already using every day 19

20 How do you generate evidence while keeping the team actively engaged in producing working software? Use the tools they are already using every day and adjust and integrate them to maintain the documentation required for CMMI evidence 20

21 Agile/CMMI Process User Stories and Tasks are kept in Rally. 21

22 Agile/CMMI Process User Stories and Tasks are kept in Rally. and are written in Eclipse and stored via Subversion. When committing, Rally will store a link to the. 22

23 Agile/CMMI Process User Stories and Tasks are kept in Rally. and are written in Eclipse and stored via Subversion. When committing, Rally will store a link to the. Automated reside in Jenkins, Rally can integrate and correlate them to the User Stories 23

24 Agile/CMMI Process User Stories and Tasks are kept in Rally. Bug Reports and are written in Eclipse and stored via Subversion. When committing, Rally will store a link to the. Automated reside in Jenkins, Rally can integrate and correlate them to the User Stories Defects are kept in Rally, and can point back to in Jenkins. 24

25 Agile/CMMI Process User Stories and Tasks are kept in Rally. Bug Reports Release Notes and are written in Eclipse and stored via Subversion. When committing, Rally will store a link to the. Automated reside in Jenkins, Rally can integrate and correlate them to the User Stories Defects are kept in Rally, and can point back to in Jenkins. Release notes are stored within the Release in Rally. Each User Story points to the code affected, as well as the Defects. 25

26 Agile/CMMI Process User Stories and Tasks are kept in Rally. Bug Reports Release Notes Requirements Traceability Matrix and are written in Eclipse and stored via Subversion. When committing, Rally will store a link to the. Automated reside in Jenkins, Rally can integrate and correlate them to the User Stories Defects are kept in Rally, and can point back to in Jenkins. Release notes are stored within the Release in Rally. Each User Story points to the code affected, as well as the Defects. The integration of these four tools allow a quick and easy way to trace from Requirement (User Story) to and, to Defects and, and to the Release. 26

27 Agile/CMMI Process Bug Reports Release Notes Requirements Traceability Matrix? User Stories and Tasks are kept in Rally. and are written in Eclipse and stored via Subversion. When committing, Rally will store a link to the. Automated reside in Jenkins, Rally can integrate and correlate them to the User Stories Defects are kept in Rally, and can point back to in Jenkins. Release notes are stored within the Release in Rally. Each User Story points to the code affected, as well as the Defects. The integration of these four tools allow a quick and easy way to trace from Requirement (User Story) to and, to Defects and, and to the Release. 27

28 Questions? Catherine Clark Business Solutions Architect