Skip to main content

DeMarco and Lister on Standards

Joy Beatty recently posted an entry about standards on the Requirements Defined blog. She wrote, "[D]evelop them as a team, so that the standards are not forced on anyone who is not bought into them."

I agree with the notion of consensus and buy-in that Joy suggests. Whenever someone mentions standards, I like to quote Tom DeMarco and Timothy Lister. Here is what they wrote about standards in Peopleware: Productive Projects and Teams:
Identifying an ideal practice, or at least a candidate ideal practice, is a useful endeavor. But the programs that mandate such a practice are something else entirely.

[Big 'M'] Methodologies seek to force convergence through statute. There is an inevitable backlash, the result partly of enforcers' heavy-handedness and partly of thinking workers' strong sense of independence, the cowboy mentality so common to those who populate any new frontier. Better ways to achieve convergence of method are training, tools, and peer review.

It's only after this kind of gently guided convergence that you may think of publishing a standard. You can't really declare something a standard until it has already become a de facto standard.

The opposite approach would be one in which every new undertaking is run as a pilot project. To the extent that there was a standard way to carry out the work, that would be the only way you weren't allowed to carry it out. The standard would be for at least one part of the effort to be run in a non-standard way. (This seems to be an informal rule within certain divisions of Fujitsu, for instance.)
In general, seek standardization through convergence, not by mandate.

Comments

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Henry Ford's "Faster Horse" Quote

You may have heard the ( apocryphal ) Henry Ford quote: If I'd asked customers what they wanted, they would have said "a faster horse". Over at the On Product Management blog , Saeed gives his take on this infamous quote. He "hates" it, and gives some compelling reasons. Saeed is spot on in his explanations. Personally, I think the quote is great, but it's a matter of interpretation. The valid point of the quote is not that it's a bad idea to facilitate a conversation with your market to better understand it. The valid points are: You must ask the right questions to get valuable answers. You must interpret the answers thoughtfully - often outside their direct meaning - to glean reliable information. Asking questions is not always the best way to "listen" to your market. (E.g., sometimes pure observational studies are more reliable.) Nonetheless, I find the quote is helpful to combat "armchair product management" in the

Stop Validating and Start Falsifying

The product management and startup worlds are buzzing about the importance of "validation". In this entry, I'll explain how this idea originated and why it's leading organizations astray. Why Validate? In lean startup circles, you constantly hear about "validated learning" and "validating" product ideas: The assumption is that you have a great product idea and seek validation from customers before expending vast resources to build and bring it to market. Indeed, it makes sense to transcend conventional approaches to making product decisions . Intuition, sales anecdotes, feature requests from customers, backward industry thinking, and spreadsheets don't form the basis for sound product decisions. Incorporating lean startup concepts , and a more scientific approach to learning markets, is undoubtedly a sounder approach. Moreover, in larger organizations, sometimes further in the product life-cycle, everyone seems to have an opinio