I don’t know who Brasington is, but I came across this list of Law’s. My response is below.
- Brasington’s 7th Law: Projects quickly progress until they become 90% complete, then they remain 90% complete forever.
Build system in an incremental and iterative fashion. This way you have value along he way, and when you reach 90% complete you’ve been delivery value long before.
- Brasington’s 8th Law: If project content is allowed to change freely, the rate of change will exceed the rate of progress.
Garbage in Garbage Out is applicable to project requirements as well
- Brasington’s 9th Law: A carelessly planned project takes three times longer to complete than expected; a carefully planned one will take only twice as long.
A Plan is a strategy for the successful completion of the project. Whether writing software or flying to the moon. No Plan, you lost before you start.
- Brasington’s Insight: One advantage of fuzzy project objectives is that they let you avoid the embarrassment of estimating the costs.
To remove the fuzzy-ness, clear and concise descriptions of “done” for the next iteration are needed. This is actually hard work, requires discipline, and most of all leadership
- Brasington’s Note: Project teams detest project reporting because it vividly manifests their lack of progress.
Measuring physical percent complete means knowing what done looks like up front, in units of measure meaningful to the customer.
Original post: Herding Cats


You found a list I put together maybe 25 years ago to bring an IT project view to Murphy’s Laws. Originally in a text file in DOS (yes I am that old).