Remove Agile Remove Consulting Remove Customer Experience Remove Feedback Loop
article thumbnail

Building an Effective Product Feedback Loop

The Product Guy

Ruthless prioritization translates to product teams spending time building the right thing at the right time. 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. . And per customer?

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. A focus on a “standard” agile approach, regardless of how much agility is in that approach.

Insiders

Sign Up for our Newsletter

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

Trending Sources

article thumbnail

Multiple Short Feedback Loops Support Innovation

Johanna Rothman

Strategy and Product Feedback Loops. In the team, to solve the problems in a way that will attract users/buyers/customers. In the team, to solve the problems in a way that will attract users/buyers/customers. Don't want to spend time forecasting an entire release because they know they will be wrong.

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. Sometimes, multiple times a day. Sometimes, once a week.

article thumbnail

Unemployed Agilists: Review the Hype Cycle & Your Agility to Help You Manage Future Job Changes, Part 4

Johanna Rothman

I started this series by discussing why managers didn't perceive the value of agile coaches and Scrum Masters in Part 1, resulting in layoffs.) That's why I then asked people to review their product-oriented domain expertise and agile-focused domain expertise in Part 3. Especially, Agile is Not a Silver Bullet.

article thumbnail

Effective Agility: Three Ways to Change Your Team’s Project Culture, Part 3

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 watch the flow of the work , not the people doing tasks. Can you create an agile culture for your team even if you can't change how the organization works? 1,2 and so on.

Agile 80
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. Oh, the bad old days.).