 |
|
 |
| |
Seminars 2008 |
|
 |
 |
 |
|
|
 |
New Principles for
Developing
Products in Half the Time |
|
Brisbane Stamford Plaza, 18th August 2008 |
|
|
| |
New Principles for developing Products in half the time |
|
| |
Whilst most companies recognise the crucial business
significance of product development, many struggle to
create a development process that gives them true
competitive advantage. Often, the company’s motivation
is intense but they lack awareness of what tools to use
and how to design individual process components.
Sometimes they search for the missing ‘best practices’
to add to their already complex process. But, such
enhancements rarely produce results because a best
practice in one situation can be a useless burden in
another. Fortunately, there is another approach to
development process design. This approach is grounded on
understanding and exploiting the specific underlying
economics of process.
This interactive and practical
programme will provide in-depth coverage of material
that focuses on the latest developments in cutting
product development cycles. Some of the techniques are
modifications of standard management approaches, others
are unique to rapid product development.
The programme
will also emphasize the quantitative and technical
dimensions of optimising development cycles - dimensions
that are too often overlooked by those who believe that
development is an art, not a science. In the
participative environment of this exclusive 1-day
programme, delegates will be able to work first-hand
with the world-wide time-to-market guru Don Reinertsen -
who is the sole presenter for the whole course. In order
to give delegates the maximum opportunity to interact
with the tutor, and get answers relevant to their
specific situations, places are strictly limited on each
course. We recommend you make your reservations quickly
in order to avoid disappointment. |
|
| |
|
|
| |
Workshop Content |
|
| |
Using Economic Analysis |
|
| |
Good business decisions can only be made when we
understand the economic impact of our actions. We will
discuss how to determine the cost of delay versus other
development objectives, and how to use this information
to assist the day-to-day management of a project.
Key Learnings |
|
| |
- Modelling development programme economics
- Quantifying the cost of delay
- Developing trade-off rules for programmes with
multiple goals
|
|
| |
Managing the Fuzzy Front End |
|
| |
Commonly half the available development cycle is
expended before development even starts. We will discuss
what causes this to happen, and the techniques that can
be used to achieve faster project starts.
Key Learnings |
|
| |
- Why the predevelopment process is so critical
- How to measure the Fuzzy Front End
- Practical approaches for shortening the
predevelopment phase
|
|
| |
Using Incremental Innovation |
|
| |
Controlling the scope of programmes is one of the more
powerful techniques for shortening cycles. This
technique reduces both risk and cycle time. We will
discuss how to do it and why it works.
Key Learnings |
|
| |
- Avoiding the mega-project trap
- The pros and cons of incremental innovation
- Prerequisites for incremental innovation
|
|
| |
Creating Effective Product Specifications |
|
| |
Good specifications are crucial, because without them
projects become unstable often requiring complete
redirection and massive delays. Yet, many product
specifications are developed through a highly sequential
process that assumes the market will stand still
throughout the development process. We will discuss
approaches to quickly developing specs that work.
Key Learnings |
|
| |
- Simplifying the product specification process
- Working with changing requirements
- The pitfalls of a specification-driven process
- Going beyond what the customer wants
|
|
| |
Using Product Architecture |
|
| |
Development cycles can be dramatically shortened by
correct system design decisions. However, these
decisions are rarely used as a tool to shorten
development cycles. We will discuss approaches to
managing product architecture that are well suited for
rapid development.
Key Learnings |
|
| |
- The role of modular product structures
- The importance of interface management
- The benefits of risk concentration
|
|
| |
Staffing And Organising For Streamlined Product
Development |
|
| |
Teams need to be selected with the right combination of
skills, the correct cross-functional mix, and certain
types of people. We will discuss approaches to team
selection that work when developing products quickly.
Key Learnings |
|
| |
- Managing part-time team members
- Co-location and its alternatives
- Alternative organisational forms
|
|
| |
Designing Fast Development Schedules |
|
| |
One of the keys to rapid development is causing tasks to
occur concurrently rather than sequentially. This should
occur both throughout the development process and within
individual stages. We will give examples of how this
overlap is achieved and what some of its negative and
positive consequences are.
Key Learnings |
|
| |
- The importance of activity overlap
- The limits of phased development
- Assessing overlapping schedules using the
control triangle
|
|
| |
Control Systems For Rapid Development |
|
| |
Rapid product development requires different control
strategies than conventional project management. Team
empowerment becomes a critical need. We will discuss
practical approaches to managing and controlling rapid
development teams.
Key Learnings |
|
| |
- Basing controls on economics
- Reducing control system delays
- Reducing low value control activities
|
|
| |
Capacity Management |
|
| |
Rapid development requires careful management of work
queues. Most companies overload their development
organisations and ignore these queues. We will discuss
the consequences of poor capacity management and the
techniques used to avoid these problems.
Key Learnings |
|
| |
- Analysing development process queues
- Techniques for controlling queues
- The fallacy of optimising efficiency
- Setting the right level of excess capacity
|
|
| |
Controlling Risk |
|
| |
Rapid product development does not inherently raise
overall project risk. Most companies use testing
strategies that are not explicitly designed to use time
efficiently. We will discuss approaches for reducing the
overall risk associated with rapid development programs.
Key Learnings |
|
| |
- Defining technical and market risk
- Smart testing strategies & test process analysis
- Accelerating life testing
|
|
| |
|
|
|
|
|
 |
|
 |
