3 ms·
Does this quote from the article: > They were all working hard, that was clear, but there was a fatal flaw: no one really knew what the project was ultimately
by azangru 4y ago
Does this quote from the article:
> They were all working hard, that was clear, but there was a fatal flaw: no one really knew what the project was ultimately supposed to look like, or exactly what purpose it was supposed to serve.
sound like scrum though? No product owner, who would have a vision for what the product's purpose was or what it was supposed to eventually look like. No product backlog outlining a path to get to the vision. No sprint reviews with the product owner and stakeholders to inspect whether the product is on the right track. At least not that I saw in the article while quickly skimming through.
What she is describing is some techniques picked from some agile methodologies; but lacking the proper spirit of the game.
- sgt101 4y agono true scotsperson?
- geodel 4y agoYep, pretty simple really. If it works then only it can be called agile. E.g. we sacrifice goat everytime story is complete and human when an epic is completed successfully. It has worked so well for us. So I am gonna call it Right™ way of doing agile.
- sgt101 4y agoI am happy with that so long as you : a) do not try and make other people kill goats, and b) do not insist on stopping the other team that likes to shave its hair after every show & tell because that works for them.
- geodel 4y agoWell b) is excellent point. Instead of stopping it should be promoted everywhere.
- sgt101 4y agoactually just wet myself a little bit when I read this.
- azangru 4y agoIt's cool if some people prefer to shave their hair, while others say that this goats business is silly anyway and better be skipped; but then they shouldn't claim that they are the followers of Right(tm). It's only fair. Whereas you can hear people claim that they are doing scrum, or even develop a strong dislike to scrum without actually doing what's in the scrum guide.
- mch82 4y agoThis is agile: https://agilemanifesto.org/ https://agilemanifesto.org/ If the result isn’t “working software” created with “customer collaboration”, while “responding to change”, then it’s not agile. There are also twelve principles (https://agilemanifesto.org/principles.html https://agilemanifesto.org/principles.html). My favorite is: (7) Working software is the primary measure of progress.