What CMMi means for smaller organizations or any startups.

1. CMMi Journey @ small
organizations
Jyoti CHOPRA

2. Process improvement of any kind requires a
considerable investment of time and money on
the part of the organizations that decide to
pursue it.

3. How Do You Want to Work – Option 1?
Random motion – lots of energy, not much
progress
No teamwork – individual effort
Frequent conflict
You never know where you’ll end up

4. How Do You Want to Work – Option 2?
Working with CMMi
Directed motion – every step brings you closer to
the goal
Coordinated efforts
Cooperation
Predictable results

5. Why focus on Processes
• It complements your focus
– on technology
– On people
Work hard -> Work smart

6. Common Myths
• I don’t need process, I have
– Really good people
– Advanced technology
– An experienced Manager
• Process…
– Interferes with creativity
– Isn’t needed when building small Applications
– Is only useful in large Projects
– Costs too much
– Slow down the delivery

7. CMMi is not the PROCESS.
CMMi is set of industry BEST PRACTICES.
CMMi model describes the
characteristics of effective Processes.

8. The Capability Maturity Model
Integration is a suit of products used to
improve Processes.

9. 5 Maturity levels in the CMMI

10. Another view of CMMi

11. The Five-Stage Capability Maturity
Model (CMMI)
There are five defined stages,
1. Ad-hoc / crises. Your organization has few common processes. The success
of your projects depends on the strength and skills of your people. The
organization provides little in a supporting environment to help make all
projects successful. Most companies are at this level; although some
companies say half-jokingly that they are at a 0 or even a -1 level.
1. Standard project management. Your organization has implemented
standard project management processes, and you utilize these common
processes on all projects. You are trying to establish a baseline foundation
upon which to improve further in the future. Most companies that start
down the CMMI path are trying to reach this level.

12. The Five-Stage Capability Maturity
Model (CMMI)
3. Standard software development. You are trying to achieve
standardization in your development process similar to what you did
for project management in level 2. This includes common and
repeatable software development processes, deliverables, tools, etc.
4. Managed feedback. You collect metrics on all aspects of your
project management and development processes. you have a
repository of metrics and key learnings on historical projects that can
be leveraged by new projects.
5. Optimizing / continuous improvement. you have a closed loop of
process execution, measurement and continuous improvement. You
continuously use measurement, feedback and creativity to optimize
your processes.

13. Is there any PAIN involved in the
Journey
There is pain involved
with all culture change
initiatives when you ask
people to change how
they do their JOBS

14. The pain can definitely be worth the gain, if the
organization can stay focused for the time it will
take for the culture change to take effect.

15. Why CMMi …?
COST : Reductions in the cost to find and fix
a defect, and overall cost savings
SCHEDULE : Less time needed to complete
tasks and increased predictability in
meeting schedules
QUALITY : Measured improvements in
quality, mostly related to reducing defects
over time or by product life cycle

16. Few more ….
CUSTOMER SATISFACTION :
Improvements in customer
satisfaction, including
demonstration of customer
satisfaction through award fees.
RETURN ON INVESTMENT : Positive
returns on investment from CMMI-
based process improvement.

17. Few benefits and impacts
• Better Project Management
• Better Quality Products ( Software )
Model of CMMi impact

18. Glimpses of Journey ahead …
 Project Management
 Requirement Management + Change Management
 Technical and Management Reviews
 Code standardization and best practices
 Software Configuration Management process and Practices
 Testing and tools
 Defect Management System and tools

19. Few Deliverables…
REPORTS

20. It’s so much more than merely
improving software processes.