could pop up in your development that might become a road block ◦ unfamiliar part of the app? ◦ modal overlay: i’ve run into issues with those before? ◦ frontend: i’m clueless? ◦ are there even tests for this yet? ◦ how reproducible is the issue? ◦ how complex will the solution need to be?
the complications you considered, and throw some number at it. The initial estimate doesn’t matter as much as how that estimate evolves. If you have no clue, break it down into smaller pieces: • how long do migrations take to write? to optimize? • how long does writing the test take? • how long does review usually take?
a ballpark estimate so they are in the loop. You’ll probably go over, that’s fine. Use phabricator tickets, phabricator work boards, spec slides, proposal documents But, yes. You care. The estimate is for yourself to compare time spent vs. work done. Keep your own notes to stay on track and within scope
working relative to your initial estimate. Hours estimate: check yourself at each increment of the estimate Days estimate: check yourself at each partial increment of the estimate Weeks estimate: you done messed up. get back to the first step, then we’ll talk.
by large factors, it’s time to re-scope. Break it down into smaller pieces: • Consider the engineers who will be reviewing this code • Consider your own concentration: don’t solve everything at the same time • Split up work vertically by component or horizontally by layer in stack Cut out pieces: • Don’t solve everything at the same time. Scope down, postpone peripheral fixes.
experience, tells me writing a migration to archive notifications and fix how they’re archived in app will take a day. ▪ Migrations for updating a large set of data related to several other models generally takes me half a day to find a query that is optimal and runs in a reasonable amount of time. ▪ Writing a test for notification archival and fixing the notification should take about half a day. ▪ Code diffs have been averaging an hour or two turnaround.
the migration written, behind schedule but not significantly ▪ assignment notifications still not down to a reasonable count for mike ↳ what did we miss? those students are from last year, maybe we could also archive the assignment notifications for students that have completed their course? A few more hours: ▪ Half focused on other cases of when notifications should be archived ▪ Half focused on solving the checkpoint completion notification archival problem
as is, I’m at 4x my gut estimate: ▪ Revisit the initial scoping steps, dividing future work into distinct pieces Enrollment Changes Source: Message Source: Assignment Source: Nudge Source: FunctionalAssessment M M T E S T T E S T T E S T T E S T freeze with mentor freeze without mentor, unfreeze transfer mentor dropout course completion M M T E S T T E S T T E S T T E S T T E S T
the task: ▪ I investigated the end-of-course processes for a student ↳ looks like there’s 2 rake tasks that run on the last day of a course: email and graduation standing fix ↳ those should be consolidated into one graduation task ↳ oh man, graduation could balloon into so many tasks, how would be deal with that..? ▪ Postpone the end-of-course problem, this is now out of scope ▪ Don’t ignore it: throw thoughts and notes into a new phab ticket