Few queries on review meeting,daily scrum and PB

Hi Shalini,

Thanks for the interesting questions.

• Review of the timeline, budget, potential capabilities, and marketplace for the next anticipated release of the product. Based on this statement what is to be reviewed and do the development team understands the budget, marketplace etc.,

  • This is about the Sprint Review. This phrase means that attendees collaborate on the next things that could be done to optimize value of the next anticipated release of the product. It can include all related aspects: product features, possible timeline, marketplace, etc.

• Daily scrum: highlight and promote quick decision-making--> Decision to be taken on what?

  • Any team member can ask for advice or report about an impediment. All the team will cooperate on a quick decision. If a question is tough, it can be discussed after the Daily Scrum.

• The Scrum Master’s job is to work with the Scrum Team and the organization to increase the transparency of the artifacts. This work usually involves learning, convincing, and change--> Can anyone explain the terms learning,convincing and change with examples.

  • It is easy. The Scrum Master should help the team and organization use Scrum theory, practices, and rules. Scrum relies on artifact transparency. For example, Product Backlog items should be clear to every team member. If one of the members, for example, does not share this idea, the Scrum Master should convince him to learn Scrum a bit more. So, the team member should change, accept the idea of transparency and start trying to make Product Backlog items more clear.

• Product backlog: Multiple Scrum Teams often work together on the same product. One Product Backlog is used to describe the upcoming work on the product. A Product Backlog attribute that groups items may then be employed.--> What is Product backlog attribute. Can you explain with example?

  • An attribute is just a tag, keyword to group related items with each other. It will help to work with a large Product Backlog. Example attributes could be: “UI”, “Parity with the Desktop version”, “REST API”, etc.

• If any organization have standard guidelines to be defined scrum guide says minimum we need to include them and also. Guidelines that are appropriate for the product also needs to be added. Is it correct?

  • The Scrum Guide says that if an organization already has some requirements to the increment that can be applied, all Scrum Teams must follow them as a minimum. However, it is expected that the Definition of Done will evolve to include more stringent criteria for higher quality.

Regards,

--Mikhail Lapshin