With every great movement, there are pioneers, early adopters, and then the majority who follow their lead. The agile pioneers understood that agile is not a process change, nor a new SDLC to implement, but a whole new way to think and work while serving your customers. So why do most agile transformations focus on teaching frameworks, methods, laws, and practices?

Join me to learn how to activate and encourage this way of thinking, often described as an agile or growth mindset, within yourself and your company on your journey towards a more agile workplace.

If you’ve been exploring agile methods, you probably want to deliver the most value in the least amount of time possible. But what if the best prioritization and planning just isn’t enough to keep your organization at the top of your market?

Enter Impact Mapping, an approach that reveals the hidden assumptions that keep you from reaching your goal. This technique helps when you're looking for innovative solutions to tough business problems because you'll bring in strategic thinking skills as you identify the ones most likely to reach your goal. Even better, you'll know upfront how to measure the impact of those solutions, so you won't invest more than you need.

This workshop is hands-on, so get ready to learn while you’re working!

With every great movement, there are pioneers, early adopters, and then the majority who follow their lead. The agile pioneers understood that agile is not a process change, nor a new SDLC to implement, but a whole new way to think and work while serving your customers. So why do most agile transformations focus on teaching frameworks, methods, laws, and practices?

Join me to learn how to activate and encourage this way of thinking, often described as an agile or growth mindset, within yourself and your company on your journey towards a more agile workplace.

Agile encourages us to eliminate activities that don’t add value and find the simplest solution possible to solve our business needs. For many teams, that can lead to a state where collaborative design no longer happens or is discussed on a whiteboard that gets erased after the conversation.

How then, can you share the knowledge with team members who don’t work on that feature, or join the team after the feature is built? What about distributed teams, are they unable to have collaborative design because they don't have a whiteboard?

I had those same questions in 2012, when Ron Garton of the Agile Coaching Network showed me a lightweight solution and we stopped creating traditional design documents. Ron provided me permission to bring that solution to the agile community through sessions like these.

This solution helps everyone on the team understand what they will create or change in the current systems before it’s built, which can also be retained to increase the domain knowledge for that system later. Though the template itself can be helpful, like many agile tools, it’s the conversation that it starts that’s truly powerful.

Hurricanes Harvey, Irma and Maria left a wake of catastrophic damage in 2017 and overwhelmed all regular forms of assistance.

Individuals and grassroots movements stepped up to fill the gap. Largely unknown people helped other people, neighbors helped neighbors, and all of it used crowdsourcing with methods known as Scrum, Kanban or Scrumban, even when the individuals didn't understand what they were using.

Listen to the story of how an agile coach became part of the response and started a movement to help bring comfort and joy back to over 150 families in the Keys when they needed it most. More importantly, learn how you can use shared common purposes, agile values, principles and methods to do the same for any crisis that might come your way.