In Organizing an Agile Program: Part 1, Introduction, I discussed the difference between hierarchies and networks. I used Scrum of Scrums as an example. It could be any organizing hierarchy. Remember, I like Scrum as a way to organize a project team’s work. I also like lean. I like XP. I like unbranded agile. I […]
If you want to organize an agile program, so you can manage the stream of features in your agile program, you have some options. It depends on the size of your program. The communication structures in your agile program matter. How Large Is Your Agile Program? I think of programs as small, medium, and large.
I have an article posted on projectmanagement.com. Think Small: Five Tips for Agile Program Management is up. I’ve been quite busy with client work, and was too exhausted to blog. (I know, can you imagine??) Please comment over there.
If you have an agile project larger than two or three feature teams, you have an agile program. A program is a collection of projects where the objective is one business deliverable. If you’ve managed programs before, you know how difficult it is to keep programs on track. With bigness comes more risk. One of
How Effective Are You? A colleague emailed me, asking me how she could tell if her staff was effective. She had developed a few metrics. But her gut was telling her she was looking at the wrong data. She was right. She was looking at the wrong data. Her managers wanted to know how effective
Imagine you are transitioning to agile. You are a program manager, with a couple of agile projects, and a couple of traditional projects. How do you manage the program? Here’s what a program team looks like. For the sake of argument, assume that Sally is an agile program manager, because we can tell she’s working
I keep hearing a lot about “chief” this and “chief” that when it comes to Big Agile, aka program management. You know, chief product owner, chief architect, that kind of thing. I’m kind of puzzled. I thought agile was all about self organization and no command-and-control. Chief anything reeks of command-and-control to me. At the
Rothman Consulting Group, Inc.Vol 9, #16: Great People Create Great Products November 29, 2012 ISSN:2164-1196 In This Issue: Great People Create Great Products Hiring Geeks That Fit is Available
One of my program management clients is organizing a program and is having trouble thinking about a delivery model that fits their program. They are transitioning to agile and are accustomed to traditional releases. When I suggested they have someone representing deployment on their core team, that was an initial shock to their system, and
Someone asked me again about self-assessments for their agile transition. That got me thinking about this problem of transitioning to agile. I don’t believe agile is for everyone in every circumstance. Some people claim agile has “crossed the chasm.” Certainly, many people are aware of agile. Many people understand that a cross-functional team works in