I started this series with many specific concerns about a particular interview question: “The product owner and dev team cannot decide on a sprint goal, even after hours of discussion. They (the team) feel that the tasks for the sprint are too varied to manage to a single sprint goal. What should the Scrum Master […]
If you’re trying to use an agile approach, what do you care about in terms of finishing: That the team finish the work, regardless of the personal or team cost? That you know who did what, so you can reward them? Or that the team completed the work, without undue stress and strain? (also called
Fred, a client, asked how I could help him get more work out of his resources. I asked if he meant people. He said yes. So I asked if he focused more on what each person did or if he focused on the team’s work. “Each person.” I smiled and said, “I have a deal
Gregory Miller and I discussed the ideas of behaviors vs mindset on his podcast. See Behaviors Create an Agile Culture with Johanna Rothman. We spoke about the Modern Management Made Easy books. In our wide-ranging discussion, we discussed the various traps that managers create or encounter: Rewarding heroics instead of collaboration. How to offer credit
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?
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
It’s time to wrap this series. I started asking if you actually need an agile approach in Part 1 and noted the 4 big problems I see. Part 2 was why we need managers in an agile transformation. Part 3 was about how people want a recipe. Part 4 was about how “Agile” is meaningless
I started this series asking where “Agile” was headed. (I didn’t like what I saw at the Agile 2019 conference.) Part 1 was about the 4 big problems I see. Part 2 was why we need managers. Part 3 was about how people want a recipe. This part is about what “Agile” or “agile” means.
I started this series asking where “Agile” was headed. Part 1 was about the 4 big problems I see. Part 2 was why we need managers. This part is about how people want a recipe, The Answer, for how to get better at “Agile.” Before we can address what an answer might be, your need
I just read Zappos is struggling with Holacracy because humans aren’t designed to operate like software. I’m not surprised. That’s because we are humans who work with other human people. I want to talk with people when I want to talk with them, not when some protocol tells me I must. It’s the same problem when