Skip to main content

How to make the classic PM Iron Triangle

Agile Tetrahedron Model
I was in a workshop just the other day and asked if everyone was aware of the dynamics of the classic project management iron triangle.  While most people had heard of it, it was apparent that few actually understood the dynamics of the model.
For a better model than the PM triangle see the Agile Tetrahedron.
Perhaps a physical model of the PM triangle would help people to grasp the meaning.  So let's build an adjustable Iron Triangle out of something.  It needs to be inexpensive, made from common items, and build-able in 20 minutes.

Here's is how to make a PM iron triangle out of plastic drinking straws.

You need:

  • Straws - the bendable kind - multi-colored.
  • Scissors
I used 3 yellow straws for the flexible corner pieces.  Cutting the straw just about 2cm beyond the flex on each side.  I cut the straw at an angle.  This makes assemble easier, as you must crimp and slide this piece into other straws.  The taper makes this easier.



Cutting diagram & finished triangle
Working on the red side.  I use 2 red straws.  Cut one into 3 pieces, throwing away the flex part.  The other is cut just to the side of the flex and throwing away the flex part also.  You are left with 3 red pieces, one short and two long.  Slide the yellow flex parts into the short red piece and the other yellow flex into one of the long red pieces.

One side of the adjustable triangle.
Repeat for the green side and the orange side.

All the pieces of the triangle
With the remaining long pieces we make the inner tubes.  Crimp the straw longitudinally so that it will become smaller and slide into the other straws.  Insert one end into the short red straw.  Do the same for the green and orange sides.
The 3 angles
 Now the angles may be assembled into a triangle.  Sliding one straw over the crimped straw.  This allows the sides to adjust in length.  And flex at the corners.

You now have an adjustable Project Manage Iron Triangle.  Label the sides and start playing with it.  Enjoy your new found understanding of the constraints of projects.

If you need an explanation of the power of the Iron Triangle and its limitations as a model for software development listen to the Agile in 3 Minutes: episode 21 Predict.


Post a Comment

Most Popular on Agile Complexification Inverter

Exercise:: Definition of Ready & Done

Assuming you are on a Scrum/Agile software development team, then one of the first 'working agreements' you have created with your team is a 'Definition of Done' - right?



Oh - you don't have a definition of what aspects a user story that is done will exhibit. Well then, you need to create a list of attributes of a done story. One way to do this would be to Google 'definition of done' ... here let me do that for you: http://tinyurl.com/3br9o6n. Then you could just use someone else's definition - there DONE!

But that would be cheating -- right? It is not the artifact - the list of done criteria, that is important for your team - it is the act of doing it for themselves, it is that shared understanding of having a debate over some of the gray areas that create a true working agreement. If some of the team believes that a story being done means that there can be no bugs found in the code - but some believe that there can be some minor issues - well, …

Elements of an Effective Scrum Task Board

What are the individual elements that make a Scrum task board effective for the team and the leadership of the team?  There are a few basic elements that are quite obvious when you have seen a few good Scrum boards... but there are some other elements that appear to elude even the most servant of leaders of Scrum teams.









In general I'm referring to a physical Scrum board.  Although software applications will replicated may of the elements of a good Scrum board there will be affordances that are not easily replicated.  And software applications offer features not easily implemented in the physical domain also.





Scrum Info Radiator Checklist (PDF) Basic Elements
Board Framework - columns and rows laid out in bold colors (blue tape works well)
Attributes:  space for the total number of stickies that will need to belong in each cell of the matrix;  lines that are not easy eroded, but are also easy to replace;  see Orientation.

Columns (or Rows) - labeled
    Stories
    To Do
    Work In P…

Webinar: Collaboration at Scale: Defining Done, Ready, and NO.

I was invited to participate in a Scrum Alliance Webinar.  Maybe you would like to listen to us in a discussion of techniques to collaborate at scale (remotely and with many people).  The topic is one that I've got some experience in discussions - yet I never seem to get to done...
Collaboration at Scale: Defining Done and Ready and NO for Distributed Teams
With Joel Bancroft-Connors, Agile Organizational Coach; David A. Koontz, Agile Transition Guide; and Luke Hohmann, CEO and Founder of Conteneo, Inc.


14 February 2018 11 a.m. ET (USA).




The Scrum Guide is pretty clear on the criticality of the definition of Done: "When a Product Backlog item or an Increment is described as "Done," everyone must understand what "Done" means. However, the Scrum Guide ALSO says that the definition of Done can "vary significantly per Scrum Team." This leads us to examine when and how the definition of Done should vary, how distributed teams should cr…

A T-Shaped 21st Century Knowledge Worker

Knowledge workers in the 21st Century must have many areas of deep knowledge, while also be capable of collaboration across multiple other domains with dissimilar T-shaped individuals.  This description of a person is a metaphor.  Compare it to the shape of the "I" in the classic saying there is no "I" in Team.


I first read about Scott Ambler's term "Generalizing Specialist" - but it's so hard to remember the proper order of the words... get it backwards and it has an inverted meaning... T-Shaped is easier to remember. 
A generalizing specialist is someone who:
Has one or more technical specialties (e.g. Java programming, Project Management, Database Administration, ...). Has at least a general knowledge of software development. Has at least a general knowledge of the business domain in which they work. Actively seeks to gain new skills in both their existing specialties as well as in other areas, including both technical and domain areas.  General…

A FAILURE to Communicate

I was working with a failing team some time ago.  I use "failing" to describe the outcome of the team - not the people on the team.  Are you OK with that description?



An issue arrose in the stand up - a team member that was to verify the quality of a procedure did so and reported that there were a few records that didn't match expectation in the data set.  Upon inquire the number of records not matching was over 2000.  Most people acknowledged immediately the exaggeration - I could tell by the laughter.  After about 10 minutes of discussing the details of the problem - it appeared the team had a handle on the specific situation.

I stopped the discussion and inquired if they could name the impediment.  One team member did a great job of describing the impediment as a _communication gap_.  Wonderful - I could work with that - the problem had a name and it didn't include anyones Proper Name.

"If the problem has a first name; we are going to have a problem."

I&#…