@ddd_eu@swardley 4/ I tried to read it several times during 2018. I was unable to really grasp the surface. I put Wardley Mapping on hold.
Lucky me, people joined the mapping movement and built a stronger community.
@ddd_eu@swardley 5/ That's why some years later, in 2020, I found the wardley-mapping-community! Awesome content there! I could learn from more people π§‘π
I liked how all the concepts are synthesized and accessible! π
@ddd_eu@swardley 7/ Then, in 2021, @HiredThought made awesome video content on learning practical wardley mapping. Thanks so much! The courses made mapping more accessible to me π€
It came after understanding the paradigm shift from Organizing teams, where we see a tendency toward @TeamTopologies, #DDD, and #DynamicReteaming as new emerging practices vs the old paradigm.
2/ With a higher #TeamTopologies adoption, it creates new sorts of needs for managers.
Needs that I'm currently facing and I'm currently solving with Excel files to gather team's feedback and improve my organization sensing
3/ I will make the side project publicly as soon as I feel confident about it. Yet, I do a Tweet about it because it boosts my commitment to the side project πβοΈ
1/ I cannot stress enough the importance of junior people in the organization
I'm amazed by how much you learn when working with them. They really show where the organization/team can do better. It can be uncomfortable because they are sharing your weaknesses
2/ Don't think that they should know better to do the job, but why do we create a place where juniors cannot contribute or they have a hard time providing value? What can we do better to help them perform and learn faster?
3/ Juniors help Seniors find their weaknesses, more than seniors helping seniors. Since they show the areas to improve so easily!
- Why take that long to understand this code?
- Why is so hard to do a unit test?
- Why do they get lost in the code structure?
1/ "We expect that anything can happen and we are never prepared for anything"
This sentence resonated a lot with me
Regardless of the risk management, regardless of being adaptative, regardless of how prepared do you think you're, World keeps surprising you
2/ As a manager, your job is to make the teams, product, and business more resilient and adaptative to survive in several situations.
Yet, I never felt that we reached a level where we can say
"We're safe!"
It's not viable.
3/ You manage the areas that are more probable to happen and the impact is higher. Then, you just accept those situations that are outside that scope, to be handled as you can.
1/ We have been debating with some colleagues about the importance of learning about our decisions within the organization, and how the fast rotation of talent that's happening lately is affecting the decision-making outcomes quality.
2/ Here we had the supposition that the feedback cycle between a decision is made and understanding the consequences are long enough. We always thrive for fast feedback loops, yet we acknowledge that that's not always possible.
3/ It's not the same doing TDD within a unit test - feedback cycle of seconds-minutes vs a business decision and go-to-market strategy that can take months.
We are talking about the latter. Where those business learnings are most valuable for the organization
1/ When you start doing project development, you find yourself with tight deadlines, a lot of tradeoffs in quality, and money spend.
You start feeling that you might be doing something wrongly. You feel that you're not delivering business value
Thread π§΅
2/ You learn about Agile, and why deliver working software as soon as possible. You adopt Scrum, but with a project mindset. So, it's a fake Scrum. It's more like a 2 weeks waterfall.
Yet you adopt a very important ceremony important, the Retrospective.
3/ Based on Retrospectives, you start questioning yourself how are you working. Why can we deliver value to the customer? Why aren't we customer-focused?