Let’s build an airport
07 Nov 2017 — 0 Comments — — Estimated reading time: 3 minutes read
Once again a talk I held. This time it is quite a long time ago that I talked about estimating large scale products on UX Camp West 2016 in Cologne. Two weeks ago I repeated the talk in an internal meeting at McCann. And I remembered that I still wanted to blog about it.
So here we go. The first thing: why do I talk about large scale projects? Because estimating is always rough and inherits a lot of insecurity. The larger a project is the less important becomes estimating one item wrong. Basically, estimating large projects accurately is much easier then small ones.
So why do we estimate a project?
- We want to plan timings, workload and staffing.
- We need to allocate a budget
- We get some kind of raw concept
And getting there requires three simple steps:
- Gather all information about the project using any tool your familiar with. From a UX perspective this could be brief, vision, personas, scenarios, customer journeys, etc.
- Define the tasks that need to done. First the high level tasks (I know this is wrong, but I call those epics). And when that is done, break down those tasks to smaller manageable ones (again wrong: stories). Those stories should be possible to do in less than 5 days.
- Go through the stories and assign a complexitity and effort measurement. I usually use small, medium and high.
One thing is really important to me: you should always estimate collaboratively.
I have created an Excel workbook that can help you with the estimation. Feel free to use it.
This Estimation Tool is designed to help you to estimate large scale digital products. The tool is provided as is with no warranty. In order to adjust the tool to your project, please alter the values provided in the Configuration tab. All calculations are based on the information provided there.
The Estimation Tool is licensed under a Creative Commons Attribution-ShareAlike 3.0 Germany License.