-
One thing I feel terrible in software is when you learn about the domain, you evolve the Model, but you're unable to integrate that into the software. Ending with a misrepresentation of the problem/solution space. You know it's wrong and unable to move it fowardPermalink On twitter.com
♻️ 1 Retweets ❤️ 3 Favorites Mood -12 🙁
-
Then, multiple dimensions can be in place. 👉 Human Factor 👉 Engineering Factor 👉 Product Factor Understanding what's preventing the team to evolve the software when you have a better/useful model, it's key to move things forward.Permalink On twitter.com
-
It's quite probable that you're in between two maturity moments, like Kanban Maturity Model explains. And you cannot longer work as before, and you need to adopt new habits/practices to unlock the desired behaviour. Between two maturity levels there are barriers.Permalink On twitter.com
-
These barriers are the factors that I was talking about in the first place, and they change overtime when you're gaining maturityOn twitter.com
-
👉 Moving from an anemic model to a useful model required breaking a barrier to level up 👉 Implementing that knowledge implies breaking another barrier to reach a different levelPermalink On twitter.com
-
We might get frustrated because we are unable to perform some practices of DDD from start to end, but it only explains that DDD requires multiple maturity levels in different aspects and it challenges not only software and teams org but more dimensionsPermalink On twitter.com
-
Understanding in which place you are unlocks better approaches to address those barriers to help the team level up!Permalink On twitter.com