At first I thought this was going to be interesting as it talks about some framework for discussing complexity. But then it devolved into the standard Agile post which just makes vague hand-wavey statements. It also seems to confuse Agile with Scrum. There are other ways to order ones time than sprints.
At the very least, I agree that if one adopts one thing it should be retrospectives. However, there is a huge range in what a retrospective is like. And they are only useful if you can commit to executing on the output, so even just a retrospective is not valuable by itself.
This series of posts came out of a contract I did where teams were going through the motions of ‘Agile’ without understanding that they were actually ‘Scrum,’ nor understanding why each component was important. I wanted them to drop the practices if they weren’t getting anything out of it.
At first I thought this was going to be interesting as it talks about some framework for discussing complexity. But then it devolved into the standard Agile post which just makes vague hand-wavey statements. It also seems to confuse Agile with Scrum. There are other ways to order ones time than sprints.
At the very least, I agree that if one adopts one thing it should be retrospectives. However, there is a huge range in what a retrospective is like. And they are only useful if you can commit to executing on the output, so even just a retrospective is not valuable by itself.
I think you’ll appreciate the second post: https://blog.scottnonnenberg.com/customizing-agile/
This series of posts came out of a contract I did where teams were going through the motions of ‘Agile’ without understanding that they were actually ‘Scrum,’ nor understanding why each component was important. I wanted them to drop the practices if they weren’t getting anything out of it.
There are so many agile blog series on the internet I don’t really see a need to read another one based on this initial post.
I’d love some links to those better posts, if you’re willing to dig a couple up!