At $Company, we use sprints for our shortest planning-and-execute cycle.
In most departments, our sprints are one week, but Product/Engineering use two-week sprints to minimize meeting overhead.
At the beginning of every sprint, the team commits to small improvements they plan to get done before the end of the sprint.
The team or individual contributor:
- Takes input from their client on desired priorities
- Plans for enough priorities to fill the time available, but not more. Typically this means a set number of tasks per sprint.
- The commitment is to work on and try to make meaningful progress on, each item. The commitment is not necessarily to finish it
- At the end of the sprint cycle, the team or individual contributor presents their progress to the client and takes input for the next cycle.
This page is regularly updated. Please check the Midstage Manual for new content for this page.