Blink Estimation
Blink Estimation is a rapid estimation technique used by teams to quickly assess the size, complexity, or effort required for implementing software features or tasks, based on intuition and experience rather than detailed analysis.
Goal
The goal of Blink Estimation is to facilitate swift decision-making and planning, enabling teams to move quickly without getting bogged down in detailed estimation processes.
Context
Throughout the Continuous Design validation the solution may have iterated beyond the initial idea. This is a good time to re-validate the Feasibility of the solution. We are not looking for a detailed estimate that will be used as a timeline for implementation but rather an indication of whether we should pursue the solution further.
Format
- Preparation: Document a high-level overview of the feature or product to be estimated.
- Quick Review: Briefly discuss the documentation to ensure understanding.
- Individual Estimation: Team members independently record their estimation.
- Reveal and Discuss: Simultaneously reveal estimations and discuss significant discrepancies to reach consensus.
- Finalise Estimation: Agree on a final estimation.
Inputs
| Artifact | Description |
|---|---|
| Validated Solution | A solution that has been tested and validated with users through Continuous Design, ensuring that it meets their needs and expectations. |
Outputs
| Artifact | Description | Benefits |
|---|---|---|
| Go / No Go Decision | A decision on whether to proceed with the solution based on the estimated effort. | Prevent teams from blindly following complex solutions and evaluate whether there are other, more feasible, solutions that could be pursued. |
Anti-patterns
- Lack of Experience: Gut feel comes from experience. If the team is not experienced in the domain, the estimates will be less accurate.
- Ignoring Team Input: When one or a few team members dominate the estimation process, leading to less accurate or biased estimates.
- Skipping Rationale: Not discussing or documenting the rationale behind estimates, making it difficult to understand or revise estimates later.