Each project is different, and we acknowledge no one method works across all projects. For example, the development processes and methodologies applicable for a product in its 0 to 1 stage would be very different from those for a product in the growth phase.

<aside> 💡 For Jam (an app for a decentralized social network), we loosely embraced a 3-week sprint approach during its early stages.

</aside>

This is what a recent 3-week development sprint for Jam looked like:

2 weeks of development + 1 week of a cooldown that includes time for spillover, retrospectives, and planning for the next sprint. Sprint starts with a kick-off on a Wednesday

Managing the Sprint

We use a Kanban board in Notion to manage the sprint and track the tasks. This is how the board is organized in various columns:

• backlog
• product design active
• in-progress research
• on deck (ready to be picked up for development)
• current sprint
• in-progress development
• in-review change requested
• in-review bug fixes
• done locally / review done
• on staging
• QA verified
• live on production

Planning Phase (taken up during the cooldown phase of the previous sprint)

• The engineering lead syncs with the PX team to understand high-level requirements and gets an idea of the scope and complexity of the tasks.
  • Discussions on mocks, and suggestions if any for design updates/changes.
  • Depending on time availabilities, they might do a backlog scrub together.