Does Agile apply when managing a company? In this episode, Simon Severino shares his story and his business of taking Agile to the C-Suite of fast-growing companies!
If you follow this podcast, the success of Agile methods is not a news item. It’s clear that Agile has improved greatly our ability to deliver software products to the market. In this episode, however, we look at a different application of Agile ideas. What if we could apply Agile to the methods we use to manage our businesses? That’s where this interview focuses: how Agile changes our approaches to running a business.
Simon is a growth consulting, he works with business leaders to help them improve the performance of their business. He does that using methods that will sound familiar to all Agile product development team members.
Managing your business as if it were an empirical problem, not a planning problem
“Most purpose statements are dry and uninspiring”, that’s how this episode starts. But Stephen goes deeper and explains why that may be the case. We dive into what are the missing aspects in most purpose statements and share some examples of how he’s been able to help organizations go beyond those dry and uninspiring purpose statements.
The three types of purposes we need to take into account
This is a BONUS episode on the topic of #NoEstimates. The Agile Wire podcast hosts Jeff Bubolz and Jeff Maleski interview Vasco Duarte.
Some of you might have heard about #NoEstimates, and want to know more, and for others, it might be the first time you hear about it. Either way, in this episode we talk about the origins of #NoEstimates and why you may want to consider it when helping your teams.
This is a shared episode with a fellow Agile podcast The Agile Wire, where hosts Jeff Maleski and Jeff Bubolz interview Agile practitioners. Both Jeff Maleski and Jeff Bubolz have been guests here on the Scrum Master Toolbox podcast.
About Jeff Bubolz and Jeff Maleski
Jeff Bubolz is a speaker, trainer, and agile coach. He has been a Product Owner, Scrum Master and Development Team member. Jeff has worked with enterprise companies to small start-ups. His goal is to end human suffering in organizations, by nudging people to be the change they want to see in the world.
Jeff Maleski is passionate about working with and building up both individuals and teams using ideas from Jurgen Appelo’s Management 3.0 and Dan Pink’s Drive. When leading project teams, Jeff strives for empirical based planning and forecasting, continuous learning, and delivering high quality software products that exceed expectations. Jeff believes in leading by actions and focusing on building relationships with others.
#Remote meetings have been a topic that affects Agile teams for a long time. As many more teams go #Remote without previous experience, they become an even bigger topic for Scrum Masters who now need to facilitate online meetings almost every day.
In this episode, Lisette Sutherland (creator of the Work Together Anywhere Workshop) joins us to share her insights on how to make those remote meetings rock!
When going #Remote, it is harder to get the life/work balance right
Katja is an Agile Coach in an organization that had to organize a distributed/#Remote Big Room Planning session in less than 24 hours! Listen in to learn how they pulled it off.
One of the key learnings from that effort was that a #Remote event will take a longer time (maybe 3-4 days) than a locally organize Big Room planning event. But there are many more insights that Katja shares on this LIVE Q&A
What have been the biggest challenges for you and for the teams that you support?
Molood joins us in the special LIVE Q&A episode to talk about Distributed Agile software development and many tools, tips, tricks, and techniques for teams that just recently moved to a #Remote-first work setting.
The POWER framework for successful #Remote meetings
Scrum Masters often have to face cultural anti-patterns when working with teams, and the organizations they are part of.Those cultural anti-patterns are being amplified by the move to #Remote work due to the #covid19 situation.
What can we do? How can we get ready?
Here are some tips to get you started or to help you further adapt to this new reality.
Lack of transparency is even worse when #Remote
There are many Scrum Masters that come on the Scrum Master Toolbox Podcast and share stories that relate to a culturally-engrained lack of transparency. This lack of transparency takes many forms:
Team members don’t share their struggles in the Daily Standup because they perceive that as a sign of weakness (for example)
Product Owners don’t share the reasons why certain changes are brought into the Sprint, perhaps because they themselves don’t know
Other teams we collaborate with don’t share changes to a dependency we have on them
Whatever symptoms of lack of transparency you experienced when working in the same office, those symptoms will only get worse when our organization moves to #Remote work. Some of the reasons are:
Individuals are less engaged and motivated due to the stress, or being distracted by the presence of children while they work, or because they don’t see (and therefore don’t take into account) their colleagues during the day
Sudden tasks or priority shifts are communicated to individuals, and the rest of the team isn’t physically present to witness that change
Now that we’re distributed we miss out on all the spontaneous collaboration that used to happen.
Tips for Scrum Masters to increase transparency and foster collaboration
As Scrum Masters, we must be deliberate about improving transparency and collaboration in #Remote teams. Our domain of expertise is collaboration, and we must keep adapting to enable collaboration at all times. Here are some tips, that may help you improve transparency, information sharing, and collaboration between team members and with other teams:
Have a collective retrospective with the teams on which your team has regular dependencies
Discuss with the Product Owner how to share changes to the Sprint so that all team members are aware and can share their possible impact on the work they have to finish
Move to a shorter Sprint. Agile is about creating more, and faster, feedback loops. As we go #Remote those feedback loops are even more important. Shorter sprints provide more transparency (problems are found faster), makes the amount of work smaller which helps with clarity (shorter stories), and with identifying and solving process problems in the team, and across teams
Have 2 daily check-ins
Quick tip for #Remote#Scrum Masters: Have 2 check-ins / day. One at the start of shared work hours, and one closer to the end of shared work hours. Make the second an “informal” check-in (e.g.: ask each team member to bring their favourite drink and enable video).
Integrate more often. If you are integrating with dependant teams at the end of the Sprint, consider bringing their work into your daily build pipeline, or assign specific team members on both teams to work on integration from the start of the sprint
Track dependencies on other teams just like you would a User Story. Understanding of dependencies will grow during the Sprint. Make sure you are covering that dependency on the Daily Standup if nothing else to learn that “everything is proceeding according to plan”
Create an URGENT Slack/Teams channel, so that team members can always explicitly ask for help to solve a problem they are facing. When #Remote, even waiting one more day can make the problem harder to find.
When we are #Remote, collaboration and cooperation are harder to achieve, and transparency can be a critical trigger for that collaboration to flourish. Consider what you can do as a Scrum Master to improve collaboration. Every day.
Stay Safe, #StayHome
More tips, and more insights from the Scrum Master Toolbox Podcast
Many of us are going #Remote because of the #covid19 situation world-wide. In this very special episode we cover tips, tricks and techniques on how Scrum Masters can help their teams go #Remote to thrive, not just survive.
In this episode, we mention a treasure trove of resources to help you in your adaptation to #Remote work. You can find those below
Resources for going #Remote and Distributed Agile teams
Setting up teams to work collaboratively is one of the challenges that organizations go through when adopting Agile. The functional team setup (all DBAs, all testers, all windows devs together, etc.) is not acceptable for teams that want to quickly develop and deliver products and services to the market. But neither is it possible to have all possible skills (sometimes 10’s of skills) in one team because organizations simply don’t have that many people with certain skills.
In this episode, we talk about the possible team topologies, and how each of those affects our ability to deliver in different organizations.
How we set up teams directly affects the quality of the software teams deliver
What is Business Agility? In a time where it seems that every company wants to adopt Agile, there’s also the dark side of Agile: the belief that it only affects “people in the IT department”. That could not be further from the truth.
In this episode, we have Evan Leybourn sharing what Business Agility is about, and why it matters for your organization.