Home > Articles > Software Development & Management > Agile

Like this article? We recommend

The Issues

To pursue an approach of using both a CMM and agile methods, several issues must be addressed. Some issues are easily resolved through brief analysis. Other issues require major effort to satisfy the model.

Process Area Coverage

The most direct way to compare agile methods to the CMM-SW or the CMMI is to consider coverage of the key process areas in the CMM-SW or process areas in the CMMI. Mark Paulk has already published an analysis of extreme programming against the CMM-SW.2 We'll focus on the CMMI here, but the general approach remains the same. For each of the process area goals, can the practices of the agile method satisfy the goals? If not, is this a gap that needs to be augmented, or are these reasonable areas for tailoring the process area?

Figure 1 illustrates a possible mapping for XP and Scrum to the CMMI, assuming that they're used on a project for which the methods are a good fit.3 4 Whether the goals of the process area are satisfactorily addressed in any particular situation depends on the specific context. For example, XP's story approach or Scrum's tasks may be very effective at managing the requirements of an information system, but are probably not sufficient in a hard, real-time domain.

Figure 1Figure 1 Mapping the CMMI process areas: ++ largely satisfies, + somewhat satisfies, - doesn't satisfy.

There are several interesting process categories to mention. It's probably not surprising that these agile methods don't say much about process management category in Figure 1. However, an organization's existing CMM approaches for identifying, piloting, and deploying processes can be used for introducing these techniques. What's interesting to note is that there appears to be a conscious effort on the part of the agile community to ensure that the processes and tools needed to successfully deploy agile methods are made available across the entire industry, not just to a particular organization. The web and other publishing mechanisms have been powerfully leveraged, so that anyone looking for the assets needed to put these approaches into practice can find them readily.5 6 To a large degree, the ubiquitous availability of these assets will help satisfy the process management category of the CMMI.

The real strength of the agile methods is in project management. Both XP and Scrum spend a great deal of effort in planning, although there's not much focus on long-range planning. In both techniques, long-range plans are fairly coarse-grained. The focus is instead on short-range planning. Watts Humphrey observed that the agile approaches reflect the axiom, "If you don't plan well, plan often."7

In Scrum, for instance, a product backlog is maintained of all pending tasks. The backlog is maintained in priority order. A 30-day sprint is organized such that the top items in the backlog are implemented. Coordination within the sprint is provided by a daily 15-minute Scrum meeting in which each team member explains what was done since the last Scrum meeting, what's planned before the next Scrum meeting, and what current obstacles exist. Progress against the backlog of tasks for the sprint is maintained so that overestimates and underestimates can be identified and corrective action taken. The style is very different than the work breakdown structure practices described in the CMMI, but still satisfies many of the goals.4

Other gaps can be satisfied with complementary practices. In some of these cases, the complementary practices must be tailored to fit with the agile method. For example, an independent group validating XP work products would need practices tailored to fit the XP team's rapid pace of iterations—a member of the validation group could be included on the XP team to ensure that the stories were testable, and to validate the tests. In other cases, there's no direct interaction between the complementary practices and the agile method, and less practice tailoring may be needed. For example, because agile development typically omits practices for process management, existing practices for introducing new processes should be suitable without much alteration.

Some of the gaps in Figure 1 reflect assumptions on the part of the method; for example, Scrum doesn't specify any particular configuration-management approach, because that's assumed to be part of the engineering practices. In some cases, an organization's existing processes provide the complementary process without any tailoring. In others, agile techniques may be combined.

Process Definition

One challenge for all process-management groups is finding the right level of detail when capturing processes. This is especially true for agile methods. By design, agile methods are simple to describe and understand, even through the work required to execute them may be very complex. Consider XP's pair programming and peer reviews. Traditional peer review processes define a formal approach for reviewing products, capturing defects, and collecting and analyzing related metrics. Peer reviews are satisfied differently when agile methods are used. The idea is that there should be continuous peer review, so all developers work in pairs at a terminal. This concept can be reasonably described in an organization's template for process descriptions. However, if one were to attempt to press a traditional peer review description onto pair programming and try to capture a detailed log of the defects captured during pair programming, the practice would get bogged down and lose its value.

Work Products

Despite what many people think, it's not true that agile methods are without artifacts, although they're certainly less documentation-focused than traditional techniques. Still, this is an issue for organizations for whom the CMMI is the basis for rating their organization.

XP uses working code that customers can use and has tests that suites can validate automatically. These are easily verifiable products. Other artifacts are less formal and may prove more difficult to verify. Index cards are used frequently, as are whiteboards. However, some care and creative thought can retain these artifacts with minimal overhead. Some groups, for instance, capture their whiteboard sessions with a digital camera for later reference.

In other cases, such as in pair programming, no obvious artifact is generated by the practice. Assessment methods such as SCAMPI are much more documentation-oriented than earlier assessment methods. Artifacts are required in all areas, although interviews may provide additional evidence for affirmation8. In these cases it may be necessary to modify the process to make it auditable. In keeping with the agile approach, a simple approach should be used, such as a log of programming pairs.


There is a substantial burden of proof on an organization that wants to use agile methods and still satisfy the CMMI. The model even reads as follows (emphasis added):

When you use a CMMI model as a guide, you plan and implement processes that conform to the required and expected components of process areas. Conformance with a process area means that in the planned and implemented processes there is an associated process (or processes) that addresses either the specific and generic practices of the process area or alternatives that clearly and unequivocally accomplish a result that meets the goal associated with that specific or generic practice.9

A variety of CMM practices would need major tailoring or use of alternative practices. In some cases, it may even make sense to tailor the process areas. For example, the Technical Solution process area includes the goal, "Product components, and associated support documentation, are implemented from their designs." XP's approach doesn't design up front. Instead, simple software is built, complete with a complete test framework, and then refactored. The design emerges over the life of the project. This is certainly one of the more controversial aspects of XP, but if you're going to make it fit with the CMMI, you need to tailor the goal.

Change Management

High-maturity organizations are supposed to be agile and able to incorporate new practices. The description of a level 5 organization says, "Optimizing processes that are agile and innovative depends on the participation of an empowered workforce aligned with the business values and objectives of the organization."9 Although other approaches may optimize for performance or reduced defects, agile methods are an approach for optimizing requirements flexibility and discovery.

However, less mature organizations may have more difficulty trying to blend a CMM and agile methods. Since the agile methods have no explicit role for process or quality assurance organizations, these groups may feel threatened. The agile evangelists may perceive the process groups as a barrier. Unfortunately, each party may be making erroneous assumptions about the other. While engineers on their own may be able to introduce agile methods on their projects, process groups have the skills and expertise for introducing practices more broadly in an organization. Some organizations have been persuaded to adopt agile methods after experiencing the pain of significant failures with other techniques. Process groups can play an important role in promoting agile methods without hitting rock bottom. Process groups have experience with conducting pilots and collecting data and can guide the agile advocates. Both the advocates for agile methods and process groups want to improve their organizations. Encouraged, empowered grassroots support can be a powerful asset to a process group.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020