Skip to main content
New
Stack Overflow Jobs powered by Indeed: A job site that puts thousands of tech jobs at your fingertips (U.S. only). Search jobs
24 votes
Accepted

How to deal with sprint planning running far too long?

You're right - 5 hours in Sprint Planning for a 1 week Sprint does seem like a long time. The Scrum Guide time-boxes Sprint Planning to 8 hours for 1 month Sprints and says that "for shorter Sprints, ...
Thomas Owens's user avatar
  • 82.8k
18 votes
Accepted

How to distribute development and bug fixes tasks

Your question sounds a bit like your "team" consists of this sole engineer? If yes, the main question is why they didn't run away yet. Such a situation isn't sustainable. Apart from the &...
Hans-Martin Mosner's user avatar
14 votes

How to distribute development and bug fixes tasks

First of all I agree with Hans-Martin Mosner's answer. However, in your current situation there also might be an issue with the bug fixing process. Either all bugs are emergencies that directly affect ...
Frank Hopkins's user avatar
13 votes

Are bargaining and beat down attempts on Scrum estimations legitimate parts of the process?

The situation you describe is toxic. This sort of bargaining ignores reality and the expertise of the team, it willfully conceals information from the team and organization at large, and it inhibits ...
Jonah's user avatar
  • 756
13 votes

How to distribute development and bug fixes tasks

It sounds like you are trapped in a loop of rushing the dev work, which then has bugs, which then causes you to rush the dev work. Break the cycle by doing fewer, but better tested releases. Stop ...
Ewan's user avatar
  • 76.3k
11 votes

Need help for sprint planning when tasks are not done in previous sprint

My first suggestion would be to fix your terminology to improve communication, both internally and externally. You are using terms like "Scrum Master", "Sprint", and "Sprint Review". These are terms ...
Thomas Owens's user avatar
  • 82.8k
10 votes

Should agile sprints/iterations be back-to-back?

whether the notion that sprints/iterations in agile development should always be back-to-back Yes. A Sprint is timeboxed, and the next sprint starts right after the previous one's timebox ends. This ...
jonathangersam's user avatar
9 votes
Accepted

Should there be a gap between sprints?

There is no gap between sprints. After the Review and Retro, the next thing is the next sprint's planning. Now, what you describe doesn't sound like a gap as much as it is a 12-day sprint instead of a ...
Daniel's user avatar
  • 2,041
9 votes
Accepted

What time of day should we end a sprint before a sprint review meeting?

Scrum says nothing about this. You should hold the review as soon as practical after the sprint ends. That means after all the work is done, all tests have passed, and the team has had a chance to ...
Bryan Oakley's user avatar
  • 25.3k
9 votes

dev and qa in same sprint

How can both be completed by the end of the sprint and neither is remaining but still not have a dev sit idle near the end of the sprint while they wait for QA effort or QA starts some QA work after ...
Bryan Oakley's user avatar
  • 25.3k
9 votes

How to avoid code review bottlenecks when some of the team pair program

The teams should be empowered to review their own code, after all there's no one better qualified. GIT Pull Requests implement one of the easiest and most robust models for this: Code cannot be ...
Liath's user avatar
  • 3,426
8 votes

Do "almost finished" tasks or stories justify planning with overload in the next sprint?

Do not try to make your velocity look better than it is. The way forward is to acknowledge that the task was not completed you overestimated what you could do in the sprint and failed. But that is ...
Bent's user avatar
  • 2,576
8 votes

Are bargaining and beat down attempts on Scrum estimations legitimate parts of the process?

In my opinion, one of the greatest achievements of SCRUM is the development of story points, with the expressed explicit intent of avoiding the bargaining issues mentioned here. The whole point of ...
Cort Ammon's user avatar
  • 11.2k
8 votes

Does the Scrum Guide Specify How Often to Release QA/Test Builds?

No it does not. Only thing it states that at end of sprint, Potentially Releasable Product Increment is produced. And general consensus of "Potentially Releasable" is that it does include it being ...
Euphoric's user avatar
  • 37.4k
8 votes

How to distribute development and bug fixes tasks

