I'm looking for advice on how to structure and map a client's project to ensure accurate estimations before breaking it down into tasks for different development teams—like frontend, backend, and mobile. After discussing the client's problems and ideas, I need to create some sort of diagram or overview for proper project estimation.
What approaches work best? Should I go with a system architecture diagram, a user flow, or a high-level feature map before diving into task planning? Additionally, how can I forecast things like project shipping time, estimated costs, manpower requirements, and ongoing maintenance expenses after releasing version 1.0?
3 Answers
When I encounter similar situations, I use the Fibonacci series for estimation. It helps break larger tasks into smaller, manageable parts for tighter estimates.
It’s important to break down the project before trying to estimate anything. Think of it like planning a building project—you can’t know the time or cost without breaking it down into distinct parts first. Even with experience, you can’t accurately predict without a detailed breakdown. Take the time to do the work; shortcuts won’t help in the long run.
Let’s be real—the software industry isn't great at estimations; it’s been a struggle for decades. Just keep that in mind when planning your approach.
Asking questions isn’t a shortcut! It’s about providing a reasonable estimate without making false promises to the client. Balancing honesty with what’s possible is key.