The Agile Online Summit happens Oct 24th-26th. Get your EARLY BIRD TICKET, limited availability!

Get the EARLY BIRD ticket now!

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.

Emilia Breton-Lake on how to manage change towards Agile

In an organization with a long history it is hard to introduce new ideas that are not in line with that history. Emilia went through that and learned how to help teams that have been working in a certain way to explore, and ultimately adopt a new way of working: Agile Software Development. In this episode we refer to The 5 Dysfunctions of a Team by Lencioni, a book that helped Emilia solve the main blockers to change in the teams she worked with.

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.

Sven Schnee on the major consequences of lack of motivation

Lack of motivation is a self-destructing dynamic that can lead a team to dis-integrate. In this episode Sven explains how that dynamic can quickly destroy a team, and what you can do to avoid that fate. He explains his approach and techniques that support the team in developing their motivation.

About Sven Schnee

Sven started his journey as a developer around the year 2000. He experienced many projects and felt the pain of how traditional approaches to software development failed.
A few years ago he discovered Agile and Lean, and he is not going back.
He is an Agile Coach and Founder of Oikosofy. He wants to bring agile ways of working to a variety of customers from small companies to big enterprises. One of his key strengths is helping teams evolve on their path to self-organization.
You can connect with Sven Schnee on twitter, and link with Sven Schnee on LinkedIn.
You can read Sven Schnee’s blog The Product Owner Toolbox.

Luis Gonçalves on using Value Stream Map to help the team “see” the system

Seeing the system is an art that requires attention to detail, but also a technique that allows us to collect the right information. Seeing how we work as a team, and how the external factors affect our performance cannot be done without that information, and Luis shares with us how he used the Value Stream Map as a tool to help a team see the system that was affecting their performance.
The Value Stream Map also proved to be a great way to to collect information that helped the team have a truly valuable retrospective.
We also discuss the different levels of team development using the Shu-Ha-Ri model, and how teams have many skill areas that need to be developed and can be mapped with the help of the Shu-Ha-Ri model.

About Luis Gonçalves

Luis Gonçalves is a Co-Founder of Oikosofy, the Co-Author of the book “Getting Value out Agile Retrospectives”, a book which I use regularly to get inspired to organize innovative retrospectives. Luis is also an International Speaker and prolific Blogger. I don’t know where he gets the time to do all of this 🙂
Luis’ passion lies on the Management side of software development where he tries to apply what he has learned from the Management 3.0 books.
He is also a co-founder of a MeetUp group in Munich, Germany called High Performing Teams. A meetup he created to “Define the future of Management and Leadership”.
You can link up with Luis Gonçalves on LinkedIn, and connect with Luis Gonçalves on Twitter.

In case you are interested in Agile Retrospectives we are at the moment preparing a 10 DAYS FREE AGILE RETROSPECTIVES PROGRAM. This is a complete self-study program where you will learn anything that you need to become a great Agile Retrospectives facilitator.

Get The Booklet!
How to deliver on time and eliminate scope creep By scoping projects around outcomes and impacts, not requirements!
Get the Product Owner Booklet!
Avoid scope creep! And learn to scope projects around impacts and outcomes, not requirements!
Get These Valuable Lessons Today!
Down-to-earth, hard-earned Scrum Masters lessons and the Tips from the Trenches e-book table of contents, delivered by email
Enter e-mail to download a clickable PO Cheat Sheet
This handy Coach Your PO cheat-sheet includes questions to help you define the problem, and links to handy, easy techniques to help you coach your Product Owner
Enter e-mail to download a clickable PO Cheat Sheet
This handy Coach Your PO cheat-sheet includes questions to help you define the problem, and links to handy, easy techniques to help you coach your Product Owner
Enter e-mail to download a checklist to help your PO manage their time
This simple checklist and calendar handout, with a coaching article will help you define the minimum enagement your PO must have with the team
Enter e-mail to download a checklist to help your PO manage their time
This simple checklist and calendar handout, with a coaching article will help you define the minimum enagement your PO must have with the team
Internal Conference
Checklist
Internal Conference
Checklist
Download a detailed How-To to help measure success for your team
Motivate your team with the right metrics, and the right way to visualize and track them. Marcus presents a detailed How-To document based on his experience at The Bungsu Hospital
Download a detailed How-To to help measure success for your team
Read about Visualization and TRANSFORM The way your team works
A moving story of how work at the Bungsu Hospital was transformed by a simple tool that you can use to help your team.
Read about Visualization and TRANSFORM The way your team works