islco / methods

ISL's methods for creating interactive experiences
1 stars 2 forks source link

Backlog Refinement #51

Open scottpdo opened 5 years ago

scottpdo commented 5 years ago

Purpose

In a backlog refinement meeting, project tasks in the backlog are assessed for quality, relevance, importance, and are reprioritized, edited, or removed in order to better prepare for upcoming sprints.

Outcome

A prioritized backlog with complete and ready to pull tickets at the top.

@scottpdo waxes poetic

Like crude oil buried under the earth, we assume that on every project there exists an infinite supply of tasks — a ‘backlog’ — to be accomplished.

We assume that tasks in the backlog will eventually bubble to the surface and be assigned in a sprint, but like shrewd speculators, we should also carefully consider the tasks most worth ‘mining.’

Team Needed

The prioritization of backlog items is owned by the product owner, who is often the client. This process gives the client a chance to voice their most critical needs and also a lens into the level of effort required to meet those needs. Together the team defines the scope of tickets. Backlog refinement can be used as a tool for making tradeoffs as it relates to client priorities and team capacity/availability.

Duration: 1-2 hours

Team needed

Full project team + client

Best in class examples