Remove Agile Remove Consulting Remove Feedback Loop Remove Feedback Software
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. Just like software.) Sometimes, once a week.

article thumbnail

Build Team Resilience: Shorten Feedback Loops (Part 2)

Johanna Rothman

This part is about shortening feedback loops. Brief description of the problem at a recent client: Person A checked in code that broke an “unrelated” part of the system. They had one piece of feedback: the checkin broke “unrelated” code. It was time to see their feedback loops.

Insiders

Sign Up for our Newsletter

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

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

Why We Continue Our Quest for Silver Bullets

Johanna Rothman

For years, managers have been trying to find ways to make software product development faster and easier. I never had to experience CASE tools in the 90s. “Agile” as a way to do much more work in much less time. (NO! I'm a huge fan of tools that help me do my job. As an industry, we've tried tons of things.

article thumbnail

Balance Innovation, Commitment, & Feedback Loops: Part 3: Low Innovation Products

Johanna Rothman

Your planning feedback loops can be longer. I've seen this occur in some of these circumstances: A port from one platform to another. The technical risks are not in the knowing, but in how things work or will work on the new platform. You don't need a lot of feedback to change the requirements.

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. That's why there's feedback.

article thumbnail

Combining DevOps and Agile Transformations to Achieve Business Outcomes

Agile Velocity

Did you know you can maximize your chances of achieving desired business outcomes by combining DevOps with an Agile transformation? When you hear “Business Outcomes,” “DevOps,” and/or Agile transformation” – what comes to mind? They are key inputs for your business and technology discussions around WHAT to work on.