Yes. Yes it is. Well, sort of…
Basically it’s getting a physical deliverable out of the door in a set time frame.
Your team agrees that they can do all the work to bring a feature, x, up to spec and out of the door in (usually) two week increments.
However, that requires some caveats.
The work is agreed upon by all parties that it’s doable - including testing, debugging and deploying.
No other work (with the exception of fires etc) is to be introduced to the team in that period.
All the dependencies have been highlighted and accounted for.
There is a solid, agreed upon definition of done.
That seems to require a level of foresight and planning that most corporations don’t have. That’s almost like a blueprint for failure when some middle manager changes the scope of a project with a hard coded time limit, IMO.
Anyone interested in not-agile development? Maybe we can call it “Ship it when it’s ready” lol
Ancient developer here / not really a coder, but what the hell is “Agile” software development?
Is it some kind of pseudonym for pushing buggy, untested code to a production server or something?
Like a speed run category for software development?
Yes. Yes it is. Well, sort of… Basically it’s getting a physical deliverable out of the door in a set time frame. Your team agrees that they can do all the work to bring a feature, x, up to spec and out of the door in (usually) two week increments.
However, that requires some caveats. The work is agreed upon by all parties that it’s doable - including testing, debugging and deploying. No other work (with the exception of fires etc) is to be introduced to the team in that period. All the dependencies have been highlighted and accounted for. There is a solid, agreed upon definition of done.
However, corpos don’t follow this
That seems to require a level of foresight and planning that most corporations don’t have. That’s almost like a blueprint for failure when some middle manager changes the scope of a project with a hard coded time limit, IMO.
Anyone interested in not-agile development? Maybe we can call it “Ship it when it’s ready” lol
I fully agree. It’s supposed to be the scrum masters job to keep that away from the devs so that they can focus.
Management and other stakeholders are also supposed to be in agreement on both the agile method, and also the book of work for the sprint.
Obviously, if some priority changes mid sprint which is important, the team can agree to pick it up at the expense of agreed upon deliverables