14
votes
Sprint is 2 week and 40-stories
If you are following Scrum as defined in the Scrum Guide, the Product Owner cannot simply add stories to the Sprint Backlog. The Sprint Backlog, which is created as Sprint Planning as a negotiation ...
- 19.9k
11
votes
Demo in Sprint Review
TL;DR
There is a lot going on here. The short answer is that the Sprint Review does not have to be a demo but Scrum does advocate that the team should produce a potentially shippable product ...
- 4,095
8
votes
What can lead to disappointed and angry stakeholders?
Choosing two answers, I would select A and D.
B can be eliminated since project plans and formal change request procedures aren't typically a part of agile delivery approaches. Agile Software ...
- 19.9k
7
votes
Accepted
Does every Scrum story need to be completed at the end of the sprint?
TL;DR
You say that some teams believe the following:
[E]very story must be complete by the end of the sprint.
It may be true that some teams believe this common misconception, but it's factually ...
- 50.7k
6
votes
Demo in Sprint Review
Demonstrations are Required; Visual Demos are a Best Practice
Scrum requires that work be demonstrated during the Sprint Review. The Scrum Guide says:
The Development Team demonstrates the work ...
- 50.7k
5
votes
Accepted
Is it necessary for the whole team to participate in the Sprint Review in Scrum?
First off, +1 for checking the Scrum Guide!
The book answer would be that it says the attendees include The Scrum Team and with no extra qualifiers, it can be assumed that it means the whole scrum ...
- 16.9k
5
votes
Sprint demo feedback
tl;dr; There is no "right" answer. Whatever works for your team and client.
Probably Not a Bug
Sprint feedback is rarely a bug. While there is no strict definition, a bug, or defect, is a term ...
- 16.9k
4
votes
Demo in Sprint Review
Forget about Demo.
Before downvotes start to fly, bear with me.
As Venture mentioned (+1!), you have foundation problems that should be addressed before you get concerned about a Demo. I'll bet you ...
- 8,673
4
votes
Accepted
When to talk the problems we encountered during sprint, Sprint review or Sprint Retrospective?
Discussing problems during Daily Scrum is perfectly fine. When a team member mentions some impediment you can stay right after the Daily Scrum and discuss the issues. From Scrum Guide:
Here is an ...
- 1,046
4
votes
Should we start a sprint review with no business value stories in Scrum?
Yes! My recommendation would actually be to have a really small goal that is easy to see, but doesn't add much work (or maybe value). It's more of a talking piece than anything. That first review is a ...
- 16.9k
4
votes
Sprint Review Event
The November 2020 version of the Scrum Guide makes it very clear when the Sprint Review occurs:
The Sprint Review is the second to last event of the Sprint
This places the Sprint Review before the ...
- 19.9k
3
votes
When to talk the problems we encountered during sprint, Sprint review or Sprint Retrospective?
I think it's generally true that the emphasis of the Sprint Review is on the product and the Sprint Retrospective is on the process, but that doesn't mean the Sprint Review is exclusively about the ...
- 19.9k
3
votes
Accepted
Sprint Review: How to prevent every single type of story from being "reviewed"
As you suspect the standard purpose of the scrum review is to 'inspect the Increment and adapt the Product Backlog if needed'. In practice this means showing what work is now done (so these items can ...
- 56
3
votes
Sprint Review: How to prevent every single type of story from being "reviewed"
You need to review the product increment. From what I understand from your question, it seems to me that you are mostly reviewing the work that you did to build the actual increment.
If you want to ...
- 15.5k
3
votes
Accepted
What to do with incomplete User Stories
TL;DR
You may have an X/Y problem. While failure to achieve the Sprint Goal is a problem if it happens often enough, the actual issue you're facing seems to be a lack of trust in the Scrum Team. This ...
- 50.7k
3
votes
Should we start a sprint review with no business value stories in Scrum?
architectural user stories with no business value
I encourage teams to create a very simple 'hello world' style first user story that offers limited but non-zero business value. Then do all the ...
- 19.6k
2
votes
Accepted
Should we start a sprint review with no business value stories in Scrum?
TL;DR
Scrum requires that the event be held at the end of each iteration, even at the beginning of a project. While you might consider shortening it, or shifting the focus slightly towards process ...
- 50.7k
2
votes
When to talk the problems we encountered during sprint, Sprint review or Sprint Retrospective?
Problems or things which went wrong, should be raised in the retrospective.
The retrospective is for the whole team internally. The results can be shared with others. The retro is the event with the ...
- 125
2
votes
What to do with incomplete User Stories
Seconding the recommendation not to do this at the sprint review.
I think you have a bit of coaching to do with all involved parties as to the purpose of the sprint review.
After that, I would ask ...
- 3,659
2
votes
When to talk the problems we encountered during sprint, Sprint review or Sprint Retrospective?
There isn't a straightforward answer to this type of question because a lot depends on:
the nature of the problem. Is this a technical problem? Is it a product related problem? A problem regarding ...
- 15.5k
2
votes
What is bad to have sprint review before finishing sprint?
There's no requirement that the Scrum events that bookend a Sprint - the Sprint Review, Sprint Retrospective, and the next Sprint's Sprint Planning - all happen consecutively. Especially for the ...
- 19.9k
2
votes
Sprint Review Event
TL;DR
The Sprint Review is always at the end of a Sprint. It cannot fulfill its purpose properly until the Sprint has produced an outcome for inspection by the Scrum Team and key stakeholders. In ...
- 50.7k
1
vote
Sprint Review Event
You could hold the sprit review whenever you are able to demonstrate a useful increment of work. That's typically on the last day of the sprint and it really should be done before the next sprint ...
- 6,345
1
vote
Accepted
Can our team perform Sprint Reviews using JIRA?
TL;DR
At heart, JIRA is just a ticketing system. It is not a substitute for interpersonal interactions or real-time collaboration, and absolutely not an effective substitute for the Sprint Review ...
- 50.7k
1
vote
When to talk the problems we encountered during sprint, Sprint review or Sprint Retrospective?
When to talk the problems we encountered during sprint, Sprint review
or Sprint Retrospective?
When it's more effective.
Scrum (and agile) are not very prescriptive. That's one of the biggest ...
- 8,673
1
vote
When to talk the problems we encountered during sprint, Sprint review or Sprint Retrospective?
In the Sprint Review, you show the customers (and everyone else that is interested) the product increment you have just completed. If during the sprint you encountered problems that caused you to ...
- 2,805
1
vote
User story sign off in daily standup
A few things to consider:
First, let's start with the best: you have super-engaged stakeholders. That is so awesome! And nothing in Scrum says you have to wait until the end of the sprint to show ...
- 16.9k
1
vote
User story sign off in daily standup
I would give the following comments to your practice.
Daily Scrum:
The daily Scrum is a meeting for the team members to discuss if it is possible to reach the sprint goal. In my opinion, there is no ...
- 111
1
vote
Sprint is 2 week and 40-stories
is the 20 old stories represent a release? if yes there is a real problem at the business vision, where that the 20+ stories will completely lead to another product and how these extra stories were ...
- 187
Only top scored, non community-wiki answers of a minimum length are eligible