Pench BattaEnterprise Lean Agile DevOps Coach /SAFe Program Consultant (SPC6)| Capgemini, Inc.Bentonville, Ar, United States
Daily scrum, sprint planning, sprint review and sprint retrospective are official scrum events. Why not backlog refinement considered as official scrum event? Saving Changes...
Backlog refinement is expected to be an ongoing activity as opposed to a point-in-time ceremony.
Kiron Saving Changes...
Pench BattaEnterprise Lean Agile DevOps Coach /SAFe Program Consultant (SPC6)| Capgemini, Inc.Bentonville, Ar, United States
Thank you, Kiron! Saving Changes...
Wade HarshmanScrum Master| GDITIndianapolis, In, United States
One of Scrum's founder's (I think it was Ken Schwaber, but it might have been Jeff Sutherland) wrote that they considered adding backlog refinement to the scrum guide. They decided it would be too prescriptive. They both take pride in the fact that Scrum is a very open framework that can be adapted to organizational needs. Many Scrum trainers and ScrumMasters have since added requirements where the Scrum Guide does not.
To clarify, backlog refinement does need to happen, but it doesn't have to be an official ceremony.
I apologize that I cannot find the article I'm referencing. My Google skills are weak, this morning. Perhaps someone else can find it and share it.
Pench BattaEnterprise Lean Agile DevOps Coach /SAFe Program Consultant (SPC6)| Capgemini, Inc.Bentonville, Ar, United States
Oct 02, 2018 9:16 AM
Replying to Wade Harshman
...
One of Scrum's founder's (I think it was Ken Schwaber, but it might have been Jeff Sutherland) wrote that they considered adding backlog refinement to the scrum guide. They decided it would be too prescriptive. They both take pride in the fact that Scrum is a very open framework that can be adapted to organizational needs. Many Scrum trainers and ScrumMasters have since added requirements where the Scrum Guide does not.
To clarify, backlog refinement does need to happen, but it doesn't have to be an official ceremony.
I apologize that I cannot find the article I'm referencing. My Google skills are weak, this morning. Perhaps someone else can find it and share it.
Thank you, Wade! Saving Changes...
Pench BattaEnterprise Lean Agile DevOps Coach /SAFe Program Consultant (SPC6)| Capgemini, Inc.Bentonville, Ar, United States
But page 85 of Lesson 2 of PMI training material for PMP preparation course mentions it as agile ceremony. Those who work in agile environment have a difference of opinion here. Should we inform PMI to make changes to the material? If someone from PMI is there, then they can enlighten us.
...
1 reply by Kiron Bondale
Jul 20, 2024 10:33 AM
Kiron Bondale
...
Amitabh -
It is not a Scrum ceremony. However, other frameworks might consider it a true ceremony. Therefore, it might be an agile ceremony but not a Scrum one.
There is definitely a LOT more under the agile sun than just Scrum...
But page 85 of Lesson 2 of PMI training material for PMP preparation course mentions it as agile ceremony. Those who work in agile environment have a difference of opinion here. Should we inform PMI to make changes to the material? If someone from PMI is there, then they can enlighten us.
Amitabh -
It is not a Scrum ceremony. However, other frameworks might consider it a true ceremony. Therefore, it might be an agile ceremony but not a Scrum one.
There is definitely a LOT more under the agile sun than just Scrum...
Kiron Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
It was implicit because Grooming (used before) or Refinement (using today) really means: if you are a developer, and you take an user story, the only way you have the chance to understand what to develop is to have the acceptance criteria and other things inside the user story. And that usually happens during refinement. If you go to the guide and read about The Sprint inside Scrum Events you will find: "During the Sprint: No changes are made that would endanger the Sprint Goal; Quality does not decrease; The Product Backlog is refined as needed; and, Scope may be clarified and renegotiated with the Product Owner as more is learned." And when the guide is "talking about" artifacts, you will find the following in the Product Backlog definition: " Product Backlog refinement is the act of breaking down and further defining Product Backlog items into smaller more precise items. This is an ongoing activity to add details, such as a description, order, and size. Attributes often vary with the domain of work." If you ask me, what it works for me, including now I am using SAFe from time ago, is to maintain a time slot in the iteration or sprint related to backlog refinement not matter I push for incorporating the way of working about refinement must be done in a constant way, because this way of working demonstrate team maturity. Saying that, it will highly depend on the organizational architecture. For example, is a Product Owner assigned to the team and available when it is needed for refinement? The last is one of the things because I prefer to reserve a time slot inside the iteration or sprint. And something obvious: have user stories refined at planning event is critical success factor for the iteration of sprint. Saving Changes...
