Articles

High Tech Product Development in Agile Mode – Part 1

High-tech product development in agile mode makes concurrent engineering fully possible even with large cross-functional teams.

The value delivered to the customer, enabled by digital models, pretotypes extends the value of working software, expressed by the agile manifesto.

Value delivered to the customer drives teams beyond releasing the working product.

This is the story of what was done in a high-tech company that develops radar equipment.

The special features of high-tech product development

The development of a high-tech product is characterized by the following significant elements:

  • There is strong integration between Hardware and Software
  • The software is at different levels such as Firmware, SW CPU and SW PC 
  • Products often work under extreme operating conditions 
  • Many skills are required
  • It is necessary to break down the project into the hardware part and the software part by taking care of their integration
  • A lot of experimentation is needed given the interaction between hardware and software.

The critical issues of high-tech product development

There are the following critical development factors:

  • Concurrent engineering is very difficult to achieve in sequential process
  • Can’t wait for requirements to be completed before starting any development due to short lead time
  • It is difficult to make integrations between design, production and purchasing.
  • Experimentation is done with breadboards, mockups, structural models, or simulators
  • People are focused on domain skills and local optimum

The approaches required for the development of physical products

High-tech product development as with all physical products requires 2 integrated approaches:

  1. The development of alternative solutions to compare with each other

    1. The same functionality can be realized in different ways each with advantages and disadvantages.

  2. Concurrent design or concurrent engineering

    1. Different departments work simultaneously on different aspects and/or stages of product development.
    2. The alternative solutions that are designed and/or developed are analyzed and evaluated from the different perspectives that each department brings.

The high-tech product development with agility

Agile development proceeds by small steps or iterations of process. 

Product increments and changes (product iterations) are developed at each step

These increments and changes may not be functioning elements of the product.

Indeed, it should be remembered that it brings value to the customer or stakeholders anything that allows them to direct development as: 

  • Product forerunners or pretotypes
  • Simulations and digital models
  • Product updates

Agile development that proceeds in steps with increments and product changes effectively encapsulates concurrent engineering:

  • At the end of each step of development, the work done is presented (Sprint Review)
  • In the following next step planning meeting (sprint planning), the items that have emerged are discussed and planned if they need to be developed.
  • Sprint Review and Sprint Planning events are really operational design review meetings

This provides a process that continuously carries out the design review meetings that are critical to concurrent engineering.

The Agile approach, allows development to begin with still incomplete requirements that themselves become deliverables. 

This allows requirements to be refined according to what emerges in the early stages of product development. 

In this way, product development becomes technically feasible and sustainable for the customer, the company, and the team.

These are elements of the development process that I experienced with teams at a company in Rome that builds high-tech radar equipment.

The process of developing high-tech products has many other implications, both technical and human, which we are addressing with management and teams. 

I like to mention in particular:

  • The compatibility of agility with medium- and long-term planning typical of high-tech products 
  • The impact of the agile approach on the work of development teams in offices and labs 

The human aspect is the most relevant, and I will return to these topics with a  more article.

Leave a Reply

Your email address will not be published. Required fields are marked *

Other insights into Agile product development that you might be interested in

Discovery & Construction

Product Discovery Product Construction

I talk to you about innovative product development, inspired by the book “
Inspired: How to Create Tech Products Customers Love ” by Marty Kagan. There is a big difference between leading companies and others in the product creation process. The key concept is “product discovery”: exploring and testing ideas before investing heavily. This is integrated with “product delivery” or “construction.” The author of the book stresses the importance of prototypes, which in HW I prefer to call “pretotypes,” and tools such as Lean Canvas and Story Mapping. There is too much focus on Scrum, when instead it is important to create truly useful functionality. The book is recommended for those who want to truly innovate.

Read More "

The pretypes i.e., the forerunners of the product

Pretypes are quick and inexpensive demonstrators to test key ideas before creating complete prototypes. I am talking about an automated palletizing project where we made a pretotype of the most critical component, which was the tray, in just 15 days. We saved several months and significant investment. This pretotype allowed us to validate the best materials with which to build the final tray.

Read More "

What is the Agile Factory – StoryTime Interview

In this interview with Antonio Panareo of Story Time, we talked about the agile innovation factory that I established during my last corporate experience. Establishing this agile factory was a real gamble and I talk about the experience I had with my teams.

Read More "