Upgrade to Pro — share decks privately, control downloads, hide ads and more …

๐ŸŽŸ Tech Delivery Blueprint (Agile)

๐ŸŽŸ Tech Delivery Blueprintย (Agile)

Overview of how i've seen Tech delivery done well, for you to use as a blueprint when creating your squads

Callum Silcock

January 29, 2020
Tweet

More Decks by Callum Silcock

Other Decks in Business

Transcript

  1. There are many methods of how to do tech delivery,

    this is what I've seen work well, the idea is for you to use it as a blueprint not a ruleb k
  2. โ”‚ โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ” .โ”€. .โ”€. โ”‚ โ”‚ ( ) โ”‚ (

    ) โ”‚ โ”Œ โ”€ โ”€ โ”€ โ”€ โ”€ โ”€ โ”€ โ”€ โ”€ โ”€โ–ผโ”€ โ”€ โ”€ โ”€ โ”€ โ”€ โ”Œ`โ”€'โ” Requirements โ”Œ`โ”€'โ” โ”‚ Todo โ”‚ Doing โ”‚ Review โ”‚ Done โ”‚ โ”‚ โ”‚โ”€โ”€โ”€โ”€โ”€โ”€โ”‚โ”€โ”€โ”€โ”€โ”€โ”€>โ”‚PO โ”‚โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜ โ”‚โ”Œโ”€โ”€โ”€โ”ฌโ”€โ”โ”‚โ”Œโ”€โ”€โ”€โ”ฌโ”€โ”โ”‚ โ”‚โ”Œโ”€โ”€โ”€โ”ฌโ”€โ” โ””โ”€โ”€โ”€โ”˜ โ””โ”€โ”€โ”€โ”˜ โ”‚ โ””โ”€โ”‚โ”‚โ”‚ โ””โ”€โ”‚โ”‚ โ”‚โ”‚ โ””โ”€โ”‚โ”‚ Design โ”‚ โ”‚ Create โ”‚โ”‚Storyโ”‚โ”‚โ”‚Storyโ”‚โ”‚ โ”‚โ”‚-----โ”‚ Tech โ–ผ โ””โ”€โ”€โ”€โ”€โ”€โ”˜โ”‚โ””โ”€โ”€โ”€โ”€โ”€โ”˜โ”‚ โ”‚โ””โ”€โ”€โ”€โ”€โ”€โ”˜โ”‚ COps โ”‚ โ”Œโ”€โ”€โ”€โ”ฌโ”€โ” โ”” โ”€ โ–ฒ โ”€ โ”€ โ”€ โ”€ โ”€ โ”€ โ”€ โ”€ โ”€ โ”€ โ”€ โ”€โ”‚โ”€ โ”€ etc. โ”‚ โ””โ”€โ”‚ โ”‚ Kanban Board โ”‚ โ”‚ โ”‚Epic โ”‚ โ”‚ โ”‚ โ”€ โ”€ โ”€ โ”€ โ”€ โ”€ โ”€ โ”€ โ””โ”€โ”€โ”€โ”€โ”€โ”˜ Create Sprint โ”‚ โ–ฒ โ”‚ Breakdown โ”‚ โ–ผ โ”‚ โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”ผโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ” โ”‚ .โ”€. โ”‚ โ–ผ โ–ผ โ–ผ .โ”€. ( ) โ”‚ โ”Œโ”€โ”€โ”€โ”ฌโ”€โ” โ”Œโ”€โ”€โ”€โ”ฌโ”€โ” โ”Œโ”€โ”€โ”€โ”ฌโ”€โ” ( ) โ”Œ`โ”€'โ”€โ” โ”‚ โ”‚ โ””โ”€โ”‚ โ”‚ โ””โ”€โ”‚ โ”‚ โ””โ”€โ”‚ Pointโ”Œ`โ”€'โ” โ”‚Userโ”‚ โ”‚ โ”‚Storyโ”‚ โ”‚Storyโ”‚ โ”‚Storyโ”‚โ”€โ”€โ”€โ”€โ”€โ–ถโ”‚Devโ”‚ โ””โ”€โ”€โ”€โ”€โ”˜ โ”‚ โ””โ”€โ”€โ”€โ”€โ”€โ”˜ โ””โ”€โ”€โ”€โ”€โ”€โ”˜ โ””โ”€โ”€โ”€โ”€โ”€โ”˜ โ””โ”€โ”€โ”€โ”˜ โ”‚ โ”‚ โ”‚ โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜ Analysis
  3. ! CREATING EPICS - Product will generate these with help

    of the business owner - What are the must haves vs nice to haves - Start thinking about these from a user perspective - Validating the ideas are worth building for - What is the success criteria - Design / Tech input (eg. whether achievable)
  4. ! EPIC ESTIMATION - Usually per quarter before defining your

    OKRs - T-shirt size - XS S M L XL - Can be tacked on to other meetings (eg. backlog grooming or sprint planning)
  5. ! WHAT DO YOUR STORIES LOOK LIKE? - Given when

    then syntax (as a user) - Requirements based - Light vs Heavy - Whatever the format, your team needs to decide on it
  6. ! STORY CREATION SESSION - Product / Rotating Devs !

    / UXD - Take those epics and break them down - Write down what you think will help - Split between function or together
  7. ! STORY ESTIMATION - Dev / Lead (no need for

    product) - Go in with no context - Write down assumptions - Throw things back to product - COMPLEXITY NOT TIME
  8. ! SPRINT PLANNING - Product / All Devs - You

    need to know who is working - Figure out your velocity - eg. point per dev day / median points per sprint - Commitment
  9. ! RUNNING A SPRINT - Goal - Stand-ups (they can

    be remote) - Blockers - Async and open communication is better - Write down things in the tickets you're working on - Don't bring things in, support others to finish tasks first
  10. ! WHAT HAPPENS WHEN THINGS GO WRONG? - dropping stories

    - re-estimating - canceling sprints half way and starting anew - P1s
  11. ! SHOWCASE (DEPO DEMO) - be proud of what you've

    achieved - work does not need to be client facing to be demo-able - rotate who's demo-ing
  12. ! RETRO - Go over last retros actions - Went

    well / Didn't go well - Ideas - Cake (congrats, applause) - Create and assign actions
  13. ! ROLLING THIS UP - Points > Velocity > Projected

    throughput in a (sprint length) period - Epic estimation (t-shirt) vs Epic actual points > Projected epic length - epic x was medium and when delivered was y points
  14. โ˜‘ THINGS YOU NEED TO DO - Sprint length -

    Story point scale / context (what's 0 / too complicated to point look like?) - How are you going to write your stories - How will you measure velocity? - Definition of done (merged? in production? passed experiment?)