Remove Agile Remove Consulting Remove Demo Remove Feedback Loop
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. Feedback Loops Drive Collaboration. And, with whom?

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. More often, I prefer external feedback.

Insiders

Sign Up for our Newsletter

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

article thumbnail

How to Create Partnerships Instead of Using Stakeholders

Johanna Rothman

Strategy and Product Feedback Loops About 20 years ago, I taught a project management workshop to IT people. ” For years, I explained that the more often the team or program could demo, the more the project or program could engage its stakeholders. That's why the duration of the internal feedback loops is so important.

article thumbnail

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

Johanna Rothman

Of course, there are feedback loops here, too: Notice that we expect feedback from later features back to the previous features. However, if we have “bad” feedback from the last (or interim feature), we don't have the “Kiss of Death” as we did in the serial or iterative lifecycles.

article thumbnail

Balance Innovation, Commitment, & Feedback Loops: Part 1: High Innovation Products

Johanna Rothman

Many of my clients are trying to use short feedback loops in agile approaches. The more need for product innovation and change, the shorter the feedback loops need to be. I wrote about this in Create Your Successful Agile Project.) High Need for Product Innovation and Change.

article thumbnail

What’s Wrong With Detailed Gantt Charts and How to Make Fewer Details Work for You

Johanna Rothman

I suspect their teams hide their feedback loops. When people create a high-level WBS, no one sees the feedback loops or the dependencies. The feedback loops tend to be late and create chaos in the project. That's another great way to hide feedback loops. I always see unplanned feedback loops.

article thumbnail

How WIP Insights Allow Us to Revisit Brooks’ Law About Adding People to a Team

Johanna Rothman

” It depends on how your lifecycle manages feedback loops and learning, how collaborative the team is, and how much WIP the team has. Each Lifecycle Manages Feedback Loops Differently Brooks wrote the original version of The Mythical Man-Month in 1975, based on the 1960s IBM 360 project. .”