Home » Author Archives: Johanna Rothman (page 3)

Author Archives: Johanna Rothman

Johanna consults, speaks, and writes about managing product development. She helps managers and leaders do reasonable things that work. You can read more of her writings at jrothman.com.

When is Agile Wrong for You?

agile-logo

People often ask me, “When is agile  right or not right for a project?” I’ve said before that if the team wants to go agile, that’s great. If the team doesn’t, don’t use agile. That answer is insufficient. In addition to the team, we need management to not create a bad environment for agile. You might not have a great ...

Read More »

Velocity is Not Acceleration

agile-logo

I see a lot of confusion around velocity in new-to-agile teams. Too many people treat velocity as an acceleration measurement. That is, they expect velocity to increase to some large number, as a stable state. Velocity is a rate of change coupled with direction. When managers think they can measure a team with velocity, they confuse velocity with acceleration. As I enter ...

Read More »

Resource Efficiency vs. Flow Efficiency, Part 5: How Flow Changes Everything

agile-logo

The discussion to now: Resource Efficiency vs. Flow Efficiency, Part 1: Seeing Your System Resource Efficiency vs. Flow Efficiency, Part 2: Effect on People Resource Efficiency vs. Flow Efficiency, Part 3: Managing Performance Resource Efficiency vs. Flow Efficiency, Part 4: Defining Accountability When you move from resource efficiency (experts and handoffs from expert to expert) to flow efficiency (team works ...

Read More »

Resource Efficiency vs. Flow Efficiency, Part 4: Defining Accountability

agile-logo

This is the next in a series of posts about resource efficiency vs. flow efficiency: Resource Efficiency vs. Flow Efficiency, Part 1: Seeing Your System Resource Efficiency vs. Flow Efficiency, Part 2: Effect on People Resource Efficiency vs. Flow Efficiency, Part 3: Managing Performance Managers new to agile often ask, “How do I know people will be accountable?” Let’s tease ...

Read More »

Resource Efficiency vs. Flow Efficiency, Part 3: Managing Performance

agile-logo

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 performance? How will I ...

Read More »

Resource Efficiency vs. Flow Efficiency, Part 2: Effect on People

agile-logo

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 won’t take longer if we ...

Read More »

How to Use Continuous Planning

agile-logo

If you’ve read Reasons for Continuous Planning, you might be wondering, “How can we do this?” Here are some ideas. You have a couple of preconditions: The teams get to done on features often. I like small stories that the team can finish in a day or so. The teams continuously integrate their features. Frequent features with continuous integration creates an ...

Read More »

Who Should be Your Product Owner?

agile-logo

In agile, we separate the Product Owner function from functional (development) management. The reason is that we want the people who can understand and evaluate the business value to articulate the business value to tell the people who understand the work’s value when to implement what. The technical folks determine how to implement the what. Separating the when/what from how ...

Read More »

7 Tips for Valuing Features in a Backlog

agile-logo

Many product owners have a tough problem. They need so many of the potential features in the roadmap, that they feel as if everything is #1 priority. They realize they can’t actually have everything as #1, and it’s quite difficult for them to rank the features. This is the same problem as ranking for the project portfolio. You can apply ...

Read More »

Want to take your Java skills to the next level?

Grab our programming books for FREE!

Here are some of the eBooks you will get:

  • Spring Interview QnA
  • Multithreading & Concurrency QnA
  • JPA Minibook
  • JVM Troubleshooting Guide
  • Advanced Java
  • Java Interview QnA
  • Java Design Patterns