We have 6451 guests and 3 members online
Home > Blogs > Featured Blogs > Brad Appleton's ACME Blog > An Agile CM Manifesto: Lame Oxymoron or Long Overdue?

An Agile CM Manifesto: Lame Oxymoron or Long Overdue?

E-mail
Written by Brad Appleton   
Wednesday, 06 May 2009 17:02

I submitted a proposal on this topic to the Agile2009 conference. The idea was to garner feedback as to whether or not there is a perceived need for Lean/Agile CM Manifesto (or "Declaration" of some sorts), which sort of presumes there is a legitimate place for something called Agile CM (or Lean CM).

The proposal was well received by its reviewers, but alas the sheer number of submissions versus number of available slots meant that even a lot of well-received submissions (including mine) didn't make the final cut.

Here is the proposal (below)! What do you think about the basic question it would ask of its audience? Is there a legitimate need for a Lean/Agile CM Manifesto? If so, what do you think it should say?



Summary Description

Agile development, agile project management, agile management, agile testing, all thus far have grown sizeable communities founded by many respected experts in their field. Why is this not yet the case for agile configuration management? Is there simply no need? Is lean/agile CM an oxymoron? Or is it an idea whose time has come and is long overdue? This talk will explore common complaints and misunderstandings between agilists/developers and CM, define what lean/agile CM really means, and whether or not a corresponding “manifesto” for CM is warranted (and if so, what must it include).


Presentation Outline

Approx ~30min of presentation followed by discussion/dialogue with the audience on whether or not the world needs a Lean/Agile CM manifesto, and what it should say. The Outline follows:

  • What is CM? (its more than just integration/build and version-control)
  • Traditional CM definition and Lean/Agile perspectives on CM
  • What is “Agile CM”? (CM for Agile projects? Agility for CM? or both?)
  • Lean/Agile CM Planning?
  • Lean/Agile Change Control/Tracking?
  • Lean Configuration audits/reviews, and status accounting?
  • Lean Traceability? (everyone’s favorite)
  • Agile Version control and Lean branching
  • Agile integration & build (nested synchronization & harmonic cadences)
  • “Emergent CM Architecture” from “refactoring” to SCM patterns

Discussion Points:
  • Common agilist/developer complaints & misunderstanding about CM [interspersed with the presentation]
  • Common CM complaints about (agile) development [interspersed with the presentation]
  • Do we need a Lean/Agile CM manifesto? Why or why not? [at the end of the presentation]
  • What must this manifesto include? from whom? [at the end of the presentation]

Background/Materials:

Materials for the presentation will be distilled from the following sources where many of the points above have been presented or discussed in more detail. Each of the below will be distilled into no more than a single slide (with few exceptions):


For additional background, links to a veritable cornucopia of related articles may be found on the CMWiki-web at http://cmwiki.com/AgileSCMArticles

Learning Outcomes:
  • Learn what Lean/Agile CM really means & implies
  • Common misunderstandings of agilists and developers about CM, and vice-versa
  • How to apply Lean thinking and Agile principles to more than just CI (CM planning, change-tracking, version-control, etc.)
  • Discover why there is (or is not) a need for a Lean/Agile CM “manifesto” or “declaration of interdependence”

An Agile CM Manifesto: Lame Oxymoron or Long Overdue?

Posted: 2009-05-07 00:02:00

Read Full Article
Author:Brad Appleton

Trackback(0)

Comments (0)Add Comment


Write comment

security code
Write the displayed characters


busy
 
Cialis

Agile Marketplace - Announcements and Special Offers

The Business Case for ALM Transformation
Are legacy systems holding your company back?  Breakthrough these technical constraints with an open and scalable environment that meets your unique business need to transform. There is no reason to be locked into an obsolete platform. The output of a number of recent transitions from legacy systems, this is practical white paper shares lessons learned and illustrates how guidance and enablement can pave the way for change.
Download this Whitepaper