Should you ever re-estimate user stories?

My current project is having a ‘discussion’ which is split down the middle- “this story is more complex than we originally thought, we should re-estimate” vs “you should never re-estimate as you only ever estimate up and never down”.

Should the number of developers be considered when estimating a task?

I am pretty inexperienced with working in agile projects but I have tried it a few times and I always run into this problem when estimating a task.

Are Scrum and XP comparable things or are they used for different things

Are Scrum and XP comparable things or are they used for different things? what is the main features of each of them? how do they overlap?

Validating User Stories: How much change is too much?

While the core of requirements development and acceptance criteria would ideally take place during the planning meeting in order to create a better estimate, Scrum encourages continuous interaction with the product owner throughout the sprint to validate and refine user stories.

Is there a study showing which agile approach is best suited for particular kind of project? (in this case a re-platforming project, Java to .NET)

It is said that the Kanban methodology is suited for software maintenance and support areas, whereas Scrum is more suited for new product development. No process or methods are complete. Using the right one will help you succeed, but they will not guarantee success.

Is it appropriate to run a complex enterprise-system configuration and migration project in a similar way to a Scrum development project?

I’m just starting out on the implementation of a large enterprise-wide system, which has complex requirements and many stakeholders.

If you have several SCRUM teams working on one backlog, how do you divide story point estimation between those teams?

I’m asking because approach in my company looks as follows:

How do you keep track of a requirements document on an agile team?

I understand that User Stories dominate the agile world, but how are these artifacts stored, so that new developers who join the team can come up to speed with the requirements?

Evaluating a product owner [closed]

Closed 8 years ago.

How do bug reports factor in to a sprint?

I’ve been reading up on Scrum recently. From my understanding, a meeting is held before the sprint starts, to decide what gets moved from the product backlog to the upcoming sprint backlog. Once a feature is completed in the current sprint, it will go into the “Ready to QA” bucket, and it’s at this point that I’m getting confused. Do bug reports go back into the product backlog? I assume they can’t go back into the sprint backlog as we’ve already decided what work will be done for this cycle? What happens when QA finds a bug? Where does it go?