This presentation provides an overview of Agile and CMMI, including common misconceptions and a comparison of the two methodologies. You will leave the presentation with a better understanding of how to apply CMMI when using Agile.

1. Apply Agile in a CMMI World
Pat Eglin
p.eglin@davidconsultinggroup.com

2. Agenda
• What is Agile?
– Characteristics
– Methods
• What is CMMI?
– Characteristics
• Common Misconceptions
• Quick Agile/CMMI Comparison
• CMMI PA/Agile Comparison
©2013 David Consulting Group 1

3. What is Agile?
• Agile is a toolbox containing various methods
– Xp, Scrum, FDD, Crystal, etc. (tools)
• It is a way to deliver software on a continuous basis
• It focuses on completing those tasks which provide
the most value
• It allows for changing requirements, even late in the game
• It promotes daily collaboration
• It facilitates continuous process improvement
©2013 David Consulting Group 2

4. Characteristics of Agile
• Adaptive – allows for change in development focus
• Flexibility – sounds adaptive; focuses on the outcome of the iterations
over the plan
• Collaboration – across multiple reporting levels
• Self Organization – within teams
• Iterative and incremental – often and in short cycles
• Agile Manifesto:
– Individuals and interactions over processes and tools
– Working software over comprehensive documentation
– Customer collaboration over contract negotiation
– Responding to change over following a plan
©2013 David Consulting Group 3

5. Agile Misconceptions
• Ad-Hoc
• No Process
• No Documentation
• No Repeatability
©2013 David Consulting Group 4

6. What is CMMI?
• CMMI is a process improvement approach.
• CMMI is a framework that identifies best practices – what
planning, process, development and support practices organizations
should implement to improve quality and delivery of products.
• CMMI is a model that provides guidance for developing processes. It
identifies what actions an organization should be performing in the
areas of Process Management, Project Management, Engineering and
Support Functions.
• CMMI is descriptive, not prescriptive.
• According to the Software Engineering Institute (SEI, 2008), CMMI
helps "integrate traditionally separate organizational functions, set
process improvement goals and priorities, provide guidance for quality
processes and provide a point of reference for appraising current
processes."
©2013 David Consulting Group 5

7. Characteristics of CMMI
©2013 David Consulting Group 6

8. Quick Agile/CMMI Comparison
Characteristics xP Scrum FDD CMMI
Development Iterative Iterative Iterative Project Planning
Approach
Time Period 1-6 weeks 2-4 weeks Days-2 weeks Project Planning
(Iteration)
Teams Small Small Medium-Large Organizational
Process
Definition
Project Planning
Communication Daily Stand- Daily Stand-up Documentation - Project Planning
up Meetings Meetings based Project
Monitoring and
Control
Customer Often Often Often Integrated Project
Management
Involvement
Documentation Basic Basic Heavier All Process Areas
©2013 David Consulting Group 7

9. CMMI Process Area – Agile Documentation
Comparison
Level 2 & 3 Process Area PA Description….In 10 words or less AGILE
Organizational Process Definition Document processes Document agile approach (SCRUM, Kanban, XP)
Organizational Process Focus Determine process improvement needs Team retrospectives- team determined improvements
Organizational Training Train resources for their roles Independent of development methodology- train on AGILE
Integrated Project Management Coordinate teams, schedules, resources SCRUM of SCRUMS, release plans, team construction, iteration cadence
Project Monitoring and Control Update the schedule and plans update backlogs, hours, taking corrective action
Project Planning Create a budget and schedule, plan for resources backlogs, release plans, team construction, budget
Requirements Management Track changes to requirements updated backlogs, customer feedback, demos
Risk Management Identify and manage risks release planning, iteration planning
Supplier agreement Management Buy goods from suppliers Independent of development methodology, backlog item
Product Integration Build the product Development
Requirements Development Gather Requirements Creation of backlogs, stories, customer feedback, demos
Technical Solution Design Design, Architecture
Validation Are we satisfying the requirements Demos, testing
Verification Peer Review/Test standups, demos, testing
Configuration Management Control configuration items Independent of development methodology
Decision Analysis and Resolution Document formal decisions backlogs, iteration planning, release planning, meeting minutes
Measurement and Analysis Gather/report metrics burndowns, velocity, team iteration planning
Process and Product Quality Assurance Ensure processes are being followed independent of development methodology
©2013 David Consulting Group 8

10. Contact Us
Email: p.eglin@davidconsultinggroup.com
Phone: 1-610-644-2856, ext 21
http://www.davidconsultinggroup.com
@DavidConsultGrp
/DavidConsultGrp
/company/David-Consulting-Group
©2013 David Consulting Group 9