As people gain experience, they often want new and different responsibilities. In a typical career ladder (Part 1), they had one direction: up. That often creates a problem: great technical people become insufficient managers. Let’s not blame these people—many of them didn’t want to become managers However, if people want more responsibility, the career ladder […]
Part 1 discussed a typical career ladder. I said that when we focus on individual achievements and deliverables, we ignore the agile system of work. Worse, when we reward individual achievements we prevent an agile culture. That’s because agile teams learn together as they create the product. We need career ladders that reward working together.
As I’ve been speaking about the Modern Management Made Easy books, people ask these questions: We’re pretty good with our agile approach. It’s time for performance reviews. How do we reward someone based on individual work when we want teams to work together? What do we do? Can we extend whatever that is to our
I’ve been speaking with several possible clients. They’re having trouble with Scrum. The managers don’t believe the teams need product owners, so the teams don’t have POs. The managers think a Scrum Master can support at least four teams. The teams start a lot and finish very little. The teams think they have too many
We often hear that agile is a mindset. That we need to change our thinking to use agility. Is that correct? That you need to change how you think first, before anything else? I can think I change my mindset all day long. However, I don’t change until I change my actions, my behaviors. That’s
When I think about agile approaches to work, I think about how fast we can change and the cost of those changes. We can change the next decisions about the work because we finish the current work and release it. Multiple deliverables allow us to change what we do and what we plan next. That’s
Several of my clients want to use some sort of maturity assessment for their agile transformations. Often, the maturity levels demand adherence to specific practices or processes. Some of those practices and processes work for my clients now. (I’m not so sure about others.) As my clients evolve, will what they do now continue to
I wrote Unearthing Your Project’s Delays a couple of years ago. I told the story of Cliff, a manager who wanted to understand why the projects were so late. I gave several talks about that article. One eagle-eyed fellow asked me this question, “How long was the time from T0 to T1?” I said, “Managers
As I complete the Modern Management Made Easy books, I realize I need to explain how much tolerance an organization has for experiments. The more clients I have, the more I realize most organizations have a sweet spot for how much they can tolerate experiments or bets. Each person has an affinity for more or
In the agile and lean communities, we talk a lot about transparency. This image is the transparency principle we used in From Chaos to Distributed Agile Teams. I see the most product and program success when the various teams create transparency between them, the middle of the continuum. That’s the full-product transparency. I see many