Answer the question
In order to leave comments, you need to log in
Why are sprints needed?
Hello everyone
. I'm trying to figure out the meaning of sprites, excluding the terms "speed" and "planning", which are needed solely for managing within the deadlines.
Let's say we are a company that is working on its product, and we are not driven by time, only quality. We can release in a week, or we can in 2 months, the main thing is to do the job efficiently. What's the point of fixed sprints when you can just plan a slice of work and move towards completion?
This will not turn out to be a waterfall, where all the work is taken, but a cut, i.e. in our case, the movement is iterative (for example, 1-2 features), but there is no time limit, i.e. Once it's ready, we can move on.
In theory, in this case, the meaning of Agile is lost, because Agile is a way of tracking the life of a project and the possibility of making decisions on time, and if we are not driven by deadlines, then this task simply does not exist.
It turns out that for projects that are not driven by deadlines, there is no point in classic Agile.
What are your thoughts?
Are sprints necessary if the project is driven by quality?
Answer the question
In order to leave comments, you need to log in
The whole point of Agile is described in the Agile manifesto (I strongly advise you to read it, it is small), and there is no talk of any sprints there)
There are sprints in Scrum, which, as you rightly noted, is not suitable for everyone.
If sprints are removed from scrum, kanban will come out, roughly speaking.
The meaning of sprints in scrum is to deliver new features at least in some form in some fixed-short period
Let's say we are a company that is working on its product, and we are not driven by time, only quality. We can release in a week, or we can in 2 months, the main thing is to do the job efficiently.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question