PIVOT Enablement Leadership

Dev Team Sprint Changes

Planning Meeting Changes

Our goal should be that all work planned in our meetings is slated for next sprint (planning at least 1 sprint ahead).

This will allow us to pull work into a sprint based off of points and the team will have a clear idea of what we are delivering this sprint.

Change to Task structure to help us identify work for individual Business Objectives as well as better identify things we are waiting on from other teams. This has been much harder to identify in this new structure.

The task structure that best fits our needs is having a master Business Objective task which then has all of the proposed features laid out in subtasks. We can then add work breakdowns and tasks under each of the features and pull in relevant work based on this layout.

Properly setting up blockers as well really helps when we are waiting on another team for work, such as designs, table or stored procedure creations, etc. This is something we can manage as a team if we find that works best.

Project: Application

→ Section: Business Outcome

→ Milestone: Outcome Chunk (MVP, V1, etc.)

→ Subtask: Feature

→ Subtask: Work (add to Sprint Boards)

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.