This Month’s Pattern *

36 Cider House Rules

Members of the project team ignore or work around rules made by people who are unconnected to the project’s work.

The Cider House Rules, a novel by John Irving, tells the story of a group of apple pickers who return to an orchard every season to pick apples for making cider. During the weeks they pick apples, the pickers live in the old cider house. Inside it, Olive, the owner, has tacked a typewritten page headed Cider House Rules. One of the new pickers, upon reading it, can hardly fail to notice that most of the rules are being openly flouted. Inquiring about these breaches, he is told by a veteran picker, “Nobody pays attention to them rules. Every year Olive writes them up and every year nobody pays no attention.”[1]

“There are rules, and we do break them.” —Linda Prowse

The problem with the cider house rules is that someone who does not live in the cider house—and has no intention of ever living there—is setting the rules for those who do. Olive lives in the big house and therefore does not appreciate that on hot summer nights, the roof is the only cool place to relax. Nor does she understand that drinking on the roof has become part of the apple pickers’ way of life. By setting rules that are inappropriate, she shouldn’t be surprised to discover that they are being ignored. By setting rules that are imposed on others from afar, she is asking for them to be defied.

Some development organizations have their own versions of the cider house rules. People who are not involved in project work set the rules for those who are. These organizations have a Process Improvement Office, or a Standards Group, or a Quality Department, whose task is to mandate work processes or methods. These departments might also choose tools to be used by projects or develop standards for the projects’ deliverables. These are outsiders setting rules for how a project team should do its work, potentially without any meaningful understanding of that work.

The pattern becomes more apparent when the selection of processes, methods, or tools is the only job of the selector. He does no project work; he just tells those who do the work how they should be doing it.

The outside maker of rules is rarely in the best position to determine how work should be done. When he is not intimately familiar with the work, he generally sets rules that require pointless work to be done. After all, he wants to cover all the bases (including his own rear end), and should things go wrong, his rules must be beyond criticism and absolve him of any blame. Moreover, the rule maker does not want anyone to see his rules as being in any way inadequate.

Naturally, successful project work is not complete anarchy. There must be some rules and defined processes. However, it is necessary for there to be goodness of fit between the world envisioned by the rule makers and the world inhabited by the people who are to follow those rules. The best fit comes when the process or quality specialists are regular members of the project team, or are at least closely aligned with the reality of the project’s work. Once this condition is met, the specialists are in the best position to apply their knowledge and define appropriate processes for the team. The burden shifts to the rule maker to be certain that all rules are the right rules for that project.

When the rules are appropriate, the project team will abide by them: They are useful, reasonable, and seen to be sensible. But when reality and rules differ, then reality is king, and you have cider house rules.



