I am bit confused with a question, The customer can see the sprint goal, but should he be also able to see sprint backlog? or it is not allowed for the customer to see sprint backlog?
Scrum: Sprint Backlog: Who can see the Sprint Backlog and who are restricted to see the Sprint Backlog?
132 Views Asked by nipanch At
4
There are 4 best solutions below
0
On
First of all of we talk purely Scrum book terminology, I don't think there is such party as Customer. Scrum defines three roles: Development team, Product Owner and Scrum Master. You can argue Product Owner represents customers but this is not really outlined in Scrum Bible.
Sprint backlog as an artifact is generally managed by the Dev team as this is essentially what's been committed to a sprint. So the only restriction I can think of in regards of Sprint backlog will be its modification. Changing it during sprint is only allowed if Dev team makes an agreement with the PO.
0
On
There is a great deal of value in making the sprint backlog visible to everyone.
Reasons for this include:
- Helps to set expectations on what will be done in the sprint
- Creates trust between those in the team and those outside of it
- Allows for feedback from stakeholders to the Product Owner
- It can protect the team from having additional work dropped on them - it shows that they are busy and what they are working on
0
On
Customer can see the sprint goal, and Release goals. To me thats enough for a customer view. Sprint back log must be visible to the team, scrum master, product owner and other engineering stakeholders only.
Anyways its agile, as long as you give access to your backlog anyone can see the backlogs.
One of the Scrum Values is Openness. Scrum does not specify what a customer can and cannot see. However, you can apply the value of Openness as a litmus taste to a decision about what to share and what not to share.