Yes. But the problem is that the simple is not easy. Otherwise everybody what do it. Which is why I think you are missing an important dimension: That of how to produce structure and discipline in software development, which happens within socio-technical systems.
Glad you see the connections of TOSD and the agile problem. We are finalizing the research paper on TOSD right now and will publish it in a few days - until the end of October the latest. The article is merely an announcement or “teaser”, which is why the six characteristics are not quite understandable from the article alone.
Thanx for your feedback Niels, you’re the 1st one to do so!
Indeed, I came up with this approach in response to a team’s desperation and wanting to ditch all agile stuff. So I asked them in layman’s language to do all things agile …
Their working structure emerged naturally and their focus shifted towards delivery and quality.
That said, the same approach didn’t quite work with another agile struggling team. The reason: they were not quite open to change their ways of working.
The path towards simplicity is change (adapting) and the only way to succeed with it is by checking fitness for purpose.
I’m preparing a paper on a system of change based on a fitness sequence and adaptive intelligence. If interested I’ll share when first draft is ready. I’ll need some honest feedback 😂
Excellent piece.
Combines well with Time-Oriented Software Development, TOSD:
https://betacodex.org/white-papers/paper/introducing-time-oriented-software-development-26
Yes. But the problem is that the simple is not easy. Otherwise everybody what do it. Which is why I think you are missing an important dimension: That of how to produce structure and discipline in software development, which happens within socio-technical systems.
You might be interested in this:
https://betacodexnetwork.substack.com/p/time-oriented-software-development
It talks about how to make good use of the "ultimate structure", in software development.
Yep TOSD conceptually nails the agile problem quite nicely. The six characteristics mentioned are not clear to me, can you summarise them.
Glad you see the connections of TOSD and the agile problem. We are finalizing the research paper on TOSD right now and will publish it in a few days - until the end of October the latest. The article is merely an announcement or “teaser”, which is why the six characteristics are not quite understandable from the article alone.
Thanx for your feedback Niels, you’re the 1st one to do so!
Indeed, I came up with this approach in response to a team’s desperation and wanting to ditch all agile stuff. So I asked them in layman’s language to do all things agile …
Their working structure emerged naturally and their focus shifted towards delivery and quality.
That said, the same approach didn’t quite work with another agile struggling team. The reason: they were not quite open to change their ways of working.
The path towards simplicity is change (adapting) and the only way to succeed with it is by checking fitness for purpose.
I’m preparing a paper on a system of change based on a fitness sequence and adaptive intelligence. If interested I’ll share when first draft is ready. I’ll need some honest feedback 😂
I am very much interested, yes.
I hope that you will take a look at Time-Oriented Software Development, too.
We have also done a lot of work around organizational development, a.k.a. change: www.betacodex.org