Remove Demo Remove Efficiency Remove Productivity
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. Their products and services did not ship outside the building—their products and services enabled the organization to make money. See Customers, Internal Delivery, And Trust for a recent post about demos and trust.)

How To 125
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. The goal to release the product. When the team can focus on the product, as a cross-functional team, they can create some agility.

Agile 71
Insiders

Sign Up for our Newsletter

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

article thumbnail

Designing an Organization for a Product Approach, Part 2

Johanna Rothman

In this part, I’ll discuss an option for a product-oriented organization. Consider a Product-Oriented Organization. Instead of organizing by function, consider a product-oriented organization. Again, I am not saying this is the only way a product organization would look, but this is a possibility. What do you do?

article thumbnail

Effective Agility Requires Cultural Changes: Part 1

Johanna Rothman

When I work with these teams or their managers, I realize they're not demoing or retrospecting on a regular basis. Worse, these people and teams don't feel any satisfaction with their products. And all those ways require we change the culture from that of resource-efficiency thinking to flow-efficiency thinking.

Agile 88
article thumbnail

Five Tips for Managers of Newly Dispersed Teams

Johanna Rothman

If you're creating products of any kind—especially software products—you've got a team sport. Successful software product development is about how well the team learns together. The better the team learns together, the better the product is. See the Flow Efficiency series.) Don't decide for anyone.

article thumbnail

With Agile Approaches, No Need to “Meet” or “Enforce” Deadlines

Johanna Rothman

I asked Brad these questions: Do you have product or feature teams that are cross-functional and can release alone? ( Component teams create interdependencies and take much more time to finish work.). Does each team focus on just one product at a time? Schedule Variance Does Not Make Sense for Software Products.

Agile 85
article thumbnail

Possible Test for Splitting Stories and Valuable Minimums

Johanna Rothman

No one wants to demo this work, because everyone thinks the demo will wander all over the place. Worse, no one wants to demo, because they can't see the value for any user. Use the Demo to Guide Sizing. Use the Demo to Guide Sizing. Focus on the flow of work through the team, flow efficiency thinking.