Disagreements are not always bad. It just shows that the individuals have a different opinion on a topic. Sometimes its healthy to have these disagreements to have a balance of thoughts in the team. Of course, it has to be in good spirit without getting toxic.
A product owner would like to get as much stuff done in a given sprint, based on the current velocity of the team. Ideally there wouldn’t be a discussion of ‘scope creep’ in an Agile development environment, because the development would happen based on the written stories. If the PO wants to enhance certain stories, thereby increasing the scope and the development effort, that is technically not allowed once the sprint has started. Now, if he/she wants to get some more things done in the same sprint, that again wouldn’t happen, as the Scrum Master would ask him/her to prioritise what needs to be done first.
Scope creep and the discussion around Quality used to happen in fixed bid Waterfall projects, where the scope of project would increase with an expectation to be done in the same time & money. Then one of the way to handle that situation would be to trade-off on Quality.
But in case of Agile methodology, say for e.g. SCRUM, you have a set velocity for the sprint, you have a ‘Definition of Done’ that needs to be followed. So, in this structure I do not think a discussion would happen on Scope creep vs. Quality. Because scope is open for PO to decide – what needs to be worked upon in the sprint, and quality is governed by the ‘Definition of Done’.
However, if that situation arises, then I would suggest using the following pointers to have a discussion:
- What is the team’s velocity for a sprint?
- What is the estimate of the ‘additional’ item being added to the scope of this sprint?
- What is the relative priority of this ‘additional’ item? Can we remove other less priority item from this sprint?
- What is the ‘Definition of done’ for all user stories being developed?
If you have any question on digital product management – be it related to career, expertise, skills, projects, or ‘How to’ stuff, drop me a line at: firstname.lastname@example.org.
I would be happy to help.