You have a problem with agile methodology, you have a problem with me, and I suggest you let that one marinate.

@psud@lemmy.world
link
fedilink
English
41Y

I loved agile as an analyst, we used to use waterfall and you’d hear about incorrect designs months later, or not at all, where in agile you can work out the details with the programmers and get both nearer the business requirements, and better designs

Also I absolutely love the job of scrum master which had no equivalent in waterfall

@Lysergid@lemmy.ml
link
fedilink
English
41Y

I love waterfall as an developer, I’m using agile now and we have incomplete, conflicting designs every sprint, or spills which affect our metrics, where in waterfall you can workout all the details and have full vision of product and better design with less reworks.

Not to mock you. My point is that methodology is not import when team consists from responsible professionals

There are some instances in which waterfall is not only entirely appropriate, but also the best possible choice in terms of work organization.

There are some instances in which agile is the best fit. Likewise kanban.

Different domains have different optimal workflows.

@psud@lemmy.world
link
fedilink
English
11Y

I don’t take it as mocking or anything, I know that some devs in my team preferred waterfall. I’m just saying there are aspects of agile I really enjoy

Waterfall makes higher quality software in many circumstances. It’s optimised for quality.

Agile is optimised for speed explicitly at the expense of quality. Whatever methodology you can only pick two between development speed, cost, and quality

@SpaceCowboy@lemmy.ca
link
fedilink
English
11Y

I think a lot of it dependent on management. If you have a good product manager, software architect (or whatever) who can have things solidly designed before sending it to development, agile works great. But if the people writing the cards suck at their job, well then the project isn’t going to go well.

But then bad management is going to suck no matter what methodology is used.

@psud@lemmy.world
link
fedilink
English
11Y

You’re right on. We have some good expertise left over from our previous methodology which was both waterfall and siloed so bad feature documents don’t cause too much problem, but once our expertise retires (and we’re not makeing new experts as the silos were removed) the features will need to great to get decent products

And bad management is the biggest thing to make a job miserable

crowsby
link
fedilink
141Y

there’s a special place in heaven for kanban lovers that’s what i always say

@fulcrummed@lemmy.world
link
fedilink
English
9
edit-2
1Y

To be faiiiiiir, it’s is the easiests of the ways of workins.

@NovaPrime@lemmy.ml
link
fedilink
English
41Y

To be faaaaaaiiiiirrr…

@fulcrummed@lemmy.world
link
fedilink
English
51Y

To be faaaaaaaiiiiiiiiir 🎵

Why?

Create a post

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

Rules:

  • Posts must be relevant to programming, programmers, or computer science.
  • No NSFW content.
  • Jokes must be in good taste. No hate speech, bigotry, etc.
  • 1 user online
  • 159 users / day
  • 317 users / week
  • 704 users / month
  • 2.84K users / 6 months
  • 1 subscriber
  • 1.57K Posts
  • 34.8K Comments
  • Modlog