Estimating is really hard. It's not something I've had to do until my current role leading frontend development efforts. It takes me several days to come up wi

Estimating is really hard. It's not something I've had to do until my current role leading frontend development efforts. It takes me several days to come up with a plan of action for planning several months of work for the team. In this action plan, I map out every task that needs to be done, and figure out which tasks that can be done in parallel. Which ones have dependencies on each other. How to prioritize features that matter first. Which things need more discovery. Which features are high risk and how to mitigate. How to do a progressive demo to the stakeholders while still leaving time to tackle tech debt. How to divvy up tasks efficiently between teams so resources are utilized properly. The article captures my thought process on time estimation. Being able to make an estimate, and deliver on it, can really drive your career. Businesses almost always have a hard deadline. You have to be able to put yourself in everyone's shoes but with enough practice it's not so bad. Being able to commit to this plan let's you have conversations to deviate or adjust as needed. No estimations are ever 100% accurate, but getting something close makes planning each sprint significantly easier