article thumbnail

Large Features and Long Deadlines Mean You Have a Gantt Chart, Not a Roadmap

Johanna Rothman

Demo on a regular cadence. Which means you can demo at will. Demo Early and Often. If you want to move your managers from “we need it all” thinking to “how little” thinking, demo every single time you release a slice. Record the demo. The demo is part of your data.

Agile 143
article thumbnail

The Business Plan Is Alive And Well But It May Not Be What You Think

Steve Shu Consulting

Often need a mix of instruments here (Powerpoint & Word docs, napkin drawings, demo), depending on the team, industry, and phase of product development (e.g., Business Development General Management Intrapreneurship Management Consulting Sales And Marketing Ventures & Entrepreneurship Business Plan Entrepreneurship Strategy'

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

Tip 1: Start and Maintain a Cross-Functional Team for the Entire Project I still see many supposedly agile “teams,” where the project has a “development team” and a “testing team.” ” Even if the developers and testers are one team, I still see UX or UI teams. But that's the value of the demo.

Agile 71
article thumbnail

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

Johanna Rothman

In addition, each component team worked on any number of products, both development and support, for any given iteration. However, software product development is not construction. Software product development requires feedback loops and learning. Over months, they stopped demoing anything. And remotely!)

Agile 85
article thumbnail

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

Johanna Rothman

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. As part of the product development, they spin off security and performance teams. However, their tools approach differs from their product development approaches.

Agile 105
article thumbnail

What Lifecycle or Agile Approach Fits Your Context? Part 2, Iterative Lifecycles

Johanna Rothman

Barry Boehm developed the spiral model. We develop test plans early. In Evolutionary Prototyping, we develop the initial concept—not all the requirements. Once our customers saw demos, they wanted to change things. We need designers, testers, anyone aside from developers to develop the prototypes.

Agile 117
article thumbnail

How and When to Use Timeboxes, Iterations, and Sprints to be Most Effective

Johanna Rothman

Not the thinking and learning that go into the deliverables where you end up with something demo-able, if not usable.” However, they don't deliver value, have team-based planning, a review/demo, or a retrospective. We used internal demos because the cost to release was so high. Software product development is learning.

Agile 90