Gopinath Ramakrishnan

My feedback

  1. 165 votes
    Sign in
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      21 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
      Gopinath Ramakrishnan commented  · 

      I agree with this idea.
      Though planning is an ongoing activity & yet we have events like time-boxed Scrum Planning.
      Similarly backlog refinement is ongoing as an individual activity of the PO but still we need to have it as an event with the entire team participation.
      In fact I will go beyond this and suggest that this be scheduled as a time-boxed event (10 % of the Sprint duration) immediately after sprint retrospective and just before the next Sprint planning session of the next sprint. Scheduling backlog refinement meeting as an event will shift the team member focus from the current sprint to the forthcoming sprint. This will be a case of context switching which has been regarded as a waste from Lean perspective. But if a time-boxed backlog grooming is scheduled between two sprints the team can give full focus. So a typical 2-week sprint schedule will look like
      Monday -First Half : Sprint Planning and
      then after two weeks
      Friday - First Half: Sprint Review and Sprint Retrospective
      Friday - Second Half - Backlog refinement
      Monday - First Half - Sprint Planning (next sprint)

      One limitation with this approach is if the PO is not available on the Backlog Refinement Event is scheduled then it will get adversely impacted. But the same can be said of scheduled Sprint Planning session too.

      Gopinath Ramakrishnan supported this idea  · 

    Feedback and Knowledge Base