Skip to main content

Mapping the Agile Scrum and CMMI

Mapping the CMMI and Scrum 


CMMI practices are designed to provide value across a range of different situations and thus are stated in general terms. Because CMMI does not endorse any particular approach to development, little approach-specific information is provided. Therefore, those who don’t have prior experience implementing CMMI in situations similar to their current situation may find it difficult to interpret the practices. The following tables identify relevant CMMI practices for complying with maturity level 2 (using text taken from the model). They also show how Scrum practices were implemented in each CMMI specific practice (SP) on the large project. To be appraised at maturity level 2, the Scrum implementation had to show evidence of CMMI practices being performed. A discussion of the program’s CMMI maturity level 3 processes follows later.

CMMI Maturity Level 2 Process Areas Requirements Management The purpose of requirements management (REQM) is to manage the project’s products and product components requirements. It also helps to identify inconsistencies between those requirements and the project’s plans and work products. 



Project Planning 


The purpose of project planning (PP) is to establish and maintain plans that define the project’s activities.

Project Monitoring and Control 

The purpose of project monitoring and control (PMC) is to understand the project’s progress so that appropriate corrective actions can be taken when the project’s performance deviates significantly from the plan.










Configuration Management (CM) 

CM is not specifically called out in Scrum. However, in an Agile environment it is easy to add a layer of CM to protect work products. Even for groups that like to use white boards, you can be creative and at least establish some basic protection by labeling items (e.g., “V1.1” or “Story dated YYYY/MM/ DD”), by taking a photo, or by using other documenting techniques. The CM process area requires more than just versioning, but versioning is a good and fundamental start. Product and Process Quality Assurance (PPQA) Some basic PPQA activities are being accomplished naturally when the Scrum master checks that the Scrum process is being followed. Other PPQA activities are completed when a team performs code reviews, document reviews and validation testing. The Scrum master also removes process barriers and inefficiencies. However, Scrum does not specifically call out a level of objective process and product check, nor does it say that particular standards or processes should be defined and used. Therefore, Scrum does not automatically implement PPQA. However, refinements can be implemented to support a PPQA claim.


Supplier Agreement Management 

There are no practices in Scrum that deal with selecting and managing suppliers.


Measurement and Analysis 

The purpose of measurement and analysis (MA) is to develop and sustain a measurement capability to support management information needs. There are no practices in Scrum that establish a measurement program similar to the expectations of MA. However, the measures in Scrum can be used to implement MA 

















Comments

Post a Comment

Popular posts from this blog

User Story In Agile Scrum - By Ankur Mistry

In this article, we will learn what User Story is and how to write one. User Story plays a major role here. It is the part of the Agile process where instead of writing comprehensive requirements, we write a short description of a feature. As the  Agile Manifesto  says 'Working Software' Over 'Comprehensive Documents'. What is User Story? User Story is a short and simple description of the feature or requirements of the project. Generally, user stories are written on sticky notes or index cards as a user or role-based perspective. User Story Template As a < type of user or role >, I want < some goal > so that < some reason >. The template identifies 3 questions - "Who", "What", and "Why". If the team doesn't know these three answers, it means they don't understand the story, and if they don't understand the story, then it's difficult to split it well.   Reference:https://mazoea.wordpres
Post a Comment
Read more

Visual Studio Team Services - Agile - Scrum Project Management Tools

Before starting this article let's understand what is Agile and Scrum.  What is Agile Agile is a  Method  of project management that is characterized by dividing module in to tasks and t asks into short phases of work and frequent reassessment and adaptation of plans. In other words, Agile is a Time Boxed incremental software development method.  What is Scrum Scrum is an incremental agile software development framework  (Agile Framework).   Agile Scrum Process in Short. Product Backlog:  A product owner creates a customer’s wish list and prioritized it and create backlog, called Product Backlog. Sprint Planning:  In this meeting team select small part or module from the Top Priority Wish List of Product Backlog and prepare a small task list. Setting Capacity and Sprint:  Team has to deliver the tasks in 2 weeks or 4 weeks sprint, here Scrum Master bind tasks with Time and User. Scrum Master’s role:  Is to make sure team focused on its goal. End of the sprint:  
Post a Comment
Read more

The Burn Up Charts In Scrum By: Namrata Parik

I would like to propose a less-taken path in my maiden article to track the progress in scrum. We usually do it using the burn down chart which is relatively easier to understand as compared to the burn up chart. These charts help the team and stakeholders to see and track the progress at any point in the release process or sprint. Burn-down chart provides us the information showing the progress based on the remaining hours or story points from top to bottom. (The burn-down chart can be plotted using story points, task count or the remaining effort) This chart is a plot of expected remaining and actual remaining, this is the most used chart in scrum and since it has only two lines it is considered to be a simple chart. It does not cover the scope creep. So sometimes what might look like ‘no work ‘ done by the team may actually be a result of scope creep. The chart below reflects that the team has not done any progress in Sprint 5 and 6 as the story points remain the same. Image
Post a Comment
Read more