Comments on: Time, Resources, Scope… and Quality. http://www.adeptechllc.com/2010/05/13/time-resources-scope-and-quality/ Software, Agile Process and Security Tue, 13 Dec 2011 16:48:32 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Peter H. Coffin http://www.adeptechllc.com/2010/05/13/time-resources-scope-and-quality/comment-page-1/#comment-4645 Peter H. Coffin Thu, 13 May 2010 17:13:13 +0000 http://www.adeptechllc.com/?p=290#comment-4645 Quality doesn't really sit in the center of the chart, though it's sometimes easier to draw that way. It's off in the Z-axis; it's its own tone in the harmony. It's just a little too close to "Scope" in its characteristics to get talked about much, and you need to shift the pitch (for either metaphor) to pay attention to it. Go grab a 4-sider die, sight along one of the edges, label the front corner "Scope", the back one "Quality", and the other two "Resource" and "Time". What do you see then? Why, the Iron Triangle staring at you. With a sloppy hidden bit. And what goes into that hidden bit? Pretty graphics. Cross-browser compatibility in web applications. A very large chunk of it is help files, documentation, and cross-reference. Better input handling. Error messages that provide more than a code that uniquely identifies where something blew up. Now, how many software packages that were otherwise very big Triangle-wise got delivered missing some of the above? Quality doesn’t really sit in the center of the chart, though it’s sometimes easier to draw that way. It’s off in the Z-axis; it’s its own tone in the harmony. It’s just a little too close to “Scope” in its characteristics to get talked about much, and you need to shift the pitch (for either metaphor) to pay attention to it. Go grab a 4-sider die, sight along one of the edges, label the front corner “Scope”, the back one “Quality”, and the other two “Resource” and “Time”. What do you see then? Why, the Iron Triangle staring at you. With a sloppy hidden bit. And what goes into that hidden bit? Pretty graphics. Cross-browser compatibility in web applications. A very large chunk of it is help files, documentation, and cross-reference. Better input handling. Error messages that provide more than a code that uniquely identifies where something blew up.

Now, how many software packages that were otherwise very big Triangle-wise got delivered missing some of the above?

]]>