InfoQ

InfoQ

InfoQ

En | 中文 | 日本語 | Br

562,907 Jan unique visitors

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Complaint-Free Iterations

Posted by Geoffrey Wiseman on Apr 17, 2008

Sections
Process & Practices,
Architecture & Design,
Enterprise Architecture
Topics
Teamwork ,
Agile ,
Human Resources
Tags
Co-Located Teams ,
Culture Change
No software project is perfect, nor is the organization in which the project takes place.  When your software project goes wrong, do your team members complain, or do they take corrective action?  The Complaint Free World project encourages people to take notice of how often they complain, and reduce the frequency of the complaints, aiming for a goal of twenty-one complaint-free days. 

The Complaint Free World site FAQ describes the basic concern:
Surely, it makes sense to express pain, grief or discontent occasionally but most people do so constantly. In so doing, they are talking and thinking about what they do not want in their life and, thereby, attracting more pain, grief and discontent. Instead, think and talk about what you are grateful for. Talk about what you DO want and not what you DON'T want.

CBC Television's coverage of a Complaint-Free World wisely includes a segment of Monty Python's Four Yorkshiremen, for whom complaining seems to be a sort of entertainment.  The FAQ references but does not cite studies that "have shown that complaining about one’s health actually tends to make a person’s health worse."

A group on Revolution Health provides a sort of support-system for people wishing to become complaint free, and suggests the following steps to that goal:
  • Wear a Complaint Free purple bracelet or rubber band (and switch wrists if you complain) 7 times per week
  • Think of something you complain about. Write down what would happen if it were resolved positively once per week
  • Complain/switch your bracelet fewer times today than you did yesterday 7 times per week
  • Write down how many days you've gone without complaining in your Goals on-the-go booklet at least once per day
  • If something upsets you, speak directly and only to a person who can change the situation at least once per day
  • Check in with a complaint-free partner or with the group’s message board at least 3 times per week
  • A complaint can be an excuse not to act. Take action toward an important goal before going to bed once per day
  • Actively show gratitude by telling someone in your life how much you appreciate them at least once per day
If your team occasionally drifts into a negative mindset, consider getting some purple bracelets and start aiming for a complaint-free iteration or two.
  • This article is part of a featured topic series on Agile

Related Sponsor

In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!

3 comments

Watch Thread Reply

Nice Idea! by Mishkin Berteig Posted
Re: Nice Idea! by Tobias Mayer Posted
good idea by James Richardson Posted
Sort by date descending

  1. Back to top

    Nice Idea!

    by Mishkin Berteig

    I think this could be nicely tied in with appreciative inquiry. It would change the nature of retrospectives for a lot of teams as well.

    Reply

  2. Back to top

    Re: Nice Idea!

    by Tobias Mayer

    I agree. Complaining is incredibly boring, for everyone. In the retrospectives I run with teams I always (and continuously) ask the question: what are YOU going to do about it?

    During the last section of the retrospective all team members pair up and make commitments to each other for positive change -- just small things, that can be achieved in a week or two weeks. They actually write these down on 3x5 cards, sign them and have their partner sign them too. It is the partner's job to ensure the commitment can be met, and accepted (think acceptance criteria). The cards are displayed on the wall by the story board. This keeps the focus on positive resolution, and away from whining and complaining.

    Nice post. Thanks.

    Reply

  3. Back to top

    good idea

    by James Richardson

    nothing like bringing religion into IT. I'm sure it will all work much better with God (whichever one suits) on your side.

    Reply

Educational Content

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.

Beauty Is in the Eye of the Beholder

Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.

Architecting Visa for Massive Scale and Continuous Innovation

John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.

Max Protect: Scalability and Caching at ESPN.com

Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.

The Seven Deadly Sins of Enterprise Agile Adoption

Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.

Questions for an Enterprise Architect

Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?

Wrap Your SQL Head Around Riak MapReduce

Sean Cribbs explains what Map-Reduce and Riak are, why and how to use Map-Reduce with Riak, and how to convert SQL queries into their Map-Reduce equivalents.