Comments on: The Broken Iron Triangle Is Broken http://www.codesqueeze.com/the-broken-iron-triangle-is-broken/ Ideas for building efficient developers and software Tue, 09 Mar 2010 19:29:12 -0500 hourly 1 By: The Trouble With Triangles - Life of an Agile Manager http://www.codesqueeze.com/the-broken-iron-triangle-is-broken/#comment-9847 The Trouble With Triangles - Life of an Agile Manager Sat, 20 Feb 2010 16:21:28 +0000 http://www.codesqueeze.com/the-broken-iron-triangle-is-broken/#comment-9847 [...] few years. There’s Jurgen Appelo’s Iron Square, Jim Highsmith’s Agile Triangle, Max Pool’s Iron Line, and any number of other variations. At first glance, these seem like good thought models which [...] [...] few years. There’s Jurgen Appelo’s Iron Square, Jim Highsmith’s Agile Triangle, Max Pool’s Iron Line, and any number of other variations. At first glance, these seem like good thought models which [...]

]]> By: Max Pool http://www.codesqueeze.com/the-broken-iron-triangle-is-broken/#comment-326 Max Pool Tue, 25 Sep 2007 16:30:43 +0000 http://www.codesqueeze.com/the-broken-iron-triangle-is-broken/#comment-326 @Karl The only thing I don't like about the Contractors Triangle is it places quality at one of the corners. In my mind, lack of unit tests and quality is never an option - it cuts too deeply into my professional pride. Would you want your name attached to crummy software even if it was the best business decision for your client? Personal preference I guess... @Karl

The only thing I don’t like about the Contractors Triangle is it places quality at one of the corners. In my mind, lack of unit tests and quality is never an option – it cuts too deeply into my professional pride.

Would you want your name attached to crummy software even if it was the best business decision for your client? Personal preference I guess…

]]> By: Relationship » The Broken Iron Triangle Is Broken http://www.codesqueeze.com/the-broken-iron-triangle-is-broken/#comment-325 Relationship » The Broken Iron Triangle Is Broken Tue, 25 Sep 2007 13:06:02 +0000 http://www.codesqueeze.com/the-broken-iron-triangle-is-broken/#comment-325 [...] mariooster wrote an interesting post today onHere’s a quick excerptIf you have a good working relationship with your client, you can instead, use the Iron Line as a scale which to balance the two end points. Do they want 80% control of the budget, thus giving up 80% control of the scope? … [...] [...] mariooster wrote an interesting post today onHere’s a quick excerptIf you have a good working relationship with your client, you can instead, use the Iron Line as a scale which to balance the two end points. Do they want 80% control of the budget, thus giving up 80% control of the scope? … [...]

]]> By: Karl Katzke http://www.codesqueeze.com/the-broken-iron-triangle-is-broken/#comment-321 Karl Katzke Mon, 24 Sep 2007 13:21:55 +0000 http://www.codesqueeze.com/the-broken-iron-triangle-is-broken/#comment-321 I usually use the "Contractor's Triangle:" -- "Good, Fast, Cheap, pick any two" to get an idea of what my client wanted before we started a project. But I *insisted* on having a good control of scope by implementing a ticket system and setting up a "Current", "Next", "Future" version system. We'd go through a list of tickets together in Excel and I'd put my choices and they could confirm them. I usually use the “Contractor’s Triangle:” — “Good, Fast, Cheap, pick any two” to get an idea of what my client wanted before we started a project. But I *insisted* on having a good control of scope by implementing a ticket system and setting up a “Current”, “Next”, “Future” version system. We’d go through a list of tickets together in Excel and I’d put my choices and they could confirm them.

]]>