[contact@crossthink.fr]

Hello,

Is good to see that people try to understand the scrum guide and not just read it 🙂

for this one the response is that the DOD can be changed by scrum team after Sprint Planning or Sprint Retrospective meeting. Team comes together and decides work-flow in order to improve the quality.

thanks

[contact@crossthink.fr]

Hi,

thanks for your question and sorry for the delay. The right response is the Whole team, Determining the Sprint Goal is one of the activities that shows how the relationship between the different roles is established.

thanks

[contact@crossthink.fr]

L’option de retry est pour pouvoir passer l’examen blanc plusieurs fois, si vous souhaitez revenir sur les questions et réévaluer vos connaissances.
Bien entendu lorsque nous récoltons de nouvelles questions nous les ajouterons dans un nouvel examen afin de vous en offrir d’avantage.

[contact@crossthink.fr]

Bonjour,

Merci pour la remonté d’information nous allons regarder pour fixer cela.

Cdl

[contact@crossthink.fr]

L’incrément produit est un des artefacts SCRUM les plus importants de la culture Agile. Durant chaque Sprint, l’équipe de développement réalise un incrément de produit.L’incrément en scrum représente l’ensemble des éléments « done » du sprint en cours en plus de ceux déjà finalisé dans les sprint précédents.

En scrum, nous définissons ainsi 3 artefacts classiques et 1 artefact de transparence :

product backlog
sprint backlog
increment
definition of done (artefact de transparence)

[contact@crossthink.fr]

Bonjour,

Il est tout à fait possible de refaire le quiz blanc, pouvez vous nous envoyez un mail avec l’erreur que vous avez lorsque vous tentez de le refaire?

Merci d’avance

[contact@crossthink.fr]

Bonjour,

Certains simplifient les grandes valeurs en les transformant en 20, 40, 100… puisqu’il s’agit d’être globalement bon plutôt que précisément erroné.
Il s’agit d’une suite de fibonacci simplifié, dans l’examen vous pouvez avoir des questions sur ce point.
Cdl

[contact@crossthink.fr]

Hello!

Actually not. In all Sprints the main goal of the team is to deliver value for the client, and technical debt are not necessarily that. Technical debt is a tricky point, as the team must always pay attention to it, if it is increasing, what is the impact, and so on.

The best choice is to alwys take care of technical debt, in every Sprint. For PO might be hard to know the importance and urgency of a technical debt, even more to understand its priority compared to a functional item (user story). That is why dev team should always help PO on that, raising high risk technical debts that need to be taken care of.

When a team does not pay attention to technical debts, it arrives in a Sprint committing more to non-functional stories (debts) than functional stories that bring value to the product.

[contact@crossthink.fr]

Hello!

1. Product Owner is the main responsible for writting Product Backlog Items (this duty can be delegated), so he must come to the Sprint Planning meeting with an idea of the acceptance criteria, as it will help dev team to understand and estimat stories. So yes, before an item is selected during the Sprint Planning to be taken into a Sprint by the dev team, it must have acceptance criteria. Not necessarily the PO must write all the criteria before the Sprint Planning as during the Planning, however, dev team can challange the criteria and them and PO can adjust or adapt.

2. The first difference is that definition of done (DoD) are common to all Product Backlog Items (PBIs) of a product, while acceptance criteria is specific to each item (and will be different).

The DoD exists to ensure that the dev team members agree on what means when an item (story) is “done”. It is there to ensure quality of work they’re attempting to produce. It serves as a checklist that is common to all items and is respected. When we see an item as “done”, team, Product Owner, Scrum Master know what this notion of “done” mean (all items in the definition of done have been respected). It is transparent, and no one will invetigate if team has actually respected it. If you see that product starts having lot of bugs, issues, technical debt increasing, it may indicate that definition of done is not being respected (best time to update the DoD is during the Sprint Retrospective).

Acceptance criteria are s set of statements that describes conditions an item must respect in order for it be accepted by the Product Owner. It is normally different from story to story, as it represents some behaviours or cases we want to achieve by building the functuinality described in the item.

[contact@crossthink.fr]

Because the first team should spend time on interaction with the other teams and resolve dependencies. In the very beginning the productivity will drop even more because members of the first team will have to do some knowledge transfer to the new teams

[contact@crossthink.fr]

Le Product Owner peut utiliser le burndown chart pour vérifier la progression de l’équipe de développement pendant le sprint. C’est vrai que le moyen principal et le plus efficace de visualiser la progression de l’équipe et du produit est de faire le Sprint Review, mais en pratique, le graphique de burndown peut être utilisé.

L’équipe de développement effectue déjà la daily scrum ( tous les jours ) tient le tableau de l’équipe toujours à jour, de sorte qu’ils sont déjà au courant de la progression du sprint. Le burndown chart serait plus utilisé par le Scrum Master ou le Product Owner, et c’est un moyen de mettre en pratique la «transparence» et de donner de la «visibilité», puisque ceux-ci sont mentionnés dans le guide Scrum (cependant le guide ne mentionne pas comment les mettre En pratique).

[contact@crossthink.fr]

En fait, dans le guide, il est mentionné que la rétrospective est un bon moment pour adapter le Definition of Done:

“During each Sprint Retrospective, the Scrum Team plans ways to increase
product quality by improving work processes or adapting the definition of “Done”, if appropriate
and not in conflict with product or organizational standards”

Il est temps d’inspecter votre façon de travailler, le cadre, la qualité, la transparence, etc. et le DoD assure certaines de ces choses (comme la qualité et la transparence)

[Auteur]

Messages