I coach it to be even simpler. There’s no definition of an Epic, Capabilty or Feature. None of those provide value. They’re just containers for a group of similar work. There are only User Stories. Some small, some big, some really big. Break them down so you can implement and provide value, incrementally, every iteration.
Throw all the other terms away!! They just add confusion and provide an excuse to practice waterfall, I.e., we only release Features, which contain multiple stories and take weeks or months to complete.
You're on fire at the moment Maarten. Really enjoying your writing. A unique point of view. It's outside the agile industrial complex. It's future focused. Looking forward to your book.
I find using some of the most popular tools incredibly annoying, as they lead you down the Project Management path by default.
When you establish process on a Manual system and then try replicate in the tool, it feels like there is always a number of adjustment away from idea because of the tool.
I miss the initial days of some of the popular tools, when they were all about a backlog and enabling the manual ways of doing things.
I'm grateful for the focus on tooling because I always thought tooling needs to enable good practices and abide by the principles (distinct from process) or else they are useless. As for work item hierarchy; I always know chaos will ensue when the work item hierarchy is introduced but there is no formal definition for each item to make it distinct above the team level. It's a red flag.
Also, do you think the practices of Scrum and the guidance of a User Story being a unit of work to be delivered in 3-4 days or a Sprint led to this current-state in tools?
I coach it to be even simpler. There’s no definition of an Epic, Capabilty or Feature. None of those provide value. They’re just containers for a group of similar work. There are only User Stories. Some small, some big, some really big. Break them down so you can implement and provide value, incrementally, every iteration.
Throw all the other terms away!! They just add confusion and provide an excuse to practice waterfall, I.e., we only release Features, which contain multiple stories and take weeks or months to complete.
You're on fire at the moment Maarten. Really enjoying your writing. A unique point of view. It's outside the agile industrial complex. It's future focused. Looking forward to your book.
I find using some of the most popular tools incredibly annoying, as they lead you down the Project Management path by default.
When you establish process on a Manual system and then try replicate in the tool, it feels like there is always a number of adjustment away from idea because of the tool.
I miss the initial days of some of the popular tools, when they were all about a backlog and enabling the manual ways of doing things.
I'm grateful for the focus on tooling because I always thought tooling needs to enable good practices and abide by the principles (distinct from process) or else they are useless. As for work item hierarchy; I always know chaos will ensue when the work item hierarchy is introduced but there is no formal definition for each item to make it distinct above the team level. It's a red flag.
Also, do you think the practices of Scrum and the guidance of a User Story being a unit of work to be delivered in 3-4 days or a Sprint led to this current-state in tools?