9 Matching Annotations
  1. Last 7 days
  2. Oct 2021
  3. Apr 2021
    1. Refinement usually consumes no more than 10% of the capacity of the team. 

      It used to give me a good reason to point to the Scrum Guide when the team was annoyed by the number of refinement hours during a sprint.

      With more experience, it becomes clear that the number of refinement hours spent should not depend on the Scrum Guide but on the readiness of work. A better measure, and this differs from team to team, is how many stories shall be ready at all times? One to three sprints worth of ready work? At least enough work should be ready before Sprint Planning, so that the actual sprint delivers done work (and not more refinement work, only.)

      Refinement hours spent also depend on how predictable the work is on the Product Owner’s roadmap and if there is a need to do first iterations of refinement on future releases, months away to have a very high level estimate of effort.

      Opinions?

  4. Jan 2021
  5. Oct 2020
  6. May 2020
    1. put it in our %Backlog (meaning GitLab, Inc. currently doesn't prioritize it over other items that are scheduled
    2. This issue is going backwards in the process, not forwards. Surely, Gitlab should be focusing on things that have already been allocated milestones, especially ones that have had milestones pushed continuously for 3 years. You can argue that it shouldn't have had a milestone added in the first place, but maybe Gitlab should focus on clearing the "backlog" of issues that have already been issued milestones, and backlog new issues until some of the older issues have been solved.
  7. Sep 2015
  8. Mar 2015
    1. an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Development Team on why it is building the Increment. It is created during the Sprint Planning meeting. The Sprint Goal gives the Development Team some flexibility regarding the functionality implemented within the Sprint. The selected Product Backlog items deliver one coherent function, which can be the Sprint Goal. The Sprint Goal can be any other coherence that causes the Development Team to work together rather than on separate initiatives.

      an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Development Team on why it is building the Increment. It is created during the Sprint Planning meeting. The Sprint Goal gives the Development Team some flexibility regarding the functionality implemented within the Sprint. The selected Product Backlog items deliver one coherent function, which can be the Sprint Goal. The Sprint Goal can be any other coherence that causes the Development Team to work together rather than on separate initiatives.