BROADCASTS.com

b'

This week, Dan Neumann is joined by Eric Landes to answer a listener\\u2019s question about development. Our listener asked: How can a non-technical Scrum Master or a Scrum Master introduce technical skills and practices to strongly opinionated engineers?

\\xa0

In this episode, Dan and Eric are sharing how to shift the mindset from wanting to know it all about the design to one where emergence is embraced. They share practical tips and examples of real Agile scenarios to make change easier and lessen its costs.

\\xa0

Key Takeaways

\\u25cf How to help engineers to embrace emergence:

\\u25cb Model the behavior and examples.

\\u25cb Go on a learning journey together. Invite them to join the process if they have some technical knowledge.

\\u25cb What is in it for them? They don\\u2019t have to spend time on a design to release that later could not scale as expected, or didn\'t address the customer\\u2019s needs.

\\u25cf How to make change easy?

\\u25cb Eric shares how he started his Agile journey by creating an application that received a lot of resistance from the management.

\\u25cf Emerging design is critical.

\\u25cb The design is fundamental to the core functionality, but the architecture is probably going to fall over in an unexpected way, even with experts things don\\u2019t always get exactly right. Testing rapidly is the way of finding what is wrong earlier.

\\u25cb Make critical architectural decisions first, instead of waiting until the last possible moment.

\\u25cf What are the things people need to get right in the first Sprint?

\\u25cb Chose at least one programming language to use.

\\u25cb Identify the tools that are going to be used and where are you going to deploy the first iteration.

\\u25cb Let\\u2019s experiment with the architecture.

\\u25cf The cost of change in the development is still present.

\\u25cb Take it to the Team: How can we lower the cost of change? How can we make architectural change easier?

\\xa0

Want to Learn More or Get in Touch?

Visit the website and catch up with all the episodes on AgileThought.com!

Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!