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. Worse, these people and teams don't feel any satisfaction with their products. That's a cultural change. That's why I say agility requires cultural changes.

Agile 88
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
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

Agile Project Manager, Scrum Master, or Product Owner?

Johanna Rothman

We had (and still have) too many products to keep the same teams on them for a long time. For programs, the team stayed together and moved to a different feature set/internal product until the program finished. We could move to a new product and/or a new team. My job was to smooth the way for people to deliver products.

Agile 60
article thumbnail

Agile Approaches Offer Strategic Advantage; Agile Tools are Tactics, Part 2

Johanna Rothman

Example 1: Startup/Small Organization with Few Products. They offer their product in two versions: Pro and Lite. The first was not waiting for the end of an iteration to demo or release. They demo'd every week on Wednesday mornings and then they released after the demo. Let's start with a couple of examples. Others mob.

Agile 105
article thumbnail

How WIP Insights Allow Us to Revisit Brooks’ Law About Adding People to a Team

Johanna Rothman

The first is that Brooks strongly suggested the idea of a “surgical team” That hierarchical team was a feature- or product-based team. Ten people, seven of them professionals, are at work on the problem, but the system is the product of one mind–or at most two, acting uno animo.”

Agile 94
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 Product Orientation Requires Technical Excellence ).