00:10 - Planning exercise (40m)

[asgrim]

• [x] Perform an event storming session (@ocramius wants to join too) to explore the domain more
• [x] Define the ubiquitous language
• [x] Ensure all eventualities are thought about
• [x] Produce domain model (stickies is fine) from the ES session, attach to repo
• [x] Flesh out the book-hotel.feature with any new discoveries / business rules
• [x] Estimations - how to estimate the build of the feature
  • Break down requirements & explore as MUCH as possible (event storming with business stakeholders can help!)
  • Write down ALL your assumptions
  • The more time you spend estimating, the more accurate the estimate becomes (potentially shorter dev time too)
  • Understand risk: unknowns = higher risk. Even giving an estimate is a risk (you could be held accountable, despite non-binding estimates)
  • Use ranges, and remember you ALWAYS underestimate: x2, x3, x5 or even x10 is not unbelievable...
  • Use feedback loops; record your estimates, and how long it actually took to give an idea of accuracy
  • Consider NON development time: meetings, QA, PR loops, unexpected, unplanned things ALWAYS happen
  • Key is RECORDING in DETAIL (time estimated, time taken). Analyse this.
  • Understand:
    • What took longer than expected (why?)
    • What was more complicated than expected (why?)
    • Additional tasks that weren't included but [should've|could've] been foreseen

[asgrim]