• Save
Upcoming SlideShare
Loading in...5




A 2003 version of Introduction to CMM to small and medium sized IT Service Companies.

A 2003 version of Introduction to CMM to small and medium sized IT Service Companies.



Total Views
Views on SlideShare
Embed Views



2 Embeds 6

http://www.linkedin.com 5
http://www.slideshare.net 1



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

Firststeps Firststeps Presentation Transcript

  • Birds Overview to CMM What you should know
        • Success is defined as projects delivered on time, within budget, and with specified functionality which was achieved in only 28% of projects
        • another 49% were completed but delivered late, over budget or with fewer features and functions than originally specified
        • the remaining 23% of projects completely failed or were cancelled.
        • Source Research Report Standish Group in 2001
  • Why do projects Fail
    • Many developers don't actually know much about the nature of the business(es) that will be using their software.
    • This often means spelling out the obvious using some kind of Business Process diagramming and using that to clarify requirements.
    • Many young developers lack the understanding of words “Quality”, “Process” and don’t work in structured way.
  • Why do projects Fail ..
    • Project Planning if done is just to satisfy the clients in Small IT Organizations and Partially done in Mid-sized organizations.
    • Software Developers think it is boring to do business modeling or design and jump to do only Coding.
    • Most of the projects are led by Senior programmers and not by Trained Project Managers.
  • What’s Next for me.
    • Deming’s continuous improvement cycle
      • Plan
      • Do
      • Check
      • Act
  • What to Plan?
    • Plan a process
    • Freeze Standards
    • Set Examples on why projects fail
    • Plan a Certification
  • What to Do?
    • Give motivating lectures
    • Create Templates
    • Train your project teams on Project Management and Project Planning.
  • What to Check?
    • if people understood the procedures and processes
    • if processes and procedures are being used by team in the projects
    • Improvement in projects
  • Act
    • revise your plans if required.
    • Else plan more examples, training
    • If every thing is as expected then time for Project Management “Beyond first steps for software projects”.
  • First Steps
    • Understand what Process is and Map to where you are on process Road Map
  • What is CMM?
    • CMM stands for Capability Maturity Model.
    • CMM describes the principles and practices underlying software process maturity.
  • CMM Levels
    • Level 1 : Initial
    • Level 2 : Repeatable
    • Level 3 : Defined
    • Level 4 : Managed
    • Level 5 : Optimizing
  • Key Process Areas
    • Starting from a base of ad hoc, chaotic processes,
    • each level focuses on a series of Key Process
    • Areas (KPAs) which, when improved, enable an
  • Key Process Areas
    • organisation to advance to the next level of maturity.
    • Each KPA is composed of a series of critical practices
    • that must be in place to satisfy process goals.
  • Key Process Areas
    • These practices describe the activities and
    • infrastructure needed to ensure the effective
    • implementation and assimilation of the KPA.
  • Level 1 : Initial
    • The software process is characterized as ad hoc, and occasionally even chaotic.
    • Few processes are defined, and success depends on individual effort.
  • KPA : Level 1
    • No KPAs
  • Level 2 : Repeatable
    • Basic Project management processes are established to track
      • costs,
      • schedule and
      • functionality.
    • The necessary process discipline is in place to repeat earlier successes on projects with similar applications.
  • KPA : Level 2
    • Requirements Management
    • Project Planning
    • Project Tracking & Oversight
    • Sub Contract Management
    • Quality Assurance
    • Configuration Management
  • Level 3 : Defined
    • The software process for both management and engineering activities is
      • documented,
      • standardized and
      • integrated
    • into an organization-wide software process.
  • Level 3 : Defined
    • All projects use a documented and approved version of the organization’s process for developing and maintaining software.
    • This level includes all characteristics defined for level 2.
  • KPA : Level 3
    • Organisation Process Focus
    • Organisation Process Definition
    • Training Program
    • Integrated Software Management
    • Software Product Engineering
    • Inter group Coordination
    • Peer Reviews
  • Level 4 : Managed
    • Detailed measures of the software process and product quality are collected.
    • Both the software process and products are quantitatively understood and controlled using detailed measures.
    • This level includes all characteristics defined for level 3.
  • KPA : Level 4
    • Quantitative Process Management
    • Quality Management
  • Level 5 : Optimizing
    • Continuous process improvement is enabled by quantitative feedback from the process and from testing innovative ideas and technologies.
    • This level includes all characteristics defined for level 4.
  • KPA : Level 5
    • Defect Prevention
    • Technology Change Management
    • Process Change Management
  • Does CMM really work?
    • The following table show an example of CMM Project Statistics based upon a sample of 1000 projects delivering 2000 KLOC Development Project
    Source : Master Systems Inc.
  • What are you thinking know?
    • Project Planning
    • Reduced Project Time
    • Minimise Errors
    • Increased Profits
    • Deliver Quality Software to your clients
  • Solution A Process Driven Approach Contact nckrishna@yahoo.com