FREE Subscription to Dr. Dobb’s Digest: Same Great Content, New Digital Edition
Site Archive (Complete)
Architecture & Design
Email
Print
Reprint

add to:
Del.icio.us
Digg
Google
Furl
Slashdot
Y! MyWeb
Blink
August 02, 2007
SCRUM Meets CMMi

Agility and discipline combined

(Page 1 of 6)
Pablo Santos
Codice Software tackles Agile methodologies (SCRUM) and process improvement (CMMi) at the same time.
Pablo is a software engineer at Codice Software. He can be reached at psantosl@codicesoftware.com.


About 80 percent of software houses around the world are small companies. Compared to the large companies, small shops typically have advantages in terms of agility, performance, motivation, and focus. What they don't often have is validation that the processes they use to deliver software also focuses on quality—the type of validation usually reserved for large organizations that have adopted capability models like CMMi.

However, Codice Software (www.codicesoftware .com) is a small company that adheres to both Agile methodologies (SCRUM) and process improvement (CMMi). In this article, I explain why we pursued CMMi evaluation during the development of Plastic SCM (a configuration-management and version-control tool), what went smoothly, and what difficulties we had in making our SCRUM process fit within CMMi rules.

Why CMMi?

While companies usually adopt CMMi (www.sei.cmu.edu/cmmi/cmmi.html) to improve their software production methods, they recognize that the quality status is also worth the effort. Fewer than 2000 companies worldwide have reached one of the four CMMi official levels, so joining this exclusive club looks appealing to many companies.

Our motivations to achieve CMMi were:

  • We expected rapid personnel growth, so having well-defined procedures would help us grow.
  • As a small company entering a competitive market, a CMMi level would give us a competitive edge.
  • We didn't want our Agile processes to degrade into code-and-fix cycles.

But we also had concerns. For instance, we didn't have previous full CMMi experience, we were worried about CMMi introducing unnecessary bureaucracy, and we were totally committed to SCRUM, even though from what we could tell, it wasn't fully compatible with CMMi.

1 Why CMMi? | 2 Initial Situation | 3 The SCRUM Process | 4 Agile Concerns | 5 Requirements Management | 6 New Areas Next Page
TOP 5 ARTICLES
No Top Articles.
DR. DOBB'S CAREER CENTER
Looking for a new job? open | close
Search jobs on Dr. Dobb's TechCareers
Function:

Keyword(s):

State:  
  • Post Your Resume
  • Employers Area
  • News & Features
  • Blogs & Forums
  • Career Resources

    Browse By:
    Location | Employer | City
  • Most Recent Posts:



    MICROSITES
    FEATURED TOPIC

    ADDITIONAL TOPICS

    INFO-LINK



     




    Techweb
    Informationweek Business Technology Network
    InformationweekInformationweek 500Informationweek 500 ConferenceInformationweek AnalyticsInformationweek Events
    Informationweek MagazineGlobal CIOIWK Government ITbMightyByte and SwitchDark Reading
    Digital LibraryIntelligent EnterpriseInternet EvolutionNetwork ComputingPlug Into The CloudDr. DobbsContentinople
    space
    TechWeb Events Network
    InteropVoiceConWeb 2.0 ExpoWeb 2.0 SummitEnterprise 2.0Mobile Business ExpoNoJitter
    Black HatGTECEnergy CampCloud ConnectGov 2.0 ExpoGov 2.0 Summit
    space
    Light Reading Communications Network
    Light ReadingLight Reading AsiaUnstrungCable Digital NewsInternet EvolutionPyramid Research
    Heavy ReadingLight Reading LiveLight Reading InsiderEthrnet ExpoTelco TVTower Technology Summit
    space
    Financial Technology Network
    Advanced TradingBank Systems and TechnologyInsurance and TechnologyWall Street and TechnologyAccelerating WallstreetBST SummitBuyside Trading SummitIT Summit
    space
    Microsoft Technology Network
    MSDNTechNetTotal IT ProTotal Dev ProNET Total Dev Pro CommunitySQL Total Dev Pro Community
    space