You have apparently not considered option D: stop doing Scrum. It sounds like your work is much more suited to something like Kanban rather than Scrum, so you should do that.
Philip Kendall's user avatar
7 votes
Accepted

How do I explain to my team "there is no problem if the requirements need to change after a sprint?"

There may be many stakeholders in the real world, but as far as the developers are concerned, there is only one: The product manager who was selected by the companies involved to have the ...
gnasher729's user avatar
  • 45.7k
7 votes
Accepted

Product Backlog vs. huge features

My personal perspective from having worked in agile for a few years, is that you really shouldn't fear a large backlog (to a point). If you are writing self-contained user stories, each of which is ...
Ben's user avatar
  • 349
6 votes
Accepted

Do "almost finished" tasks or stories justify planning with overload in the next sprint?

When a story isn't done at the end of the sprint, then the points of the story don't count towards the velocity of that sprint and the story goes back onto the backlog. If during the planning of the ...
Bart van Ingen Schenau's user avatar
6 votes
Accepted

How to get started with Scrum when the team is bad at generating ideas?

What I think you lack here is a product owner. Somebody who knows about the product you guys are working on and who can make sure that the user stories that end up in your backlog meet DoR (Definition ...
Vladimir Stokic's user avatar
6 votes

How to deal with sprint planning running far too long?

I hear you. That's too long to spend! Hopefully, your team is discussing this in your retrospectives. We tried several experiments with mixed results: Everyone does a high-level design on a single ...
Jason Zinschlag's user avatar
5 votes
Accepted

How the time of Agile Sprint is calculated?

I believe you're working backwards here, from an Agile/Sprint point of view. Generally, you decide on the length of the sprint first, as that is the "time box" the work takes place in. Sprints ...
Matthew Flynn's user avatar
5 votes

How to get started with Scrum when the team is bad at generating ideas?

There's a couple of potential solutions: Is it really the case that the team should be generating ideas? Engineering teams are generally responsible for implementing ideas that come from product ...
Dan1701's user avatar
  • 3,108
5 votes

Is the Iteration Planning part of the Iteration itself?

The Sprint is the container for all the work that is done in the sprint, this includes Planning, Sprint Review and Retrospective and all the work in between. Nothing prevents you from adjusting the ...
jessehouwing's user avatar
  • 1,044
5 votes

Is the Iteration Planning part of the Iteration itself?

In Scrum, as defined by the Scrum Guide, the Sprint includes "Sprint Planning, Daily Scrums, the development work, the Sprint Review, and the Sprint Retrospective". So the answer to your question from ...
Thomas Owens's user avatar
  • 82.8k
5 votes
Accepted

Sprint planning: who decides which items of the Product backlog to be included into the Sprint backlog?

The product owner knows what is important, and prioritizes the backlog. The team knows what is possible, and can estimate backlog items. Together, they can create a sprint goal that is both relevant ...
amon's user avatar
  • 134k
5 votes
Accepted

Agile scrum - estimate another team's sprint

This sounds like management outsourced their micro-management. Even in a fully cross-functional team sprint planning is deeply personal. Not only because my skill set is personal but because my ...
candied_orange's user avatar
5 votes

In scrum, if tasks are estimated in hours, how to avoid assigning the task in sprint planning?

The statements that you claim should be true in Scrum aren't necessarily true in Scrum, according to the Scrum Guide. It is not true, according to Scrum, that you should be estimating user stories in ...
Thomas Owens's user avatar
  • 82.8k
5 votes

As a developer, how should I work differently in kanban vs scrum?

The two approaches are very compatible. In fact, it is completely possible to use both. That said, as you adopt Scrum, there will probably be two significant differences. 1) Scrum is very team ...
Daniel's user avatar
  • 2,041
5 votes

Should story points be re-estimated when rolling un-finished stories into next sprint?

I think if there is any lesson to take away from scrum and agile as a whole its "Don't waste time worrying about estimates not being right" If you didn't finish the 5pt task in the last ...
Ewan's user avatar
  • 76.3k

Only top scored, non community-wiki answers of a minimum length are eligible