views:

146

answers:

1

Has anybody here implemented a software product line approach, as defined by the SEI? How do you manage changes? How do you test? What problems have you had to deal with?

For years we've basically been trying to follow a product line approach, but I am constantly fighting Program Managers who don't want to pay for testing changes not strictly required for their program, and yet want free bug fixes. They also are very scared of changes happening to the code base that they don't need... not an unreasonable fear.

This has culminated in my getting an action item at our last PDR to explain the product line approach and why I think we should follow it. I've found softwareproductlines.com, which has a few success stories, but not enough details on how to counter the potential pitfalls.

+1  A: 

A recent SE Radio podcast had a small section discussing product line development. I believe it was the very first section.

There are also three other SE Radio podcasts that might be of interest - Episode 53: Product Line Engineering Pt. 1, Episode 58: Product Line Engineering Pt. 2, and Episode 90: Product Line Engineering Pt. 3.

I'm not sure how well these cover everything you need to know, but it will at least be a start. And perhaps you can get some pointers on where to go next from these podcasts.

Thomas Owens