Skip to main content

Demonstration-Based Agile (DBA)

Adopting agile development processes means adopting key practices, usually some combination of the following:
  1. Develop in short iterations.
  2. Release frequently.
  3. Write tests first.
  4. Communicate frequently.
Organizations moving towards agile product development typically face major hurdles as many people are entrenched in old waterfall thinking. How can you most effectively move towards agile in such an environment?

Forget about Scrum, XP, and all the buzz words. Let me introduce a new buzz word.

Start with demonstration-based agile (DBA) on a small scale. With demonstration-based agile, you insist on only one thing:

Regular Demos. The development staff demos the product to the product manager and other members of the team at the end of every week (or some other short period).
It's a lot easier for a team to agree to regular demos than it is to short iterations or frequent releases. Yet regular demos aren't much different. The team must iterate on developing the product and must have something to "release" (as a demo) frequently. Regular demos also stimulate frequent communication. Finally, the team sort of plans "tests" by defining in advance what to expect from each demo.

Some curmudgeons may resist the idea of regular demos, but for many the concept is easier to swallow than all of the agile practices that fall out of it.

Comments

Scheevel said…
I "introduced" scrum to our local dot-net user group last month. Since so few had any Agile experience I didn't know where to start...so I started at the beginning. I started with the Toyota Production System and how Lean Manufacturing was born, from which Lean Software derived giving birth to Agile principles which Scrum implements. Out of all those concepts the most valuable take-away was "short iterations" and "demos at the end of sprint." I think you've got a great idea here. Easy to implement and simple to visualize benefit.
Unknown said…
Simple yet powerful. Thanks for sharing.

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware

Is Customer Development Pseudoscience?

The “Science” of Lean Startup Lean startup practitioners embrace the scientific method, seeking the "truth" about what business model and strategy will lead to product success. We do so by: Formulating hypotheses Crafting and running experiments to test them Learning from the experiments Iteratively feeding our learnings back into revised hypotheses Sounds pretty scientific, at least in spirit, doesn't it? Yet this process actually neglects a key ingredient in the scientists' mode of operation. To identify what’s missing, let’s examine “customer development”. Customer Development Steve Blank is one of the pioneers of the lean startup movement. He introduced into the lean startup lexicon the term “customer development”. Customer development consists of sessions and interactions with customers to test hypotheses. For example, a product manager might interview a prospect, asking if she agrees with the product manager’s hypotheses about the problem