Here’s where we are so far in this discussion of what it might mean to “scale” agile approaches: Part 1: Creating Cross-Functional Feature Teams (Teams that can produce features on a regular basis) Part 2: Programs of Cross-Functional Feature Teams (Programs (multiple teams working together) that deliver features on a regular basis) Part 3: Agile Product […]
In the “Scaling” Agile: Part 1, I wrote about cross-functional collaborative teams. The cross-functional collaborative feature team is the basis for “scaling” agile. In “Scaling” Agile, Part 2, I wrote about programs. I realized I need another part before my original part 3 :-). This new part 3 is about creating agile product development capabilities.
The first post was about scaling functions to working as collaborative agile teams. See Defining “Scaling” Agile, Part 1: Creating Cross-Functional Teams. Now, let’s talk about moving to multiple teams working together, a program. The good news is that you have a few cross-functional teams. They’ve been delivering as project teams. And, now you have a
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
Agile 2015 was the week of Aug 3-7 this year. It was a great week. Here are the links to my interviews and talks. Interview with Dave Prior. We spoke about agile programs, continuous planning, and how you might use certifications. I made a little joke about measurement. Interview with Paul DuPuy of SolutionsIQ. We
We encounter problems all the time. Some we can resolve on our own in a couple of minutes. Some take more time, and/or we can’t resolve them alone. What do you do then? I’ve had a policy for about twenty years for when I become stuck. If I’m stuck for more than twenty minutes, it’s
Several years ago, I had a senior VP as a client. He wanted his managers to work as more of a team. He thought they were not working together for the good of the company. I asked him why he thought that. “When they estimate, they don’t work together on an estimate. They each estimate
I have finished integrating comments from the early review of Agile and Lean Program Management: Scaling Collaboration Across the Organization. I decided that the book was good enough to release to the general public. I find it difficult to release books in progress. The in-progress part challenges my perfection rules. However, since this is an