AGILE SCRUM MASTER
-
Hi
I´ve just finished the Scrum Master course, but somethings are still not clear to me:
1 –if the agile scrum project welcomes changes and we know that the customer constantly asks for changes, how can we put an end to a project . The customer is constantly adding things. What are the means we have to conclude the project
2. In the definition of done shoud always be considered the acceptance criteria for the tasks besides the criteria of the dev team(ex. Having done all tests , etc)
3. In the certified scrum master course, it is said that the maximum nr of team members is 10. In scrum guide it says, the dev team is 9 which means the maximum scrum team members can be 11(as it includes PO and SM). So is it 10 or 9 for the dev team?
4 – In scrum, when a question just refers to team, does that refers to the dev team or to the scrum team?–
5 – In the scrum course it is said, that No task should last more than 2 days. That’s what is said in the slide, but the presenter also applies the same criteria to story and task. Does this rule also applies to story or only tasks? If it is to both, how come is not written in the slide
6 When EXACTLY does the backlog refinement occur: immediately after the close of the sprint and before a start of a new sprint, or is done during the next sprint execution?
7 In scrum, For a sprint of two weeks the backlog refinement just occurs once or for a sprint of 3 weeks , can occur more than once? -
@Paula-Alexandra-Santos said in AGILE SCRUM MASTER:
Hi
I´ve just finished the Scrum Master course, but somethings are still not clear to me:
1 –if the agile scrum project welcomes changes and we know that the customer constantly asks for changes, how can we put an end to a project . The customer is constantly adding things. What are the means we have to conclude the project.Remember that all changes that are requested are not equal or valid changes. Nor are they without cost...therefore not every change is worth the cost to do so. For you to complete the project, you will have to have some stability, more stability towards later in the project.
- The project owner decides how and when to adapt changes.
- The cadence (sprints) are set as the longest duration of development time without changes. If you're finding changes are occurring more often, sprints time durations will need to be shortened.
- Do regular sprint reviews to allow for changes to be incorporated.
- If the changes are significant as to make the current sprint goal invalid. These changes allow you to cancel the current sprint goal to reset. You may have to review the canceled work and backlog the work if it's still necessary for the overall project.
- In the definition of done shoud always be considered the acceptance criteria for the tasks besides the criteria of the dev team(ex. Having done all tests , etc)
Not necessarily, it depends on the nature of the business. The goal of the Definition of Done is releasability. The requirements to that include for that sprint or story are:
- business or functional requirement - does this meet the presented requirement?
- quality assurance - is the quality level something that can be released?
- any non-functional - does this meet a certain requirement?
The Definition of Done is always at the Product Level itself, rather than at the sprint or story level. Does all the components lead to a releasable product should be how we define it.
- In the certified scrum master course, it is said that the maximum nr of team members is 10. In scrum guide it says, the dev team is 9 which means the maximum scrum team members can be 11(as it includes PO and SM). So is it 10 or 9 for the dev team?
Technically it's 9 + SM and PO, according the scrum framework. I think the 10 in the course may have been due to possible working experience.
4 – In scrum, when a question just refers to team, does that refers to the dev team or to the scrum team?
I think this probably up to the Scrum Master. If a question is posed, the SM should be the one to decide if the entire teams needs to be collaborating or just some or just one.
5 – In the scrum course it is said, that No task should last more than 2 days. That’s what is said in the slide, but the presenter also applies the same criteria to story and task. Does this rule also applies to story or only tasks? If it is to both, how come is not written in the slide
This may be descriptive rather than prescriptive from scrum framework. There is no real scrum rule about tasks duration. Scrum is based on past data and recommends that stories that take a longer be broken to into smaller stories of 8 point or less.
6 When EXACTLY does the backlog refinement occur: immediately after the close of the sprint and before a start of a new sprint, or is done during the next sprint execution?
The team itself decides how and when refinement is done. With this the guidelines are that product backlog refinement shouldn't take no more than 10% of dev team's capacity.
7 In scrum, For a sprint of two weeks the backlog refinement just occurs once or for a sprint of 3 weeks , can occur more than once?
The team itself decides how and when refinement is done. With this the guidelines are that product backlog refinement shouldn't take no more than 10% of dev team's capacity.
-
This topic has been moved to new category to help with visibility.