TOPIC: Using Agile Constraint Triangle

I get that Value is the least flexible constraint in the triangle. The traditional Time-Cost-Scope is consolidated into the Constraints vertex. My question is the remaining vertex: Quality. Is the triangle saying that it is acceptable to affect Quality to preserve Value? Since Quality is its own vertex suggests it can be adjusted to preserve the other two sides. I get that it is important, but want to make sure, it is reasonable to impact quality (assuming within acceptable thresholds)?

I believe so. Quality could be reduced if that was acceptable, and helped achieved another aim (e.g. delivering faster, more cheaply etc).

Thank you Elizabeth. Interesting there isn't a lot of detail on this; I mean, even reading articles off the internet-- most just assert that it is important, or critical to value delivery, but there isn't a lot of detail on how it functions within the trade-off's. I almost have to question if it should actually live as it's own vertex in the triangle...

Hi Michael,

I hope this article will help you: Six Constraints