Remove Agile Remove Efficiency Remove Guidelines Remove Productivity
article thumbnail

Middle Management Guideline: Only Plan for as Long As Your Management Can Commit

Johanna Rothman

See Create Successful Schedules: Three Tips to Rolling Wave Planning and the series that starts with Alternatives for Agile and Lean Roadmapping: Part 1, Think in Feature Sets. Later, she used these ideas for the product roadmaps. There's plenty more about rolling wave planning on this blog.) See Pairing, Swarming, and Mobbing.)

article thumbnail

Where I Think “Agile” is Headed, Part 5: Summary

Johanna Rothman

I started asking if you actually need an agile approach in Part 1 and noted the 4 big problems I see. Part 2 was why we need managers in an agile transformation. Part 4 was about how “Agile” is meaningless and “agile” is an adjective that needs to be applied to something. That would be resilient.

Agile 65
Insiders

Sign Up for our Newsletter

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

article thumbnail

Leadership Tip #13: For Innovation, Remove at Least One Policy or Procedure a Week

Johanna Rothman

Now, these same managers want business agility. The more we remove, the more agility or improvement we might see. As the organization changes (both products and tooling), people might not make those mistakes again. About a decade ago, an organization suffered three consecutive bad deployments to production.

Policies 130
article thumbnail

Management Rewards: Doing Work vs Creating an Environment

Johanna Rothman

My agile transformation clients struggle with this big question: How do we effectively reward managers? The more the organization wants or needs an agile transformation, the less the current reward structure works. Cindy wants this agile transformation to succeed. Agile Transformation Requires Management Collaboration.

article thumbnail

Minimum Requirements Documentation: A Matter of Context

Johanna Rothman

I use the guideline: If I can't write large enough on the front of the card to see, my story is too large. If the team hands off work, they're working in resource efficiency, not flow efficiency. for ways to use lifecycles other than waterfall or agile. How available is the product owner? I don't use larger cards.

Agile 68
article thumbnail

See and Resolve Team Dependencies, Part 1: Inside the Team

Johanna Rothman

Here's what happens with code review (see the image): We have a cross-functional team, Jane, Peter, and Tim, along with a product owner, Allan. Instead of treating people as individuals (resource efficiency thinking), what if you looked at the team as a harmonic whole? Jane and Peter are developers, Tim is a tester.

article thumbnail

Faster Management Decisions Can Lead to More Ease and Better Results, Part 4

Johanna Rothman

Create a yearly budget as a guideline for our specific goals, but manage that budget every week and month to manage our risks. My consulting book had the same product problems as many of my clients have: The product in our head is not what our customers need or see. I'm now able to finish the consulting book.