<aside> 💜

Senja is a product-led business shipping daily where continuous deployment is core to what we do.

</aside>

Engineering cycles

Cycles and sprints

• We run engineering in cycles
• These can also be considered business seasons
• Each cycle is made up of 5 sprints of one week
  • They look like this:

About sprints

• Each sprint lasts one week (M-F)
• The sprints and their rituals are owned and led by the Product Owner, Olly
• Each sprint should have an 80/20 focus
  • Typically this should address a revenue or engineering productivity opportunity and be tied to a business goal or metric
• Each sprint could include
  • Bugs [urgent and other]
  • UX fixes
  • Product changes
  • Backend tasks
• Typically we ship iteratively
• Each fifth sprint is a cool down
  • Cool down sprint

Future sprints

• We should always have two future sprints planned
• This is particularly important when the product owner is away

Sprint goal and energy

• The goal is to deliver everything listed in the sprint
  • This is end to end - spec, review, refine [may have been done earlier], prioritise, build, QA, approve, deploy, mark done
  • If it’s not live on production by end of sprint, it’s not done
    • See definition of done below
    • Typically customer-facing changes are announced to customers the following Monday
• The sprint energy is like a 5 day marathon
  • We start Monday and push through to get everything done
    • Lots of communication / unblocking
    • A real sense of we’re working together to ship good shit and celebrate
    • Sense of pride at the end of the week - worked hard, got sprint done