This is the next in a series of posts about resource efficiency vs. flow efficiency… Managers new to agile often ask, “How do I know people will be accountable?” Let’s tease apart the pieces of accountability: Accountable to the project for finishing their own work Accountable to their team for participating fully by doing their […]
Resource Efficiency vs. Flow Efficiency, Part 1: Seeing Your System explains resource efficiency and flow efficiency. Resource Efficiency vs. Flow Efficiency, Part 2: Effect on People explains why flow efficiency helps you get features done faster. Here, in part 3, I’ll address the performance management question. New-to-agile (and some experienced) managers ask, “How can I manage
If you haven’t read Resource Efficiency vs. Flow Efficiency, Part 1: Seeing the System, I explain there about optimizing for a given person’s work vs. optimizing for features. Some people (including managers) new to agile have questions about working in flow vs. optimizing for a person. The managers ask: How do I know the work
I’ve been working with a number of people who want to work in a more agile way. These nice folks have one stumbling block: resource efficiency vs. flow efficiency. This is partly because of how they see the system of work. If you ever used phases or a waterfall approach, you might have tried to
Commitments or Resilience Ben, a program manager, said, “My management wants a quarterly commitment. They think this will let them commit to customers about features. But, this is a problem for a couple of reasons: we change our minds more often than once every 12 weeks and the managers are talking to other managers, not
I keep seeing talks and arguments about how the portfolio team should manage the epics for a program. That conflates the issue of project portfolio management and product management. Several potential teams affect each project (or program). Starting at the right side of this image, the project portfolio team decides which projects to do and
I see people measure all kinds of things in projects. Too often, they are single-point or single-dimension measurements. Those measurements don’t provide you with a good idea about the health of your project. They might be a start. However, they are insufficient. Imagine you, like me, would like to lose some weight. You weigh yourself
Several weeks ago, the nice folks at FogCreek interviewed me. It’s here: Technical Hiring and Cultural Fit – Interview with Johanna Rothman. The interview ranged over many topics: Cultural fit Diversity What to do when you look for a job Much more I hope you enjoy it. If you want to read more about how
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
, In my session at Agile 2015, (Agile Hiring: It’s a Team Sport) one participant asked me if I hire contractors the same way I hire employees. I do. I use the same approaches for reviewing resumes, phone screens, interviews and decisions. The one difference is the offer—instead of a yearly salary paid in some