Remove Agile Remove Demo Remove Development Remove Productivity
article thumbnail

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

Johanna Rothman

So when does it make sense to customize your agile approach to gain a strategic advantage? Example 1: Startup/Small Organization with Few Products. They offer their product in two versions: Pro and Lite. They want an agile approach, so they started with Scrum. Some of the regular product teams figured out one-day stories.

Agile 104
article thumbnail

Unemployed Agilists: How to Increase Your Value to Get a Great Job, Part 3

Johanna Rothman

That part discusses why managers see agile coaches and Scrum Masters as staff positions, not line jobs. I assume you have some sort of functional product development expertise. If not, why are you in technical product development? This post is about your deep domain expertise, first in product, then in agility.

Agile 81
Insiders

Sign Up for our Newsletter

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

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. I focused on the actual development costs. Agile software teams are cross-functional and interdependent. Many agile software teams have somewhere between four and seven people.

Agile 52
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.). Opportunities for More Agility.

Agile 112
article thumbnail

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

Johanna Rothman

I discussed the origins of the agile approaches in Part 5. In this post, I'll discuss how you can create an agile approach that fits your context. Why should you create your own agile approach? Because your context is unique to you, your team, project, product, and culture. Remember, an agile approach starts with a team.

Agile 60
article thumbnail

Capitalizing Software During an Agile Transformation

Johanna Rothman

They've started to use agile approaches. There's a great introduction article, Capitalization of software development costs.). Capitalization for Agile Work. Let me walk you through an example of a 5-person agile team. Let's assume everyone works together, on one project (product, if you prefer). Why Capitalize?

article thumbnail

Visualize Work to Reduce Agile Meetings

Johanna Rothman

Many new-to-agile teams use some form of iteration-based agile approach. Back in Time You Spend in Agile Meetings (near the bottom of the post), I enumerated all the possible meetings. I mentioned how you could integrate the demo work into an iteration if you create a column for the demo.

Agile 51