Remove Culture Remove Demo Remove Efficiency
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. That creates distrust and an anti-agile culture. And all those ways require we change the culture from that of resource-efficiency thinking to flow-efficiency thinking. That's a cultural change.

Agile 88
article thumbnail

How Interview Questions Reveal the True Organizational Assumptions & Culture, Part 5

Johanna Rothman

Instead, I see assumptions that reveal a divide-and-conquer, and possibly a command-and-control culture, not an agile culture. Individual work does not encourage flow efficiency thinking. That's because, in an agile culture, the team members can each exert their leadership so they can succeed as a “ harmonic whole.”

Insiders

Sign Up for our Newsletter

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

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. This can work well if you demo something at least monthly once you start writing code and tests. That's fine.

Agile 71
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. What about those cultural changes? Where the organization rewards resource efficiency, not flow efficiency.)

Agile 81
article thumbnail

How to Create Partnerships Instead of Using Stakeholders

Johanna Rothman

” For years, I explained that the more often the team or program could demo, the more the project or program could engage its stakeholders. See Customers, Internal Delivery, And Trust for a recent post about demos and trust.) The more frequently you can demo, the more your partners can trust you to deliver something.

How To 125
article thumbnail

Different Cultures See Deadlines Differently

Harvard Business

We all have the tendency to look at other cultures through the lens of our own. In my experience working and teaching across cultures, I’ve noticed one important area where this frequently causes conflicts: deadlines. Western cultures tend to view time as linear , with a definitive beginning and end. Pamela Hinds.

Culture 44
article thumbnail

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

Johanna Rothman

Because the “teams” couldn't deliver something small, they didn't demo very often. Over months, they stopped demoing anything. Because no one saw any demos, management couldn't trust the teams to deliver. Then, the managers asked the teams to demo something every week instead of measuring schedule variance.

Agile 85