Quality of Life? Does it Exist?

Today I just want to write about some thoughts that came to my head after reading the InfoQ article about Scrum adoption in China.

The article itself is very interesting, since it shows the benefits (and also problems) that companies have had when adopting Scrum. But what triggered this post was the chart shown below, provided by one of the interviewed companies, when they were asked What’s the benefit that Scrum brought to your project, your company?

What this chart shows is that Scrum improved the quality of worklife of most members of the team. And I am writing about it because I think this is one of the aspects of agile methodologies that isn’t perceived as much as it should.

When you work with agile, instead of working alone, you work in pairs, instead of holding all the problems by yourself, you share it and discuss it, instead of working as an individual, you are part of a team.

And that makes all the diference from when you work in non-agile environments, sit alone in your cubicule and interact only with your computer during all day. That makes a diference in your life.

So, if you don’t want to try agile because of the productivity aspect, at least try it for the sanity of the persons working for you.

Advertisements
3 comments
  1. Charles said:

    Of particular interest is the roughly 1/3 of developers that classified Scrum as ‘worse’ or ‘much worse’ than their previous approach. In my own experience, this ratio seems to hold true for Agile practices in general and not Scrum specifically… in other words, there seems to be a non-trivial percentage of developers that reject the Agile experience.

    And so, we are now presented with an opportunity to advance the state of the art by investigating and better understanding the individuals and organizations that reject Agile adoption, and the nature of those failures. Is it a marketing problem? An organizational effectiveness issue? Or perhaps something more emotional or psychological in nature?

    Any readers with experience with this problem?

  2. Boris Gloger said:

    I completely agree. Scrum shall make fun. The one and most important aspect of doing Scrum form me was and is have a more fun, and more happiness in work.
    I do coaching and training since 2004 and one thing is absolutely common in all successful implementations of Scrum, who did Scrum do want to do nothing else anymore.

  3. franktrindade said:

    Charles,

    interesting comment. Maybe you can get some clues going back to the InfoQ article and reading the information provided by the same person when asked “What’s the biggest problem during the adoption, and how did you solve it?”

    And the answers were:

    First of all, we needed to get the boss to support us. And then, to tell the truth, adopting Scrum is pretty easy, much easier than CMMI.

    The most difficult thing is that you need to resolve the problems revealed in the process, such as:

    1. “We don’t have clear requirements, resulting in a high cost of communication in late stages. We spend too much time discussing with the product manager again and again.”
    2. “Delivery cycle is too long: our Sprint is 3 or 4 weeks long, but the product manager hopes we can deliver two versions per week.”
    3. “We cannot master the historical requirement and the product architecture based on the Scrum characteristics.”
    4. “The delivery date is fixed by the business guys, so we don’t have time to do unit tests, nor code reviews.”
    5. “We cannot clearly see the bottlenecks between tasks, or how to coordinate everyone.”
    6. “We need at least one week for analysing the data after deployment, it’s impossible to conclude how to make improvement right after the current sprint.”
    7. “The pace of development is too fast, we don’t have enough time to stop and do a good retrospective. The historical requirement isn’t fully used.”

%d bloggers like this: