My experience suggests that it’s best to create a regular cadence of sessions, a couple each week, to bring the team and their stakeholders together so that they can examine outstanding work and gain broader understanding of upcoming items. Some Kanban teams visualize this “upstream” work to the left of their implementation board. Kanban teams will apply explicit policies: if items are “ready” they can be brought into the system when capacity is available if not, further refinement is necessary. Scrum recommends spending no more than 10% of a team’s time on refinement but leaves the specific approach up to the team. The objective is to get work “ready” for the team, so that they can pick it up and make progress against it. What is backlog refinement?īacklog refinement brings a team together to review and revise upcoming work items. The spike does not move the climber closer to the top, but it does enable her to make further progress. Agile lore suggests the term comes from the pitons used in mountain climbing pitons are small spikes that, once driven into a rock face, provide a secure anchor for carabiners. A time limit is put on it, and, when the time limit is reached or the uncertainty is resolved (whichever comes first), those involved share their findings. In the spirit of transparency, this work is called a spike. They can gain the necessary knowledge through research, by building a prototype, collaborative brainstorming, or any other means. When a team is unsure how to move forward with their work a useful practice is to schedule a timebox in which a couple of team members (or the whole team if the uncertainty is preventing them from working on the customer’s highest priority) address the unknowns.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |