Remove Agile Remove Consulting Remove Feedback Loop Remove Testing
article thumbnail

Building an Effective Product Feedback Loop

The Product Guy

The objective is to receive feedback and prioritize it internally against (1) company objectives (2)customer pains/experience (3) Quarterly Product OKRs and ship out solutions. . A feedback loop is: part of a system in which some portion (or all) of the system’s output is used as input for future operations. It’s cyclical.

article thumbnail

How Agile Managers Use Uncertainty to Create Better Decisions Faster

Johanna Rothman

Strategy and Product Feedback Loops Many of my middle-management and senior leadership clients want certainty about future work. However, I don't do long consulting contracts—by design. But most of my business focuses on coaching, workshops, or consulting. Does that sound like an agile team to you?

Agile 95
Insiders

Sign Up for our Newsletter

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

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

Build Team Resilience: Shorten Feedback Loops (Part 2)

Johanna Rothman

This part is about shortening feedback loops. They had one piece of feedback: the checkin broke “unrelated” code. It was time to see their feedback loops. See Your Feedback Loops. Every project (or effort) has at least one feedback loop. Automated Tests Are About Feedback.

article thumbnail

Effective Agility: Three Suggestions to Change How You and Your Team Work, Part 2

Johanna Rothman

In Effective Agility Requires Cultural Changes: Part 1 , I said that real agile approaches require cultural change to focus on flow efficiency, where we focus on watching the work, not the people. If you and your team have been practicing real agility, you might say these ideas barely show any agility at all.

Agile 70
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: Summary

Johanna Rothman

What if you can complete a feature set in a couple of weeks, and really have it be done, build and test automation, and any user documentation or internal documentation complete? See Create Your Successful Agile Project for how to use cycle time to reduce the time you spend on estimation.). Make the stories very small and count them.