Almost every manager I know wants to know when a project will be done. Some managers decree when a project will be done. Some managers think they can decree both the date and the feature set. There is one other tiny small subset, those managers who ask, “When can you finish this set of ranked […]
I’m seeing ads for what should be agile program managers on LinkedIn. I can’t tell what these positions really are, but when they say “responsible for management of 15 scrum teams,” that’s an agile software program manager to me. But the distressing part of the ad is when it’s a US-based position with a base
I’ve had a heavy speaking calendar this month. I knew I’d be home, so I accepted a number of local and close domestic speaking engagements. I’ve been surprised by some fantastic stories of managers and employees. First, there’s the well-meaning manager who wants a current tester to be “motivated” to do manual testing. “How do
I’ve been working with program teams lately, and some of them have issues when they talk about different teams on their programs when they use words such as “headquarters” and “remote” locations. The headquarters teams tell me the remote teams don’t listen to them and the remote teams tell me the headquarters teams don’t hear
A few months ago at Agile Boston, Mike Cottmeyer said that when he looks at teams who want to scale agile, he looks at their ability to create working teams. If they can create teams, they can scale. If they can’t, they have little hope of scaling agile. (Mike, if I’m misquoting you, I’ll correct
The good news is that agile has name recognition. The bad news is that a number of organizations are trying to start agile in a big-bang way, especially on programs. Program management is hard enough without throwing a new approach to projects into the mix. Since so many of you are emailing me about this,
It’s a good thing I said my post about musings was just that–musings! I didn’t bring all of you along. Sorry about that. Let me be more clear. A program is a collection of projects, where the value is in the overall deliverable. Yes, each project may have a deliverable that’s valuable, but the value
I often meet people who are transitioning to agile, and they decided to pick Scrum, because it’s a helpful project management framework. Ok, that makes sense. But then they decide that they no longer need project managers, and that the development manager can act as the Scrum Master. The Scrum Master is not a management
The people who are organizing Your Team Needs Women have a good idea–diversity in teams. I have a problem with how they are doing it. I have tried to contribute to the agile community, chairing the Agile 2009 conference, speaking at user groups, writing for a number of outlets, working with my clients. I do
I’ve been working with teams who want to move to agile. Some people on their teams are in another location, where the salaries are cheaper. It’s difficult to get agile started with a geographically distributed team. If everyone’s distributed, it’s easier than if just some people–especially if they are all one function, such as developers