In many of my transitioning to agile clients, the managers want to know when the project will be done. Or, they want to know how much the project will cost. (I have a new book about this, Predicting the Unpredictable: Pragmatic Approaches to Estimating Cost or Schedule.) Managers ask for estimates because they want to […]
I have an article up on agileconnection.com called Common Misconceptions about Agile: There Is Only One Approach. If you read my Design Your Agile Project series, you know I am a fan of determining what approach works when for your organization or project. Please leave comments over there. Thanks! Two notes: If you would like to
Is there room for functional managers, such as development and test managers, in agile organizations? Maybe. It depends on whether they take the role of an agile manager. If you have organized as a feature teams-based organization, the functional managers (development, test, analysis, whatever) can take these responsibilities: Develop trusting relationships with the people on
A recent coaching client was concerned about the progress his team was making—or really, the lack of progress his team was making. We spoke about the obstacles he had noticed. “The team doesn’t have time to write automated tests. As soon as they finish developing or testing a feature, people get yanked to another project.” “Are people, developers
In self-organizing teams, teams remove their own obstacles. It’s a good idea. It can be difficult in practice. In Scrum, the Scrum Master is supposed to facilitate removing the team’s obstacles that the team can’t remove. It’s a good idea. It can be difficult in practice. And, what if you aren’t doing Scrum, or you’re
If you read my Three Alternatives to Making Smaller Stories, you noticed one thing. In each of these examples, the problem was in the teams’ ability to show progress and create interim steps. But, what about when you have a “wicked” problem, when you don’t know if you can create the answer? If you are
When I was in Israel a couple of weeks ago teaching workshops, one of the big problems people had was large stories. Why was this a problem? If your stories are large, you can’t show progress, and more importantly, you can’t change. For me, the point of agile is the transparency—hey, look at what we’ve
“Larry, I need VP approval for this,” said Josh, the director of engineering. Larry looked annoyed. “This is only $30. Why am I signing off on $30?” “Because I have no signature authority on anything. Even though I’m a director, I can’t sign off on any discretionary purchases. I have no capital equipment authorization. I
I posted my slides for my Agile 2014 talk, Agile Projects, Program & Portfolio Management: No Air Quotes Required on Slideshare. It’s a bootcamp talk, so the majority of the talk is making sure that people understand the basics about projects. Walk before you run. That part. However, you can take projects and “scale” them
If you’ve been paying attention to agile at all, you’ve heard these terms: pairing and swarming. But what do they mean? What’s the difference? When you pair, two people work together to finish a piece of work. Traditionally, two developers paired. The “driver” wrote the piece of work. The other person, the “navigator,” observed the