You know, agile was always a good term and a good movement until suddenly various industry for-profits peed in the pool. Now nobody wants to go swim there, and maybe we need to pave it over as a parking lot.
In each of these cases, those differences manifest themselves both in the design decision that shape the form and function of that system as well as the process and the organization of the team that creates it.
There is a vast difference in the architecture of a software-intensive system whose output must always be accurate and precise versus one whose output can just be good enough.
Wer das Elterngeld abschaffen will, macht nicht nur Paare ärmer, sondern auch Frauen noch abhängiger von ihrem Partner - und sollte zu Gleichberechtigung zukünftig besser schweigen.
The whole point of a kanban board is that it manages a pull system. When you ship something, you pull the next thing to work on from upstream. If you finish a story, you pull a new one from the customer. A backlog is what's called a "ready' queue. A small list of things to do when you run out of things to do. However, that ready queue is no different than any other column. There's a work-in-progress (WIP) limit, and the queue is not allowed to grow larger than that. Anything more is called "inventory waste." It's stuff you've put work into that may or may not ever be built that is bringing in no revenue.
Contrast this way of working with a huge backlog (all waste) and work, usually more work than they can handle, is pushed onto the teams. Don't know what that is, but it has nothing to do with Lean/Agile principles.
I wrote, "Scrum is a cancer," and the Internet had thoughts about it.
After 3,400 replies, I learned a few things:
First, the most common jobs among the people who told me I was wrong were "Agile Coach" and "Scrum Master." They feel very strongly in favor of Scrum, but I'm not sure why.
Second, Scrum can't fail because Scrum is whatever you want Scrum to be. There's no right way to do Scrum, so if it doesn't work for you, you aren't as bright as you thought you were.
Third, Scrum isn't agile, except when it is. But it's much better than Waterfall, except when it isn't. And it's better than nothing and everything at the same time.
Fourth, many people got triggered by my comparison of Scrum and communism. They say communism is great but recognize they have never lived in a communist society. They keep mentioning this book they read and how every person who shed blood under communism was "doing communism wrong."
Finally, by far, most people hate Scrum with passion.
No matter how you look at it, Scrum is a failure.
Programming is so fun because you get to go from lack of understanding to mastery time and time again, at a rate determined by your speed of iteratively writing & running code, and with real-world impact when you succeed.
Congratulations team!
Thanks to all who worked last weekend to resolve a long-known business concern that suddenly became our top priority.
We really showed the business that they can count on us and we crushed our velocity goal!
Keep it up!
#NotMyAgile
This is an ambitious sprint. So we've asked the team to really step up for the business and we are confident they'll do what's necessary to deliver on the commitments we've asked of them.
#NotMyAgile
I don’t recall where I first heard this , but I like it:
"A problem shared is a problem halved. A joy shared is a joy doubled".
That pretty much is how things work for me. And with a team, there is a bit of a multiplier at work. #SoftwareTeaming#MobProgramming
@PavelASamsonov#Truth - here's what I tell my students & clients:
Users are experts at their own problems & unmet needs. That's what we can learn from interviewing them & listening to requests. They are NOT experts at HOW to solve those problems - that's our job as designers.