The Manny Doctrine
The Manny Doctrine states that if the complexity of a system raises above a certain threshold causing either of the following to be true:
1. The cost in lost man-hours of maintaining or updating the system exceeds 1/4th the cost of replacing it.
2. The prospect of maintaining or updating the system causes an engineer to fall into clinical depression.
The system should then be scrapped entirely and re-built from the ground up by competent engineers.
1. The cost in lost man-hours of maintaining or updating the system exceeds 1/4th the cost of replacing it.
2. The prospect of maintaining or updating the system causes an engineer to fall into clinical depression.
The system should then be scrapped entirely and re-built from the ground up by competent engineers.
*During sprint planning*
SCRUM master -"We have some upcoming work to update our data ingress to match v3.0 of our ICD"
Engineer - "That system is awful, I call The Manny Doctrine"
SCRUM master - "Hmm, it is a bit of a black box. Alright, we'll scope out a re-design."
SCRUM master -"We have some upcoming work to update our data ingress to match v3.0 of our ICD"
Engineer - "That system is awful, I call The Manny Doctrine"
SCRUM master - "Hmm, it is a bit of a black box. Alright, we'll scope out a re-design."