The more I work with project portfolio teams and program managers, the more I understand one thing: Cost accounting makes little sense in the small for agile, maybe for all knowledge work. I should say that I often see cost accounting in the form of activity-based accounting. Each function contributes to some of the cost […]
If you’re thinking about agile or trying to use it, you probably started with iterations in some form. You tried (and might be still trying) to estimate what you can fit into an iteration. That’s called “pushing” work, where you commit to some number of items of work in advance. And, if you have to
Agile is iterative and incremental development and frequent delivery with cultural change for transparency. What do the words iterative and incremental mean? Iterative means we take a one-piece-at-a-time for creating an entire feature. Iterative approaches manage the technical risk. We learn about the risk as we iterate through the entire feature set. Incremental means we deliver those
I’m doing a Twitter chat November 3 at 4pm Eastern/8pm UK with David Daly. David posted the video of our conversation as prep for the Twitter chat. Today he tweeted this: “How do you optimize for features? That’s flow efficiency.” Yes, I said that. There were several Twitter rants about the use of the word
I started this series writing about the need for coaches in Coaches, Managers, Collaboration and Agile, Part 1. I continued in Coaches, Managers, Collaboration and Agile, Part 2, talking about the changed role of managers in agile. In this part, let me address the role of senior managers in agile and how coaches might help. For years,
In Coaches, Managers, Collaboration and Agile, Part 1, I wrote about circumstances under which a team might want a coach. It wasn’t an exhaustive list. It had several questions defining when coaches might help the team to become agile, not be cargo cult agile. One of the reasons we might need coaches for a team is because
There was a fascinating Twitter conversation last week when I was busy writing other things. (I also find Twitter to be a difficult-for-me arena to have a conversation. I need more than 140 characters.) The conversation started when Neil Killick tweeted this: orgs need coaches not because “agile is unintuitive”, but because effective sw delivery
In What Agile Project Managers Do, Part 1, I described what facilitative agile project managers do. In What Agile Project Managers Do Not Do, Part 2, I described a number of roles a more traditional project manager might think is their job still, even if they are supposed to be/use agile. Sometimes, people get confused with
In What Agile Project Managers Do, Part 1, I spoke about what agile project managers might do. Here’s what agile project managers do not do: The agile project manager does not assign work. The agile project manager does not estimate work on behalf of the team. The agile project manager does not commit to features,
One of the questions I hear all the time with people transitioning to using agile is this: How do we organize the project if we don’t have a project manager? If you read Manage It!, you know I don’t buy the idea of a controlling project manager. But a facilitative project manager? Oh my. That