This is a guest post by Marcus Hammarberg, author of Salvation: The Bungsu Story, How Lean and Kanban saved a small hospital in Indonesia. Twice. And can help you reshape work in your company. (available on Amazon)
This is the second post on a series by Marcus Hammarberg about how metrics can help engage, motivate and ultimately push a team towards success!
When we first started to work with the Bungsu hospital they were in a devasting situation.
Fast forward 1,5 years and you would see a hospital that was making money every day.
In the end, we turned the hospital from a situation where only the director and her closest staff cared, to a situation where 100 people in the hospital were actively engaged in everyday improvements.
How is this possible? What kind of magic was applied?
Keeping engagment when the bad news hit – Becoming a team!
Sometimes teams enter the “reporting” anti-pattern. Teams exhibiting this anti-pattern are focused on just describing what they have done, but spend little time discussing the value or the reasons why that work is important. In the end, the daily meeting is the engine of collaboration, and as Scrum Masters we need to focus on collaboration more than status reporting. In this episode we discuss how we can help teams move from reporting to collaboration.
Featured Book of the Week: Scrum Product Ownership by Robert Galen
Scrum Product Ownership by Robert Galen is a book with practical advice, real-world tactics, and stories to help understand and shape the Product Owner role. The book is full of ideas that focus on helping the Team and the PO deliver on the promise of Scrum.
About Varun Maheshwari
Varun is a Scrum Master and agile practitioner in Australia. He believes in “being agile” rather than “doing agile”. For him, Agile frameworks are not the goal, but rather “Delighting customers, Zero Defects, Quick ROI, Better team work, Excellent Quality & Shortest ‘Time to Market’” are some of the possible goals.
In Coaching Agile Teams, Elena found a good reminder of how Scrum Masters and team members should be aware of how they relate to each other and how that can have a huge impact on the team’s performance.
About Elena Astilleros
Elena coaches people who hate wasting their time with badly run agile ceremonies, meetings or projects. She gives them tools to get more out of their time while sprinkling in a little enthusiasm and cheerleading. You can find some of her tools in the forthcoming book Invisible Leader.
Sometimes, Scrum teams are not facing any challenges. They might even be “good” at what they are doing. When that happens, it is a sign that Scrum Masters must pay extra attention to the team dynamics and the relationship with their stakeholders. Is the team really that good, or is it so that they are just getting comfortable with the status quo and not willing to improve anymore?
Featured Book of the Week: Agile Software Development by Schwaber and Beedle
The “black book of Scrum”, Agile Software Development by Schwaber and Beedle was the first book published on Scrum and it helped Eduardo understand Scrum and why it was created. It also helps Scrum Masters prepare their arguments for the adoption of Scrum when that is necessary.
About Eduardo Ribeiro
Eddy is passionate about helping people, teams, and organizations foster a culture of continuous improvement where experimentation and embracing change becomes part of their DNA.
He’s also the author of the Beyond Lean Agile Blog, a Co-Founder of the Lean Coffee Portugal Community, Founder of Agile Online Community and Co-Founder & Director of Startup Grind Porto.
As Scrum Masters, sometimes we work with teams that are at the start of their learning journey with Scrum. These teams might even be motivated, and committed teams. But there are many aspects of Scrum that can only be learned with experience. In this episode, we talk about the possible problems we face when working with “new” teams, and how we can help them survive their first Scrum implementation.
Featured Book of the Week: Scrum Mastery by Geoff Watts
In Scrum Mastery by Geoff Watts, Nedeljko found a great list of examples on what differentiates good from great Scrum Masters. He found also many patterns that helped him solve the problems he was facing in his Scrum Master role.
Nedeljko is a Scrum Master and a full-stack developer who has been in the IT industry for the better part of the decade. He spent the last 5 years actively working as a Scrum Master with many diverse teams and projects who has helped him understand his role better. One of the core developers of the first VivifyScrum release, he has participated in its development product-wise ever since.
Even when teams are motivated, and progressing at a rapid pace, there’s an ingredient that, if missing, can derail the whole project. That ingredient is feedback from customers and users. In this episode, we talk about what happens when feedback is missing and how Scrum Masters can help their teams focus on collecting and reacting to feedback.
Featured book of the Week: Scrum, the art of doing twice the work in half the time
In this segment of the episode, we also refer to Edx.Org, a website that focuses on education and includes Agile training as well.
About Henrique Centieiro
Henrique is a Blockchain Product Manager (i.e. dealing with the blockchain related features/user stories of the product). He is passionate about teams and agile, using scrum to manage even his personal tasks.
Ajeet is an IT professional with 17 years of delivery experience in application development, system integration and software testing. He’s served as a ScrumMaster for over 3.5 years for the clients of USA, UK and Australian geographies.