User Stories needs to have certain characteristics before they can be interpreted and transformed into running-tested-code by the team. What are those characteristics? Matthias explains how he helped a team rein-in a planning process out of control with a very simple User Story maturity framework. A few simple steps to make sure your Stories are high quality.
About Matthias Seul
Matthias worked 10+ years as software developer and gravitated towards coaching in recent years. He is a tech enthusiast, board gamer, inventor and wild duck. Matthias believes in intrinsic motivation – thus he believes in Agile. He says that “together we can make projects a more fulfilling and successful work environment for all involved”.
You can link up with Matthias Seul on LinkedIn, and reach Matthias Seul on twitter. Matthias is interested in your questions and feedback, and you can reach him via email as well.
How do you measure your success as a Scrum Master? Emilia shares her definition of success, and her main tasks in the search for that successful outcome. The tool that she uses the most is 1-on-1 conversations that help her focus on the right topics and discover possible blockers. As she puts it: “whenever you have a question: ask the team!”.
About Emilia Breton-Lake
Emilia is a natural-born Agile thinker who managed to swim out of the PMI waterfall almost a decade ago. As the head of the PMO at a major non profit she is constantly looking for new ways to build better software and make the world a better place.
She has also been working on 2 major innovations, On going retrospectives, and #NoNumbers where they have eliminated sizing of stories. They still groom and plan, but don’t assign sizes to stories.
Emilia has worked hard to introduce Scrum and Agile to a non-profit that is very resistant to change.
You can link up with Emilia Breton-Lake on LinkedIn. Or follow Emilia Breton-Lake’s articles at the Scrum Alliance website.
Involving the customer is one of the key aspects of building the path towards an agile product development environment. There are many types of customers, and we discuss how to involve some of the most common types of customers. Marc also suggests some tools, like Story Mapping, that you can use to work directly with customers and create a shared understanding of the ultimate goal.
About Marc Löffler
Marc’s passion is to help teams implementing agile frameworks like Scrum and XP and to transform our world of work. Marc loves to help teams, that are struggling with agile transitions, to overcome dysfunctional behaviour. He loves to generate new insights by approaching common problems from the other side and trying to deliberately make havoc of the process.
You can connect with Marc Löffler on Twitter, and link with Marc Löffler on LinkedIn.
He hosts a Blog in English and another blog in German.
Karol shares his story of how a project went from perfect to disaster. From engaging and motivating to unfocused, “pet project” and un-interesting for the team. His experience made a big difference for his career, and has influenced his work as a team lead and Scrum Master.
SPECIAL GIVEAWAY INCLUDED: listen to the end of the episode for a giveaway that will help you get a free copy of Karol’s book: To-Do: Team!: Simple productivity techniques for improving your team & making software that matters.
Many teams will consider their Product Owner a “chicken”, but the Product Owner is a key part of the Scrum team, and Steve explains why – a very important insight for all Scrum teams. Steve also refers to a method of collaboration that is known as #MobProgramming, and how to learn to trust each other in a Scrum team.
About Steve Hoyler
Steve Holyer serves as advocate, trainer and mentor for companies looking for a better ways of working, using Agile practices in a productive, fulfilling, and fun way.
He learned his craft serving as a Scrum Master with multiple teams and organisations, so he knows how to change an organisation from the inside. Steve now serves as an indie-label Agile Coach-for-Hire. He’s passion lies with coaching managers and teams to find ways to do software better.
You can contact Steve Hoyler on twitter, and find Steve Hoyler on LinkedIn. For more, check his Lift Off workshop.
Recruiting is not easy, but when you are recruiting for an offshore team you face even more problems. How to select the right candidate? The role of language in the relationship with the client, and how to handle multiple cultures are also topics in this episode. Teams face cultural barriers, and remote stakeholders. In this offshore context recruiting is not easy.