I suggest you ...

Include Backlog Refinement in the Scrum Events section

Backlog Refinement adheres to the definition of event (formal opportunity to inspect and adapt something.) Promoting it to event would make the guide tidier (presenting everything as a role/artifact/event,) facilitate the understanding and make it more difficult to forget it.
But it would be needed to slightly change the description of event since it states that everything is time-boxed; refinement would be an exception to this rule.

170 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Jose Luis Soria shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    22 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Jose Luis Soria commented  ·   ·  Flag as inappropriate

        I know that it's not an event. That's why I'm proposing to promote it to an event.
        Planning is an activity. It takes place at the Sprint Planning meeting event.
        Collaborating about what was done during the Sprint is an activity. It takes place at the Sprint Review meeting event.
        Inspecting and adapting are activities. They are done at the Sprint Retrospective event.
        Synchronizing is an activity that takes place in the Daily Scrum.
        Refining the backlog is an activity, let's create an event for it. I’m not even saying that it must be a time box or that it has to take place always at the same time. I mean that we should list it along the other events so it gets the same attention.

      2 Next →

      Feedback and Knowledge Base