Effort Estimation for Beginners: Split the Work, Give 3 Day Counts, Agree on a Buffered Estimate

Project & Development

Effort Estimation for Beginners: Split the Work, Give 3 Day Counts, Agree on a Buffered Estimate

This effort estimation template for beginners walks a first-time estimator through splitting work, giving three day counts, adding a buffer and agreeing on the number. The whiteboard has 4 pages - page 1 aligns scope, assumptions and the work branches; page 2 tables best, likely and worst days with the expected value; page 3 sorts wide-range tasks, compares past results and places the buffer; page 4 sets the order to present, owners and review days. The task board has four columns - before estimating, working out days, checking the spread, agreed with requester - with 4 parent tasks and 3 subtasks each. Expected = (best + likely x 4 + worst) / 6, and the boards carry worked examples, so you only swap in your numbers. Share it with a limited-visibility team so the person doing the work gives the days and can explain them.

0 Likes 0 Copies Author: WeProcess
effort estimation three-point estimate how to estimate work breakdown for beginners
Sign up free and use this template

Once you have a free account, you can copy this template from the marketplace

Whiteboard preview

Preview mode Effort Estimation for Beginners: Split the Work, Give 3 Day Counts, Agree on a Buffered Estimate

Whiteboard preview

① What you are estimating and the dea... ② Work that is included ③ Work that is not included ④ Assumptions behind the estimate ⑥ How to get the expected value (read... ⑦ Three day counts per task (one row ... ⑧ Sorting the shaky tasks (place task... Wide spread x small impact Wide spread x big impact Narrow spread x small impact Narrow spread x big impact ⑨ Results from similar past work ⑩ Reasons for the spread ⑪ Where to put the buffer ⑫ Estimate with buffer (the total fro... ⑬ Order for presenting it (give the r... ⑭ Owner, due date and review day per ... ⑮ What you agreed and the first step Effort Estimation... How to use (4 pag... Agreed number or ... Assumptions and r... Reasons for sprea... Past results and ... 1/4 Set the scope Ctrl+F / ⌘F : 2/4... → 2/4 2/4 Make three day es... ↙ 3/4 What you are estimatinge.g. Build a sign-up form for an internal event Who gets the estimate, and whene.g. Give it to the requester (General Affairs) on October 20They want to go live by end of November Who builds it, and the unit of dayse.g. Two people build itThe unit is "days of one person working with focus" e.g. Sign-up screen and input checks e.g. Confirmation email to sign-ups e.g. Testing and going live Do not miss work the requester thinks is included e.g. A report screen listing sign-ups e.g. An English version of the screens Add a one-line reason why it is out If asked later, make it a separate estimate e.g. The input fields are final by end of October e.g. We get the booking system manual from them If an assumption breaks, estimate again Mark the assumptions you want the requester to confirm ⑤ Split the work ... e.g. Build the sign-up form Screen design e.g. Design the screen and build input fields Outside links e.g. Connect to the booking system Input logic e.g. Input checks and confirmation email Finishing e.g. Testing and going live FormulaExpected = (Best + Likely x 4 + Worst) / 6Range = Worst - BestThe expected value is the day count you use (likely happens most, so x 4) Worked examplee.g. Booking system link: 2, 3 and 10 days(2 + 3 x 4 + 10) / 6 = 24 / 6 = 4 daysRange is 10 - 2 = 8 days How to set the three day countsBest: nothing gets in the wayLikely: what is most likely to happenWorst: several foreseeable troubles pile up (leave out disasters) Best Likely Worst Expected Range Screen design e.g. 1 day 1.5 days 2 days 1.5 days 1 day Input fields 1 day 2 days 3 days 2 days 2 days Input checks 1 day 1 day 4 days 1.5 days 3 days Confirmation email 0.5 days 1 day 1.5 days 1 day 1 day Booking system link 2 days 3 days 10 days 4 days 8 days Testing and going... 1 day 3 days 5 days 3 days 4 days Total 6.5 days 11.5 days 25.5 days 13 days Widest range first, to ⑧ 3/4 Review the shaky ... → 4/4 4/4 Agree on the esti... 縦軸: Spread in day... e.g. Input checks (3-day range). No buffer; decide in advance which parts can wait if late. e.g. Booking system link (8-day range). Buffer goes here. Try a small test first to cut the spread. e.g. Confirmation email (1-day range). No buffer; go with the likely days. e.g. Input fields (2-day range). If late, other work stops, so start early and hold the schedule. e.g. Last sign-up form: estimated 5 days, took 8 e.g. Work linking to outside systems took about twice as long as planned both times If there is no history, ask an expert and write it down If a task was off, rewrite its days in ⑦ e.g. The booking system manual has not arrived yet e.g. Input fields are waiting for the requester to confirm Write what is undecided, not who is to blame If you know when a reason goes away, add the date e.g. Put 3 days of buffer after the booking system link e.g. 3 days is half of the 6 days from worst - expected Do not spread it over each task; put it in one place Add a one-line reason (to explain it to the requester) Expected totale.g. 13 days (total row of ⑦) Delay the buffer can absorbe.g. Up to 7 days (4 + 3 buffer) for the booking system link still fits in 16If it looks like more, review the plan Estimatee.g. 16 days = 13 days + 3 daysTwo people share the work (split it in ⑭) 1. Bottom lineGive the days and go-live date firste.g. 16 days of work. Two people can go live by end of November. 2. AssumptionsState the conditionse.g. The input fields must be final by end of October. 3. Spread and bufferSay where the buffer sitse.g. The booking system link is hard to read, so we added 3 days. 4. Review dayDecide when to review the numberse.g. Review on November 5 after trying the link. Owner Due date Review day Agreed days Screen design e.g. Alex Nov 7 Oct 31 3.5 days Input logic Ben Nov 7 Oct 31 2.5 days Outside links Alex and Ben Nov 21 Nov 5 7 days (incl. 3-day buffer) Finishing Ben Nov 28 Nov 21 3 days What you agreed with the requestere.g. Agreed on 16 days and going live by end of NovemberThe report screen (③) becomes a separate estimate Telling them when an assumption breakse.g. If the input fields change in November or laterSet a day with the requester that week to re-estimate First stepe.g. Tomorrow, remind the requester about the booking system manualOwner: ____ → 2/4 Make three day es... ↙ 3/4 Review the shaky ... → 4/4 Agree on the esti...
100%

Drag to move, scroll to zoom

Task board contents

Before estimating 16 items

Set the scope
Make 3 estimates
Review shaky tasks
Agree on estimate
Write the target
Decide in and out
Split the work
Read the formula
Enter three counts
Work out the range
Place wide tasks
Compare past data
Choose the buffer
Present in order
Assign owners
Pick the first step

Working out days 0 items

Checking the spread 0 items

Agreed with requester 0 items

← Back to templates