Marcus Hammarberg explains his recipe for team success

Many management approaches settle for measuring activity instead of outcomes. Marcus asks us to focus more on outcomes to be able to investigate the system conditions. After all it is outcomes that matter. He also asks us to be so precise about outcomes that we can measure it with a single metric. His process is:

  1. Go for smaller and smaller iterations as a way to help teams “own” their work
  2. Bring the outcome definition down to ground-level, so that everyone understands it
  3. Everyone needs to understand the metric. Simplify it.
  4. The metric needs to be one that changes often, so that we can use it as feedback.
  5. Update the metric daily
  6. Celebrate success

Marcus shared with us a discount code for all that purchase his book until October 14th, 2015. Don’t miss it, purchase the book at http://bit.ly/theKanbanBook, and use the code scrumkan.

Marcus is the Author of Salvation:The Bungsu Story, a fascinating account of a real-life crisis, and how Agile, Lean and Kanban saved the Hospital from bankruptcy! Twice! Get ready for the journey, it’s going to be a bumpy ride!

About Marcus Hammarberg

Marcus is a Software / agile consultant from Sweden on IT-sabatical leave in Indonesia, working for the Salvation Army hospitals there. And yes, using techniques from agile in that work even in non-software environments.
One of those approaches he is using is Kanban, as Marcus is the author of the book Kanban in Action with Joakim Sundén, don’t forget to go to http://bit.ly/theKanbanBook, and get the book with the discount code scrumkan.
You can link with Marcus Hammarberg on LinkedIn, and connect with Marcus Hammarberg on twitter.

Marcus Hammarberg on the Water-Scrum-Fall anti-pattern

In many organizations we see teams rushing to adopt Scrum, only to be stuck in the Water-Scrum-Fall anti-pattern. Marcus shares with us one such case, and what he learned from the experience. He shares the metrics that matter in Agile, and why Lean is a perfect complement to the ideas of Agile and Scrum.

Marcus shared with us a discount code for all that purchase his book until October 14th, 2015. Don’t miss it, purchase the book at http://bit.ly/theKanbanBook, and use the code scrumkan.

Marcus is the author of Salvation:The Bungsu Story, a fascinating account of a real-life crisis, and how Agile, Lean and Kanban saved the Hospital from bankruptcy! Twice! Get ready for the journey, it’s going to be a bumpy ride!

About Marcus Hammarberg

Marcus is a Software / agile consultant from Sweden on IT-sabatical leave in Indonesia, working for the Salvation Army hospitals there. And yes, using techniques from agile in that work even in non-software environments.
One of those approaches he is using is Kanban, as Marcus is the author of the book Kanban in Action with Joakim Sundén, don’t forget to go to http://bit.ly/theKanbanBook, and get the book with the discount code scrumkan.
You can link with Marcus Hammarberg on LinkedIn, and connect with Marcus Hammarberg on twitter.

Ebenezer Ikonne on the 5 conditions for great teams

What are the conditions for great teams to emerge? And what are the obstacles? These are some of the questions we cover in this episode. We mention also two very important books about teams, and how to build great teams: Leading Teams: Setting the Stage for Great Performances by Richard Hackman and The Wisdom of Teams: Creating the High-Performance Organization by Katzenbach and Smith.

About Ebenezer Ikonne

Technology enthusiast. Change artist. Culture hacker. People focused. Helping organizations provide their employees with the most meaningful and fulfilling experience they could have while delivering solutions that change the world. Ebenezer is also a Tech Director at Mannheim.
You can link with Ebenezer Ikonne on LinkedIn, and contact Ebenezer Ikonne on Twitter. You can also read his thoughts on Agile on his blog.

Gil Zilberfeld on the most common mistakes we make when recruiting

There are many mistakes we make when recruiting, and Gil describes a good number of those mistakes. Recruiting is a skill that no one teaches you, but Gil shares with us what he has learned over the years

About Gil Zilberfeld

For over 20 years, Gil has developed, tested, managed and designed software products. He’s gone through failures and successes, in different types of projects and companies.
He has trained and coached developers how to write tests for their untestable code. He has worked with testers on complex applications and with very tight deadlines. He’s helped release products that fit customer needs, by testing the waters, and getting their feedback integrated. He has implemented agile, kanban and lean principles and adapted them to fit teams better.
You can link up with Gil Zilberfeld on LinkedIn, or find Gil Zilberfeld on Twitter.
Gil is writing a book on Unit Testing. Check it out.

Juha Heimonen explains how to fail at self-organization

Self-organization is not a simple “tool” you can just spring on teams by saying: “Self-organize! Now you don’t have any managers.” Juha explains such a process, why it failed and what he learned from it that can help you on the path to team self-organization.

About Juha Heimonen

Juha is a entrepreneur, programmer, kanbanista and a unicorn. He calls Software a garden, and says that he tries to be a gardener tending the soil as well as the specific plants.
He is active in the local agile community in Jyväskylä, Finland and also quite active on twitter.
You can link up with Juha Heimonen on LinkedIn and connect with Juha Heimonen on twitter.
You can find out more about his thoughts on Fellowship and how he applies that in his own business at Flowa’s website and blog.

Emilia Breton-Lake on the importance of retrospectives when trying to understand the system

Emilia uses retrospectives and specific questions to help the team discover the system conditions that affect their performance. She also shares how she knows, and has learned to ask the right questions at the right time.

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.

Marc Löffler suggest: involve the team in the hiring process

Hiring people that need to work with or within a team without involving the team in the hiring process can lead to missing critical “chemistry” issues between the team and the candidate. Marc asks us to think about involving the team in the process, and suggests how that can be done.
In this episode we also discuss the anti-pattern of focusing on planning and execution and missing other aspects of team and project development such as the technical environment, the collaboration aspects, etc.

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.

Marc Löffler on the anti-pattern of laughing your way into self-destruction

Laughing is a good sign. The team is probably engaged, relaxed, happy… Or is it? In this episode Marc explains how one team was laughing their way into self-destruction, and what caused it.
We also discuss a method for investigating teams and their development called the Dreyfus model of skill acquistion

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.

Marc Löffler on the anti-pattern of micro-management

Marc explains the story of a team that was starting their Scrum adoption and allowed a project manager to use their tool, the Scrum board, as a tool for micro-management. From that a lot of anti-patterns emerge that Marc struggled with. We also discuss the use of tools for planning vs. using the same tools to generate collaboration and how to switch the focus from planning to collaboration.

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 Sójko on how a project went from perfect to disaster

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.

About Karol Sójko


Developer, software architect and a team leader. Karol is a big fan of Behavior Driven Development and open source software. In his everyday work he tries to share his experience and actively participate in development and spreading a good word about open source projects like Symfony, Behat or PhpSpec. He is also fascinated by the process of making teams work better and tweak their productivity. After hours he is one of PHPers meetups organizers in Poland.
Karol is the author of To-Do: Team!: Simple productivity techniques for improving your team & making software that matters
You can connect with Karol Sójko on twitter, and subscribe to his helpful tips on how to get your team to the next level.