Big Lever Software, Inc.

BIGLEVER NEWSLETTER: From the PLE Frontline

Getting Started with Product Line Engineering – A View from the Inside
Part 1: Introduction

Greetings from Paul Clements:

It can be difficult to decipher where to begin with your transition to product line engineering (PLE) practice. Choosing the right approach is crucial. Experience has taught us that creating a tangible, small-scale, operational pilot project is an invaluable way to plot a well-defined transition path, remove obstacles, and navigate a smooth course to PLE practice.

To this end, our customers tell us that one of the most powerful and insightful services offered by BigLever is the Getting Started Package. This highly popular program is uniquely designed to allow organizations to gain hands-on experience, using a practical and proven approach, by creating a pilot product line as the first step toward full PLE deployment. There's no better way to see powerful Second Generation PLE concepts brought to bear in your setting, on your portfolio.

Perhaps you're thinking about getting your PLE transition underway, or expanding PLE into other areas of your organization? If so, this newsletter series will give you a preview of how BigLever's getting started approach works. Regardless of your interest in our Getting Started Package, you'll get an inside view into how a growing number of companies are achieving focused, efficient, highly successful PLE transitions. For customers who have completed the Getting Started Package, we welcome your ongoing feedback regarding your experiences. We love to learn from your insights and – where appropriate – share them with others.

The heart of our approach is a three-day Getting Started Workshop, where BigLever comes to your organization and helps you build your pilot product line using Gears. I'll begin this three-part newsletter series with a short overview, so you can get a feeling for the major steps we follow in the workshop. Part 2 will explore the process in more detail, and I'll conclude the series in Part 3 with some observations.

The Getting Started Workshop is preceded by a short preparation phase that handles logistics, establishes which lifecycle assets we'll be working with and what tools you currently use to maintain them, and which stakeholders from your organization should participate.

The workshop follows a structured but flexible three-day agenda with this progression:

1. Capture the module architecture.

We work to understand the decompositional architecture of the products. What are the major "chunks" and, for each, what are its major "chunks"? It's rare that a company doesn't know this, although it might not always be written down. We elicit this because the hierarchical product line that we aim to build over the next three days will often, to a large degree, mirror that structure. For each node, we'll build a product line. For each line between two nodes, we'll connect two production lines together. Thus, where your architecture lays out a system of systems, our workshop will construct a product line of product lines.

Once we've captured that structure, it's illustrated on a whiteboard as a tree and used as a progress indicator throughout the rest of the workshop.

2. Choose a node to model.

We choose one of the leaf nodes as our starting point. Our choice might be guided by the experts in the room, or suggestions from the group about which area has rich or well understood differentiating features. Or, we might choose a node that has a particularly challenging asset associated with it (such as a complicated requirements specification). For that node, we build a production line – more on this in Part 2 of the series. The production includes the capability to configure at least one lifecycle asset – requirements, for example – that corresponds to the chosen part of the architecture.

Our goal is to complete this step by lunch on the first day.

3. Repeat until done.

We move on to other product lines in our hierarchical structure, and other assets. We wire together the individual production lines, using the Gears imported production line construct, until we have completed as much of our hierarchy as needed to illustrate and apply all of the important methodological and technological aspects of Gears and product line engineering.

Our "end game" is to create a product line for the root of our hierarchy, import all of its child product lines, actuate each product in the organization's portfolio, and show how the assets we've touched are automatically configured appropriately.

We like to achieve this by the end of the second day.

As we walk across our hierarchy, we aren't aiming for complete coverage of all the nodes in the tree, nor all the assets the organization works with, nor all of the features in any product line, nor all the potential variation points in any asset. Rather, we want to show enough in each area so that the participants have confidence that they can continue to build the models with completeness and fidelity after the workshop is complete.

The workshop concludes with a summary briefing for interested stakeholders who were not able to attend – for example, managers or other key decision-makers.  We help you construct the briefing, including a demonstration of what we accomplished. 

Coming up in Part 2: How to build a production line.

Best Regards,
Dr. Paul Clements
BigLever Software Vice President of Customer Success
pclements@biglever.com

 

Don't miss your Newsletter!
Please help us make sure that you continue to receive the BigLever Newsletter by confirming your subscription with us. This ensures that future newsletters will be successfully delivered to your Inbox and not misplaced into your junk mail or spam folder. To confirm, simply click the "confirm" link in the white bar below. After confirming, you can unsubscribe from our newsletter distribution at any time.