🤯 Why you need an Effort Estimator

• Are your features missing the release dates you planned?
• You assumed your feature would take 2 days to go live and but it really took 2 business weeks
• Not sure how your technical team estimates time for development?

🤖 When to use?

• You received a request from a stakeholder for a feature. You want to evaluate the priority of this request based on an estimated cost/effort to build this feature.
• You are working on an idea. You have a rough sketch of the solution. You want to size the effort/cost to build your solution before going to your tech team.
• You are working on a PRD. You have a low-fidelity prototype/wireframe.

✅ Before you estimate, you should have

• [ ] A basic definition of your solution.

• [ ] Wireframe or Rough sketch of your prototype.

❓ How to use it?

1. Have the wireframes or rough sketches ready for reference. Let’s call each wireframe or rough sketch a SCREEN.
2. Name each screen. Add it to the table below in the sequence of your workflow.
3. For each screen/row
   1. Click on 🏔️ Effort Estimator.
   2. Input details based on the elements on your screen.
   3. Record the “Effort in Hours” & “Effort Coefficient” values.
4. If you are confused about a big feature or a product, break it down into individual use stories or use cases before using the Effort Estimator.