5 ms·
I'll reply with what I said last time: Read the Agile Manifesto, it's been written by people far smarter and wiser than me, and likely most of us. https://agi
by ilc 3y ago
I'll reply with what I said last time:
Read the Agile Manifesto, it's been written by people far smarter and wiser than me, and likely most of us.
https://agilemanifesto.org/ https://agilemanifesto.org/
Manifesto for Agile Software Development
We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on
the right, we value the items on the left more.
---
IMHO: Agile is great. It can even happen without calling it... agile!
Alas: Most SCRUM is not Agile.
My opinion on SCRUM: As implemented in most places, it is WORSE than waterfall. It lacks the planning of waterfall, and the psychological tricks of timeboxing.
That said, I bet you could take all the same "practices" and move them into a better culture, and they'd work.
Culture will always trump process.
- dang 3y agoI understand why it happens but please don't repeat like this - it makes merging threads a real pain! I had to find your original comment and then merge the replies to this one over to that one. More helpful would be to give us a heads-up at hn@ycombinator.com. If a thread is so similar that you're about to copy-paste what you already posted, that's a significant signal of dupiness! or at least followupness (https://hn.algolia.com/?dateRange=all&page=0&prefix=true&query=follow-up%20downweight&sort=byDate&type=comment https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...).
- ghusto 3y agoYeah, I've read it. His point on communists telling him those instances of communism are "doing it wrong" is relevant here.
- bartimus 3y agoSo the problem isn't Scrum; it's that most implementations of Scrum aren't true to its principles, often bending or breaking the rules. Examples: * Having a UX designer role that's not part of the Scrum team * (Those) people working one sprint ahead * Multiple POs * POs not being business owners, but SAFe project managers * Scrum Masters acting like project managers * Teams not owning their sprints * Not letting the team in on backlog creation * User stories written like functional designs, not system requirement * Focus on sprint backlog items as opposed to sprint goals (It's just a to-do list) The point of Scrum is simple: The PO owns the product spec. Developers own the development of the product. It lets engineers do the enginering. Break these rules, and you're letting corporate waterfall creep into the agile process. SAFe often makes this worse. Jira isn't helping either. The reality is that, in a traditional line-management organization, Scrum can help to create an "agile bubble". But you need a good Scrum Master who's going to enforce the rules and safeguarde the agile process. The good ones are rare.