Comments on: Quality of Life? Does it Exist? http://blog.franktrindade.com/2008/04/23/quality-of-life-does-it-exist/ Agile, software and some non-sense Thu, 17 Jun 2010 09:41:19 +0000 hourly 1 http://wordpress.org/?v=3.0 By: franktrindade http://blog.franktrindade.com/2008/04/23/quality-of-life-does-it-exist/comment-page-1/#comment-29 franktrindade Tue, 13 May 2008 20:40:10 +0000 http://franktrindade.wordpress.com/?p=38#comment-29 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." 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.”

]]> By: Boris Gloger http://blog.franktrindade.com/2008/04/23/quality-of-life-does-it-exist/comment-page-1/#comment-27 Boris Gloger Fri, 25 Apr 2008 22:04:10 +0000 http://franktrindade.wordpress.com/?p=38#comment-27 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. 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.

]]> By: Charles http://blog.franktrindade.com/2008/04/23/quality-of-life-does-it-exist/comment-page-1/#comment-28 Charles Thu, 24 Apr 2008 15:24:05 +0000 http://franktrindade.wordpress.com/?p=38#comment-28 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? 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?

]]>