“Let’s import this 100GB CSV into a PostgreSQL table.”
One simple ask, articulated correctly, might seem to reduce the cost of a requirement.
It is a simple requirement; how hard can it be? It should not take more than a day.
As soon you uncompress the requirements, inevitably, the estimate will go up.
How do you know when you need to uncompress a requirement? It is very simple: if no one in your team has done it before.
If no one in your team has experience with the compressed requirement, your or your team’s estimates are wrong.
Uncompress the requirement into multiple tasks, then estimate.
Founder & CEO at InTheValley
I build remote engineering teams for startups. My blog uses a proprietary platform to generate in-depth articles about something I’m passionate about: Advertising.
Latest posts by Leo Celis (see all)
- Contrasting Traditional vs. Remote Team Management Tactics - 11/20/24
- The Role of Color in Brand Identity - 10/23/24
- Human-in-the-Loop for Bias Mitigation - 10/16/24