Summary

We discovered that the Team Backlog is a collection of work that the team can undertake, which includes User Stories and Enablers. The PO is primarily responsible for it, but any team member can contribute to it. We learned that User Stories are small pieces of desired functionality that our Agile Teams implement within a few days. Acceptance Criteria are the conditions the story must meet to be considered complete.

We also took a look at the importance of estimating User Stories, which is done by the team, and outlined several techniques for splitting and prioritizing User Stories with reminders to always factor in relative sizing. Lastly, we took a look at Kanban Team Backlogs, and how to prepare for PI Planning.

Let’s now take a look in w at the events the teams execute.