Avoiding The Iron Triangle
Many software development projects run afoul of the "Iron Triangle" of project management: the interrelated constraints of Scope, Schedule, and Resources. Simplistically, a change in any one of these constraints has a necessary effect on either one or both of the other two. If the three constraints are out of balance with each other at the beginning of the project, then one or more of them must change/break or the resulting quality of the project is destroyed by artificially meeting the constraints by cutting corners.
Your Author:
John Lewis
John A. Lewis is the Chief Software Architect for Unicon Inc, the leading independent provider of open source training, consulting, and support in higher education. John is a 16 year veteran of the software engineering industry. His passions are large-scale enterprise architecture, open-source technologies, and agile software development methods. John has been working heavily in Java-based enterprise information portals since 2001 and is the lead developer of Spring Portlet MVC, which provides JSR 168 support in the Spring Framework. He is also active in several higher education open source communities, including uPortal and Sakai.
Blog Disclaimer: Opinions expressed in my blog are just that: opinions. Don’t have a fit if you think they’re wrong — post your comment or write your own blog.
.jpg){kind=small}
