Member-only story
Assumptions Are Deadly to Development Teams and Software Projects
Leave no assumption alive
Software developers should treat assumptions the same way they treat seeing their boss working in their underwear — Keep asking questions until they go away?
What is the deadliest weapon to break code, design, architecture and project plans? Change is.
Change is the plan breaker, the code destroyer, the requirements ripper upper and chaos bringer. Change is dangerous. Everyone is on high alert to stop it change from disrupting their project.
The great trick change ever pulled was convincing developers to assume they knew how things worked and create code on top of it.
Assumptions are deadly
Assumptions are like the big bad wolf disguised as Granny, ready to eat your project for dinner. Assumptions are unclarified requirement changes everyone misses.
Assumptions is change developers created themselves and don’t know it exists yet. Assumptions are unsaid facts everyone knows, they are so sure of them no one needs to document them as requirements.
