InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

SEI publishes report integrating CMMI and Agile

Posted by Manoel Pimentel , translated by Felipe Rodrigues on Nov 17, 2008

Sections
Process & Practices
Topics
Agile ,
Agile in the Enterprise
Tags
Patterns and Practices

Last week was hot in international scenario on software development. The SEI (Software Engineering Institute) recently published a report entitled " CMMI or Agile: Why Not Embrace Both!", which addresses the integration between the ideas and practices of the CMMI with the ideas and practices of Agile as something possible in software development projects.

According to the document, which counted on participation of some famous agilists as David Anderson, the focus of this initiative is:

More dialogue would be healthy and beneficial for users, the paradigms, and the broader community.

Also in another sentence of the document, which is explained the desired result of that:

We hope this report encourages both CMMI and Agile proponents (ideally, everyone in software related industries) to do the following:

  1. Recognize the value of each paradigm.
  2. Resist common misperceptions.
  3. Continue experimenting, learning, and reporting on what works and in which contexts.

The document also addresses other issues such as:

  • The Origins of Agile Methods
  • The Origins of CMMI
  • Lack of Accurate Information
  • Terminology Difficulties
  • There Is Value in Both Paradigms
  • Challenges When Using Agile
  • Challenges When Using CMMI
  • Problems Not Solved by CMMI nor Agile

In general, different reactions have occurred by the agile community, especially in Brazil (see messages in portuguese here Visão Ágil and here Scrum-Brazil, where many feel that this is pure opportunism, because they can’t see the synergy between these two worlds. And others see this as a good opportunity for all and a great chance to fix some problems from the past, on the understanding and adoption of Agile and CMMI itself.

But in truth, this was only the first step towards a clearer synergy between Agile and CMMI and perhaps there are still many questions that only with continuous experimentation and adjustment, we could really know whether this relationship is possible and more important if it is healthy.

  • This article is part of a featured topic series on Agile

Related Sponsor

In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!

No comments

Watch Thread Reply

Educational Content

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.

Beauty Is in the Eye of the Beholder

Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.

Architecting Visa for Massive Scale and Continuous Innovation

John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.