- Agile Leadership Development
- Product Owner
Tip 4 – Use the Agile Management Canvas as a guide to Agile adoption or transformation.
After explaining the basics of the model (three jobs, two sides), share the canvas with a group that is interested in adopting an agile approach. Have them provide their subjective input into which elements on the canvas are the biggest
Readers! Subscribers! “Followers”! I hope you are all healthy and safe.
What is “Technical Debt”?
People are still debating over the one true meaning of the term “technical debt.” It was coined by Ward Cunningham around 2009, and the short definition is this:
Technical Debt is the deferment of good software design for the sake
Tip 3 – use the full Agile Management Canvas to see the larger system of management when trying to address challenges.
If we take the example of a team complaining that their daily standup is taking too long and start to look for ideas in the canvas, we might start with the Collaboration Structures element.
Tip 2: Use the jobs and the two sides to identify areas that may be out of balance in your organization.
As an example, I’ll give you an outside view of Tesla motors. Full disclaimer – I’m a shareholder and a student of Tesla, but I have no insider information so take it with a huge
Tip 1: Use the three jobs to clarify responsibilities in the organization.
For example, the job of Creating Clarity has an overlap between the role of the Product Owner on a Scrum team. Which responsibilities belong to management and which belong to the Product Owner? You can use the elements in the Agile Management Canvas,
I’ve discovered that the people who get the most out of training do these 5 things. Here are some key tips to maximize learning in a virtual environment. Read More
I encourage my clients to find and focus on the core value of whatever they’re creating. What is it that doesn’t yet exist in the world but should? Go there first. Don’t defer that value.
“But we need to create the infrastructure for that first, don’t we?” they often reply, by which they mean things
Ron Jeffries coined the term #DarkScrum.
#DarkScrum occurs when we focus on enforcing Scrum mechanics rather than reinforcing Agile Values and Principles.
This results in