Project Management Operational Problem Solving Implementation & Change Management Strategy & Alignment

Frank Patrick's Focused Performance Business Blog
This Focused Performance Weblog started life as a "business management blog" containing links and commentary related primarily to organizational effectiveness with a "Theory of Constraints" perspective, but is in the process of evolving towards primary content on interactive and mobile marketing. Think of it as about Focusing marketing messages for enhanced Performance. If you are on an archive page, current postings are found here.

Thursday, December 11, 2003

Agile/CCPM - Non-Meaningful Distinctions -- A recent thread in the TOCExperts YahooGroup has touched on the subject of SCRUM, one of the family of Agile approaches to [software development] projects. Being a Theory of Constraints oriented discussion group, it was not to be unexpected that at some point in the conversation, a "comparison" with Critical Chain-based Project Management (CCPM) would pop up. Clarke Ching, a frequent and knowledgeable member of TOCExperts, offered an excellent summary of SCRUM for the non-practitioner, but within it, he offers a few bullets on how SCRUM differs from CCPM that are worth some questioning comment. The first "difference" offered is that...
CC aims to get the project finished as quickly and reliably as possible. Scrum aims to get working functionality delivered as quickly as possible.
This is, in my opinion, a non-meaningful distinction, as the basis of the difference is in the comparison of "project" and "working functionality." In a CCPM-managed project, there is nothing to say that the objective deliverables can't be pieces of "working functionality." There is nothing to say that individual pieces of "working functionality," delivered via SCRUM practices, can't be assessed vis-a-vis expectations of cost and schedule via CCPM's buffer management, either as individual sub-projects, or as deliverables diverging from the mainline critical chain of the overall project. The management of the effort is related to the second offered difference...
CC buffers with time. Scrum buffers with functionality.
Now I've been known to utter similar comments about buffering with time versus buffering with scope, but reviewing some recent descriptions of "burn-down" charts common to agile environments (and perhaps viewing the recent PBS NOVA episodes on string theory), I've come to a view of scope and time as sufficiently intertwined to be only one of perspective. Like the idea of space-time, drawing too fine a distinction between the components of scope-time is a distraction at best. Too much scope left (for the time we wanted to deliver it it) and not enough time left (to complete the work we would like to) are the same thing. Any decisions about changes in the work content to recover our initial promises/targets or the deliverables that we finally produce in either approach immediately get into the question of time of work remaining (and vice versa).

At the practical, less metaphysical, level, the content of SCRUM meetings are nothing more than the equivalent of the content of CCPM's daily buffer management reviews of single projects. "Burn-down" charts, used to assess what is left in SCRUM and other Agile project environments can map directly to CCPM buffer consumption analyses. Both, with their forward-looking view, are superior to the backward focus on supposedly immutable baselines or completed work as the source of "earned value" in other approaches to projects.

The third difference is offered as...
CC says "Don't put the safety in the task; put it in the project." Scrum says "Don't try and figure it all out up front because you can't. Things will change too much as you go. Instead, build working software quickly, inspect and adapt."
Again, I don't see the "difference." I almost saw putting these two together as a non sequitor, but then there might be some connection, and again, more similarity than difference. SCRUM and other Agile approaches use plans for their efforts. They're just not detailed in a way that locks them into a calendar or to artificial dependencies to make promises, mapping them instead to a set of time-boxed sequential iterations or sprints. CCPM also frees the interim activities of a project from the calendar by removing the idea of task level safety, commitment, and due-dates.

As in most things, when there are two common sense approaches to a particular issues, there is often more in common than there is different.


posted by Frank - Permanent Link - |

Current Posts (Main Blog Page)

Previous Posts

It is a common delusion that you make things better by talking about them. - Dame Rose Macaulay

What's this XML thingie all about?

View Frank Patrick's LinkedIn profileView Frank Patrick's profile


FP's Recommended Reading
- From the FP Bookshelf...

...from My AStore

...and some ideas from Amazon...

Best of the FP Blog Archive
- The really good stuff...

Strategic Thinking and Improvement

Enterprise PM - It Starts with Strategic Interdependence

Face Reality

How to Think With Your Gut

Hugger-Mugger and Helter-Skelter

Managing for Murphy, Satan, and Yourself

More of the Same (Local/Global)

PMI Congress Notes: Using Risk Management for Strategic Advantage

Tell Me How You'll Measure Me and Ah, But What to Measure?

What's in Your Strategy?

Why Can't We All Just Get Along?

Why TOC Works
Project and Multi-Project Management
Critical Chain and (not or) XP

Defining Project Success (But for Whom?)

Down 'n Dirty w/TOC and PM (Part 1 of 5 consecutive posts)

End of Project Review

If Project Management is the Answer, What's the Question?

In Defense of Planning

It Ain't the Tools

Lessons Learned, Revisited

Predicting Uncertain Futures

Project Conflicts

Project Determinism (and other myths)

Project Portfolio Management

Promises, Predictions, and Planning

Removing Bottlenecks - A Core Systems Design Principle

Stage Gates and Critical Chain

Ten Top Sources of Project Failure (The Executive Version)

The Meaning of "Schedule"
Leadership and Change Management
Consistent Leadership Behavior

Invisible Dogma - Perpetuating Paradigms

Nothing But Value

On Assumption Busting

Personal Productivity - An Excuse?

The Psychology of Change Management

FP's Blogroll
- Other weblogs and sites I read

FP's Ryze Page

FP's Technorati Profile
- Click the pic

Who links to FP?

For Your Charitable Consideration:

Give Something Back Foundation

Global Virtual Classroom

FP's Link List
- Selected Sites and Resources

Critical Chain Discussion Group

Lilly Software: Visual DBR

Sciforma PS (Critical Chain Software)

Spherical Angle (Critical Chain Software)

Synchrono Supply Chain Planning Software

FP Blog Archives
- All the oldies, but goodies...

10/09 | 09/09 | 08/09 | 07/09 | 06/09 | 05/09 | 04/09 | 03/09 | 02/09 | 01/09 | 12/08 | 11/08 | 10/08 | 09/08 | 08/08 | 07/08 | 06/08 | 05/08 | 04/08 | 03/08 | 02/08 | 01/08 | 12/07 | 11/07 | 10/07 | 09/07 | 08/07 | 07/07 | 06/07 | 05/07 | 04/07 | 03/07 | 02/07 | 01/07 | 12/06 | 11/06 | 10/06 | 09/06 | 08/06 | 07/06 | 06/06 | 05/06 | 04/06 | 03/06 | 02/06 | 01/06 | 12/05 | 11/05 | 10/05 | 09/05 | 08/05 | 07/05 | 06/05 | 05/05 | 04/05 | 03/05 | 02/05 | 01/05 | 12/04 | 11/04 | 10/04 | 09/04 | 08/04 | 07/04 | 06/04 | 05/04 | 04/04 | 03/04 | 02/04 | 01/04 | 12/03 | 11/03 | 10/03 | 09/03 | 08/03 | 07/03 | 06/03 | 05/03 | 04/03 | 03/03 | 02/03 | 01/03 | 12/02 | 11/02 | 10/02 | 09/02 | 08/02 | 07/02 | 06/02 | 03/02 | 02/02 | 12/01 | 11/01 | 10/01 | 09/01 | 08/01 | 06/01 | 02/01 | 01/01 | 12/00

Powered by Blogger

If you are interested in adding an easily updated weblog to your site, I would suggest you look into the free service provided by Blogger.

Who is FP?
Contact Focused Performance