article thumbnail

Effective Agility Requires Cultural Changes: Part 1

Johanna Rothman

I see many teams and team members who say, “Agile stinks. ” When I ask people what's happening, they say: We're doing an agile death march because someone else already told us what we have to do and the date it's due. And don't get me started on how coaches tend to do life coaching instead of support for agility.)

Agile 88
article thumbnail

Tired of Fake Agility? Choose When to Experiment and When to Deliver

Johanna Rothman

I have a new book: Project Lifecycles: How to Reduce Risks, Release Successful Products, and Increase Agility. I wrote it because I'm concerned about what I see in too many supposedly agile teams: Crazy-long backlogs and roadmaps. Worse, sometimes the team doesn't demo or deliver. The post Tired of Fake Agility?

Agile 84
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Agile Approaches Offer Strategic Advantage; Agile Tools are Tactics, Part 2

Johanna Rothman

So when does it make sense to customize your agile approach to gain a strategic advantage? Example 1: Startup/Small Organization with Few Products. They offer their product in two versions: Pro and Lite. They want an agile approach, so they started with Scrum. Some of the regular product teams figured out one-day stories.

Agile 105
article thumbnail

Unemployed Agilists: How to Increase Your Value to Get a Great Job, Part 3

Johanna Rothman

That part discusses why managers see agile coaches and Scrum Masters as staff positions, not line jobs. I assume you have some sort of functional product development expertise. If not, why are you in technical product development? This post is about your deep domain expertise, first in product, then in agility.

Agile 81
article thumbnail

Create Feedback Loops (Agile Approaches) for Hardware Products

Johanna Rothman

In Costs of an Agile Approach for Hardware Products , I suggested that an iteration-based approach for hardware was too expensive. Agile software teams are cross-functional and interdependent. Many agile software teams have somewhere between four and seven people. This hardware team swarms on a product.

Agile 52
article thumbnail

Agile Project Manager, Scrum Master, or Product Owner?

Johanna Rothman

We had (and still have) too many products to keep the same teams on them for a long time. For programs, the team stayed together and moved to a different feature set/internal product until the program finished. We could move to a new product and/or a new team. My job was to smooth the way for people to deliver products.

Agile 60
article thumbnail

What Lifecycle or Agile Approach Fits Your Context? Part 3, Incremental Lifecycles

Johanna Rothman

Once the team completes that highest priority feature(s), the team can release the product. When we release, we can regroup and figure out what to do next for this product. Fork another product. (I I did this with several Lite vs Pro products using this approach.). Opportunities for More Agility.

Agile 112