In this chapter we talk about the artifacts main challenges.

During the sprint, the Developers recognize that an item is more complex than planned. So, with the approval of the Product Owner, the Developers want to change it with another easier one.

In this case, the Developer finds that the work selected for the sprint was different than the initial plan, so the Developer, according to the Product Owner can select a different item from the product backlog to work on. The important thing is that they need to consider what’s the sprint goal in selecting the new work because the new item need to be useful to the sprint goal without decreasing its quality.

The team finds a process that isn’t in line with the company policy and standards.

The definition of done of the PBI needs to include at least the organizational policy and standards. So the process need to be in line with the DOD and so with the organizational policy and standard.

The Product Owner wants to keep offline the Product Backlog. If someone wants to access it, they need to talk with him.

This is wrong because the backlog needs to be visible to all the team and the stakeholders to foster transparency. In addition the developers can have the need to access to the backlog during the sprint repetitively to add more details about an item so they have the necessity to access it directly.

During a Sprint Review, two developers discuss an item arguing if it meets the definition of done.

The definition of done is created and owned by the Developers and helps to create transparency on when a Product Backlog Item becomes an increment.
In this scenario, the team needs to look at the definition of done for say if the PBI is considered Done. If the definition of done isn’t clear, the developers need to clarify it with the scope to avoid future doubt.

The product owner asks the developers why one item is such complex with a similar one with a smaller estimation.

The Developers and the Product Owner should collaborate during the sprint for the product backlog refinement. In this activity, the Product Backlog Item is broken down into more detailed items. Only with a detailed PBI it’s possible to compare the complexity with another item. But it’s important to know that only the Developers who are doing the work are responsible for the sizing.

What improve the transparency over the artifact?

The Daily Scrum is an event that helps to plan the work for the next day highlighting impediment. It helps to give transparency over the Sprint Backlog.

The sprint review helps to analyze the work done and the work that needs to be done. It helps to give transparency over the Product Backlog.

The definition of done helps to give transparency over the Product Backlog Item because only when the DoD is met, the increment is born.

The product owner wants to postpone the sprint planning because he is still adjourning the product backlog.

The sprint planning starts at the start of each sprint with no waiting. In these events, the product owner and the developers can collaborate to clarify the product backlog item for making the sprint backlog.
The product backlog is never ended, so there is no reason to wait for it.

Share on: