Skip to content

change wording in project triangle analogy? #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

change wording in project triangle analogy? #13

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion wisdom.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -132,7 +132,7 @@ Brief introductory remarks regarding the Project:

----

- Every project is a triangle made of time, money, and quality; shortening the length of one side necessarily lengthens one or—more often—*both* of the other sides.
- Every project is a triangle made of time, money, and quality; trying to improve one side necessarily worsens one or—more often—*both* of the other sides.
- Less well known is that we each tend to blow it hardest in estimating the sides of the triangle we least understand or respect.
- Kindly note that the grave existential truth of the Project Management Triangle is *non-negotiable*. People **hate** this. Which is normal.
- If the person with whom you are negotiating finds it difficult to provide a decisive budget estimate for their project, ask them to try and situate it between two orders of magnitude. As in, "How many zeroes are we talking about here?" Quickly discovering that your ballpark figures are 2 to 6 zeroes apart can save you both a *lot* of time and frustration.
Expand Down