Remove Culture Remove Demo Remove Development Remove Productivity
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 104
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?

Insiders

Sign Up for our Newsletter

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

article thumbnail

Retire These Metaphors & Reframe the Discussion to be More Effective

Johanna Rothman

For years, we've used several metaphors to describe software product development: People-based metaphors, such as: Man-weeks for all the humans working on a project or a product. Demo inside the organization. In product development, is it anyone's job to make a baby at work? Worse, the less effective we are.

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 93
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 ).

article thumbnail

What Lifecycle or Agile Approach Fits Your Context? Part 3, Incremental Lifecycles

Johanna Rothman

Once the team completes that highest priority feature(s), the team can release the product. When we release, we can regroup and figure out what to do next for this product. Fork another product. (I I did this with several Lite vs Pro products using this approach.). See and demo the product as it grows.

Agile 111
article thumbnail

What Lifecycle or Agile Approach Fits Your Context? Part 6, Create Your Agile Approach

Johanna Rothman

Because your context is unique to you, your team, project, product, and culture. And, with any luck, nudges the culture in a good direction for your team, project, and product. Why Do You Want an Agile Culture for Your Product? Notice I said the culture is for this particular product.

Agile 60