|
You are here |
friendgineers.rosenshein.org | ||
| | | | |
www.stum.de
|
|
| | | | | [AI summary] The author reflects on their extensive experience with various software development methodologies, emphasizing the importance of adapting Agile principles to fit specific project needs rather than rigidly following prescribed rules. | |
| | | | |
sboots.ca
|
|
| | | | | "Agile" gets mentioned enough in digital government work that can sometimes seem like it applies to everything: is anything not agile? But there's a deeper meaning behind it that's easy to miss: adding agile practices without removing established, "waterfall" processes that slow a team down is a recipe for frustration. Being agile means choosing one approach over another, and deliberately prioritizing what you spend your time on. | |
| | | | |
coreydmccarty.dev
|
|
| | | | | Agile methodologies are really easy to let become strict process instead of dynamic workflow | |
| | | | |
www.sicpers.info
|
|
| | | OK now that the anniversary's out of the way, I can stop being hagiographic towards agile software development and point out the one big flaw in the approach. It's a stinker. Here's the list of everybody mentioned in the manifesto and the principles behind it: The authors ("We are uncovering better ways of developing software",... | ||