DEV Community

Jim Medlock for Chingu

Posted on • Originally published at Medium on

How does your Team start a Sprint?

Sprint 4 — Monday

Photo by airfocus on Unsplash

Achieving your Sprint goals directly depends on what you do at the start of the Sprint. As you can probably guess your sprint should start by:

  1. Review tasks from the previous Sprint and update your Product Backlog so you know which tasks were completed and which need to carryover to this Sprint.
  2. Reflect on how the team worked & on your teamwork to identify what worked, what didn’t work, and what you’ll do to improve.
  3. Decide which tasks from the Product Backlog will be worked on in this Sprint, including those that weren’t completed in the previous Sprint
  4. Commit to posting status daily, even if there’s no progress, and asking for help when it’s needed.

You don’t know what you don’t know until you know it!

Sprint plans are great, but you will need to be flexible and adapt them throughout the Sprint. Your plan and your team shouldn’t be rigid or resist change, you should embrace it because at the time you create any plan you don’t know what you don’t know!

This is the beauty of following an Agile methodology — it is based on having a plan for each Sprint, accepting that change will occur, & adapting to it.

Before you Go!

Chingu helps you to get out of “Tutorial Purgatory” by transforming what you’ve learned into experience. The experience to boost your Developer career and help you get jobs.

You can learn more about Chingu & how to join us at

Discussion (0)