I had a terrific time with Chris Williams on his Badass Agile podcast. We discussed the Modern Management Made Easy books. (Let me just say, I love the fact that I can now say I am a Badass. Hehehe.) We had a terrific discussion. Some of the topics we covered: Are managers born or made? […]
At a recent talk about the Career Ladder posts, someone asked this question: Can managers pair effectively? That’s a great question. Some managers job-share. However, they don’t work simultaneously on the work. One person works for a couple of days. That person then hands off work to the other person. The handoff might work in
You want business agility. The teams have worked hard to change how they work. And you realize your current career ladder isn’t working for you—or the people you serve. The people and teams continue to experiment with agile behaviors. You would like more lateral, not just vertical options to support any person’s growth. What can
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
On the Maintainable podcast, Robby Russell often interviews people about technical issues. Not this time! We discussed the Modern Management Made Easy books among other topics: A little about the origins of agile approaches The issue of “too many meetings” and why they might need to be called something else. (See Decide When You Need
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
Make Better Decisions When You Have Too Much Ambiguity As a leader in the organization, you have a Big Decision to make. You need more data. However, getting the data is impossible in the timeframe you need to decide. The data you want might not even exist. What do you do? You could pray. I’m
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