Sprint plan issues

[bedeho]

Background

We decided that, in order to assist in prioritization work, all design sprints will have an initial sprint issue describing the scope of sprint, and issue should be shared with product manager as early as possible before work begins. Obviously scope make change as design work commences, in which case it would be good practice to write a follow up entry in the same issue. Apply label sprint-plan. We should consider doing something similar for sprints overall, or for pure tech sprints, as well in the future.

How-to

In order to write an effective plan, its important to describe the sprint in terms of problems one attempts to solve, from a user perspective, rather than specific solutions one has in mind for what to do.