Programming

17540 readers

66 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 2 years ago

MODERATORS

snowe

Ategon

[email protected]

423

Study finds 268% higher failure rates for Agile software projects (www.theregister.com)

submitted 5 months ago by [email protected] to c/programming

137 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 5 months ago

Might wanna read it again, it's right there :)

The best architectures, requirements, and designs emerge from self-organizing teams.

It's an incredibly critical part companies love to completely ignore.

If you assign devs to teams and lock em down, you've violated a core principle

And it's a key role in being able to achieve these two:

Agile processes promote sustainable development.

And

The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

This is talked about at length by the likes of Fowler, who talk about how locking devs down us a super fast way to kill sustainable development. It burns devs out fast as hell.

Note that it's careful not to say on the same project