* Each month we plan to publish here one of the patterns from our Jolt Award book, Adrenaline Junkies and Template Zombies — Understanding Patterns of Project Behavior. (Watch this space for a mere 86 months and you'll have read the whole thing.) The book is published by Dorset House Publishing, in the US and Hanser Verlag in Germany. It is available at Amazon and also as a Kindle book.

events

Munich, Mastering Software Architectures
18-Jun-2013 to 21-Jun-2013

The dynamic duo Peter Hruschka and Gernot Starke teach their 4-day seminar in German.You can take the exam to become a Certified Professional for Software Architecture right after the seminar. Contact arc42 for details.

Vienna, Pragmatic Requirements Modeling
25-Jun-2013 to 27-Jun-2013

Peter Hruschka teaches this IREB Advanced Level Module. Contact CONECT for details.

Brussels, Mastering the Requirements Process
24-Sep-2013 to 26-Sep-2013

James Robertson teaches Mastering the Requirements Process. Please contact I.T.Works for details.  

London, BA Conference
24-Sep-2013 to 25-Sep-2013

Suzanne Robertson speaks about Discovering the essence of the problem: the route to the best, most innovative solution. Details and registration at Business Analysis Conference Europe 2013.

Reykjavik Masterign the Requirements Process
2-Oct-2013 to 4-Oct-2013

James Robertson presents Mastering the Requirements Process for Continuing Education at the University of Iceland. Please contact Ragna Haraldsdóttir.

Brussels, MRP part 2
10-Oct-2013 to 11-Oct-2013

Brussels, Mastering Business Analysis
10-Oct-2013 to 11-Oct-2013

James Robertson teaches Mastering Business Analysis. Contact IT Works for details of this course.  

Oslo, Mastering the Requirements Process part 2
14-Oct-2013 to 15-Oct-2013

Suzanne Robertson teaches Mastering the Requirements Process part 2. Details for this advanced class at Den Norske Dataforeningen.

Maarsbergen, Mastering the Requirements Process
15-Oct-2013 to 17-Oct-2013

James Robertson presents Mastering the Requirements Process for Adept Events. Details and registration: English - Dutch.

Oslo, Mastering the Requirements Process
16-Oct-2013 to 18-Oct-2013

Suzanne Robertson teaches Mastering the Requirements Process. For more information on this popular course, contact Den Norske Dataforeningen

Rome, Mastering the Requirements Process
21-Oct-2013 to 23-Oct-2013

Rome, Mastering Business Analysis
24-Oct-2013 to 25-Oct-2013

James Robertson teaches Mastering Business Analysis. Contact Technology Transfer for details of this course.  

Rome, Mastering the Requirements Process part 2
28-Oct-2013 to 29-Oct-2013

Suzanne Robertson teaches Mastering the Requirements Process part 2. Please contact Technology Transfer for details of this advanced class.

Maarsbergen, Mastering Business Analysis
4-Nov-2013 to 5-Nov-2013

James Robertson teaches the popular Mastering Business Analysis. Details from Adept Events in English or Dutch.

Wellington, Mastering the Requirements Process
27-Nov-2013 to 29-Nov-2013

The ever popular Mastering the Requirements Process. For details please contact Software Education.  

Melbourne, Mastering the Requirements Process
2-Dec-2013 to 4-Dec-2013

Mastering the Requirements Process. Please contact Software Education  for details and registration. 

Sydney, Mastering the Requirements Process
2-Dec-2013 to 4-Dec-2013

Suzanne and James Robertson teach the popular Mastering the Requirements Process sponsored by Software Education.

Melbourne, MRP part 2
5-Dec-2013 to 6-Dec-2013

Suzanne Robertson teaches Mastering the Requirements Process part 2. Contact Software Education for details of this advanced class. 

Vienna, Mastering Software Architecture
10-Sep-2013 to 12-Sep-2013

Peter Hruschka present the seminar that allows you to become "Certified Professional for Software Architecture". Please contact CONECT for Details

in depth

In this podcast James speaks of his experience in the profession of architecture and how it provides inspiration for his work on innovation and creativity. He also discusses the role of the business analyst in agile teams. Listen to the podcast.


There are now seven books by Guild authors available as ebooks, either as Nook Books or as Kindle Books.  



Shane Hastie's interview with the authors and book excerpt: Mastering the Requirements Process on InfoQ.


The preparation course for the IREB "Certified Professional for Requirements Engineering" is now available as video training. Learn at home or any other place. Including questionnaires to prepare you for the multiple choice test.



Mastering the Requirements Process, third edition Getting Requirements Right is now available as a Kindle Book, Nook Book, or in traditional paper.



A Sci-Fi novel from Tom DeMarco: Andronescu’s Paradox.  Could this be the Apocalypse we’ve all been dreading?  Or has the nineteenth century just returned for an encore?  Click to find out.



James & Suzanne Robertson challenge the accepted wisdom of the agile community and point out how agile projects don't always deliver value to the organization. Download the pdf from Cutter Consortium.


In a recent issue of IEEE Software Tom DeMarco asserts that “All Late Projects Are the Same.”   Do you agree with Tom or not?  Take a look at All Late Projects Are the Same.



Suzanne Robertson was interviewed by Penny Pullan on the subject of 'The Business Analyst Working with the Project Manager'. This interview is part of the Business Analysis Summit, November 2011. Listen to the interview at volere.co.uk



Tom DeMarco and Peter Hruschka interviewed by Markus Voelter on Software Engineering Radio about the process and the discoveries from writing Adrenaline Junkies and Template Zombies.