This Month’s Pattern *

19 Film Critics

Film critics are team members or corporate spectators who have determined that the value they add to the project lies in pointing out what has gone wrong or is going wrong, but who take no personal accountability to ensure that things go right.

You are in the final weeks before releasing your new system into production. Integration testing has been in full swing for some time, and the developers are fixing bugs as they come in. Release managers are going though their checklists of pre-ship activities to ensure that nothing has been overlooked. Then, at a readiness review, a new voice is heard. This is typically someone who has been associated with the project since its inception, but who has had little to say until now. We’ll call him Herb.

Herb is not all that pleased with the state of things. Herb feels that the product about to be shipped has missed a few key features. And the design reviews were not all they could have been. And the integration testing should have been far more rigorous. Given all of the problems he sees, Herb feels that shipping the system now may pose serious risks. He has enumerated the risks in an impressive PowerPoint deck that he has e-mailed to the world.

You consider Herb’s points, and you have to agree that some of them are valid. But your overall reaction is,“Why are you telling us this now? Where were you when we had time to address these issues?” Herb waves off your questions, offering no constructive suggestions for correcting what he sees as deficiencies, but reiterating his concerns about the way things have been handled.

Sometimes, on projects, film critics have real jobs and their criticism is more or less a hobby. Other times, they are actually chartered to be film critics by a manager who values this behavior. Either way, all film critics share one trait: They believe that they can be successful even if the project they’re on is a failure. They have, in effect, silently seceded from the project team.

Not all project critics are film critics. A lot of the difference is in the timing. People who feel accountable for the success of the project tend to speak up right away when they see that something is going wrong or could be done better. They come forward and say what they think, to whomever they believe can make a difference. They do so as soon as they can, because they know that time is always short and that corrective actions should be taken sooner rather than later. These people are not film critics; they are your fellow filmmakers. They know that they cannot succeed if the project fails, so they are taking matters into their own hands, every day, to increase the probability of your collective success. You may agree or disagree with their criticism, but you can see that they are working on the same film you are.

Pursuing the analogy between projects and films, we note that film critics don’t tend to weigh in until the film is complete, or so near to completion that there isn’t enough time left to take corrective action. It’s not that they actually want the project to fail; it’s more that they have come to believe that their own success is independent of the project’s success and has more to do with being seen as a keen observer of the obvious and an accurate predictor of the inevitable. They don’t necessarily realize it consciously, but they no longer care whether the project succeeds or not, as long as they are seen as having been right.

Why are some projects infested with film critics while others have few or none? There is only one reason: Some management cultures emphasize doing things right, while others emphasize not doing anything wrong. When managers are most concerned about not making mistakes, or at least not being seen as having made mistakes, they send obvious signals, both explicit and tacit, that catching people making mistakes is just as valuable to the organization as doing things right. Those people in the organization who have natural film-critic tendencies rise to these signals and engage in freelance film criticism on their current project to see how it will be received. If it is tolerated, or even rewarded, then film critics will multiply and accountability will diminish. Keep in mind that it is far easier to be a film critic than it is to be a filmmaker, that is, to be an accountable leader or team member. If the organization demonstrates that it values film critics, it shall have them.

Film criticism can exist at all levels in an organization, and it even can be institutionalized in a number of ways. The most common case is the unofficial film critic. This person already has a role on the project, though typically a peripheral one. Many film critics are in staff support roles, and from there, they can criticize multiple projects. In an especially diseased management culture, senior leaders may even charter an entire organization to act as a watchdog on teams building systems.

On project teams, film criticism is one example of a more general destructive pattern that we call goal detachment. Notice what enabled the film critic: the belief that there were multiple ways to succeed on this project. The project itself could succeed, of course. But the film critic (or the leader who chartered the critic) allowed that goal to be replaced by a related but independent goal: to accurately identify what’s going wrong on the project. It’s not that identifying deficiencies is a bad thing; it obviously is not. Goal detachment is destructive because people pursuing detached goals are only coincidentally working toward the success of the project; their efforts are just as likely to be inconsequential or even counterproductive.



* 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

Brussels, Mastering the Requirements Process
30-Jan-2012 to 01-Feb-2012

James Robertson teaches Mastering the Requirements Process. Please contact I.T.Works for details. This course is now full. Please check the April course.  

Trondheim, Mastering the Requirements Process
15-Feb-2012 to 17-Feb-2012

Mastering the Requirements Process with Suzanne Robertson. Contact Den Norske Dataforeignen for details. This course is now full.

London, Mastering the Requirements Process
20-Feb-2012 to 22-Feb-2012

The Spring edition of Mastering the Requirements Process with Suzanne Robertson. Please contact IRM UK for details.

Stavanger, Mastering the Requirements Process
20-Feb-2012 to 22-Feb-2012

James Robertson teaches Mastering the Requirements Process in Stavanger for Den Norske Dataforeignen.

Moscow, The Guild Way Towards Great Projects
28-Mar-2012 to 30-Mar-2012

The Guild Way Towards Great Projects. Three days with the Atlantic Systems Guild bringing you key insights for successful projects. This event is hosted by Careerlab and SoftwarePeople. Details here.  

Oslo, Mastering the Requirements Process
11-Apr-2012 to 13-Apr-2012

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

Rome, Mastering Business Analysis
12-Apr-2012 to 13-Apr-2012

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

Rome, Mastering the Requirements Process
16-Apr-2012 to 18-Apr-2012

Sassenheim, Mastering the Requirements Process
18-Apr-2012 to 20-Apr-2012

Brussels, Mastering the Requirements Process
25-Apr-2012 to 27-Apr-2012

Melbourne, Mastering the Requirements Process
21-May-2012 to 23-May-2012

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

Melbourne, MRP part 2
24-May-2012 to 25-May-2012

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

Sydney, Mastering the Requirements Process
28-May-2012 to 30-May-2012

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

Sydney, MRP part 2
31-May-2012 to 1-Jun-2012

Suzanne Robertson and Mastering the Requirements Process part 2. Please contact Software Education for details of this advanced class. 

Auckland, Mastering the Requirements Process
11-Jun-2012 to 13-Jun-2012

Wellington, Mastering the Requirements Process
11-Jun-2012 to 13-Jun-2012

The first New Zealand presentation of the year of Mastering the Requirements Process. For details please contact Software Education.  

Auckland or Wellington, Mastering the Requirements Process part 2
14-Jun-2012 to 15-Jun-2012

Suzanne Robertson teaches Mastering the Requirements Process part 2. Details for this advanced class at Software Education.

in depth

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 the November, 2011 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.


Tim Lister discusses risk management. This was part of an assignment for Cutter Consortium in Mexico. Watch the Video.


Tim Lister analiza la gestión del riesgoVea la versión en español.


Listen to Tom DeMarco's 10-minute interview on Coping With Sea Change, part of Andreas Heilwagen's ongoing "10-Minute Project Management" series.


Suzanne and James Robertson's popular Mastering the Requirements Process is now available as a Kindle edition.


The Guild's 2009 Jolt Award book, Adrenaline Junkies and Template Zombies is now available in a Kindle edition.


Tom DeMarco and Tim Lister's perennially popular book Peopleware is now available in a Kindle Edition.