277
Being Agile (lemmy.ml)
submitted 5 months ago* (last edited 5 months ago) by yogthos@lemmy.ml to c/programmerhumor@lemmy.ml
you are viewing a single comment's thread
view the rest of the comments
[-] a2part2@lemmy.zip 8 points 5 months ago

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

[-] Naz@sh.itjust.works 3 points 5 months ago

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

[-] a2part2@lemmy.zip 1 points 5 months ago

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

this post was submitted on 15 Jun 2024
277 points (97.9% liked)

Programmer Humor

32479 readers
166 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS