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
Go Small to Gain Momentum You’ve seen projects that start off great. They zoom along, delivering. And then something happens. They slow to a crawl. Sometimes, they get stuck so badly you decide to stop and declare victory (or defeat) and start all over. What can you do to make sure that doesn’t happen to
In my article, Which “Scrum Master” Are You Hiring?, I suggested you articulate the type of leader you might be hiring. Why? You might not be hiring a “Scrum Master” at all—but you are likely hiring a servant leader. In this article, let’s discuss the kind of qualities, preferences, and non-technical skills you might need
Have you looked at some of the ads for Scrum Masters lately? Some ads include the need for PMPs or they say they will give you a bonus if you complete the project at a certain time or to someone’s satisfaction. Some talk about hiring the team or about managing the customer’s expectations. Some talk
I posted my most recent Pragmatic Manager newsletter, Scale Agile With Small-World Networks on my site. This is a way you can scale agile out, not up. No hierarchies needed. Small-world networks take advantage of the fact that people want to help other people in the organization. Unless you have created MBOs (Management By Objectives)
If you are organized as platform team, middleware, and front-end teams, you have a component team organization. That made sense at one point in your history. But if you are transitioning to agile or have transitioned, and if you want to use agile on a program, that might not make much sense now. If you
Scale Agile With Small-World Networks Some organizations, when they think of programs (a collection of projects with one business objective), think of many teams, each with Scrum Masters or project managers. That’s one way to scale agile. That’s scaling up. It creates a hierarchy. Hierarchy can slow you down with centralized decision-making, coordination, and communication.
This post is continued from Cost, Value & Investment: How Much Will This Project Cost, Part 1 We’ve established that you need to know how much this project will cost. I’m assuming you have more than a small project. If you have to estimate a project, please read the series starting at Estimating the Unknown:
I’ve said before that you cannot use capacity planning for the project portfolio. I also said that managers often want to know how much the project will cost. Why? Because businesses have to manage costs. No one can have runaway projects. That is fair. If you use an agile or incremental approach to your projects,