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.

Monday, March 24, 2003

Assuming the Worst about Requirements -- More on a recent theme...

For requirements to succeed, they must be clearly defined and enough time must be allocated to complete them. This is crucial to preventing team clashes and to creating a positive work environment. Writing the correct requirements and following them, is the key to producing a quality product. In this StickyMinds.com column (may require free registration), Becky Winant explains why properly assigning requirements is important to creating project deliverables. In the piece, she mentions three way in which "requirements become suspect.."
"We believe in miracles. Ever hear a story about how some genius sold his idea based on a napkin sketch? I think sometimes we expect our analysts to do the same. Hey, once the sketch is down, we're done! Time to hand the napkin over to production.

"We get carried away by sports analogies. In some organizations, the requirements stage feels like the warm-up before a game. We spend just enough time to loosen up, because we are saving time for the real work. So, requirements becomes all about establishing the customer relationship and maintaining a friendly mood.

"We believe in components. This is good, because once we really have requirements this could buy us time and produce reliable results. Without clear requirements, we risk assembling a van instead of the sedan that was requested. We heard "vehicle for the family," started thinking about which components to use, and went to work."
She goes on to provide some reasonable advice on the subject, which, to my mind, can be related to many kinds of projects, not just the software-centric ones to which the issue of "requirements" are usually considered.

That said, I want to add that I particularly resonate with Winant's third source of problems -- belief in components. The common use of a detailed WBS (work breakdown structure) is one way of trying to deal with it, but, as many of those involved in agile methodologies like to point out, a lot of those details are unknown and unknowable in the early days usually associated with planning. In addition, even if one could lay out a detailed WBS to define the project, its local, partial, component-focused nature can easily lead those assigned to work on the individual components to think and work within a too narrow range of focus. The hierarchical, "leggy" nature of a WBS makes it too easy to miss dependencies and opportunities across the legs, and therefore make project promises (as well as requirements) suspect.

This is why, in the Critical Chain community, if a WBS is used at all, it is only used to one or two layers of detail to define high level objectives, deliverables, and success criteria. The typical critical chain planning process quickly moves to the building of the project's dependency network, so that, even if details of how components are to be delivered are fuzzy, at least the required interactions between components can be defined. In this way, the project is understood not as a sum of components, but as a system of interdependencies supporting the project objectives.

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



Google
Web focusedperformance.com


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...

Current
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