Shobhit MathurDoctoral Student| IITB-Monash Research AcademyMelbourne, Victoria, Australia
Dear members,
I am looking for examples of requirement change requests which are subtractive in nature, i.e., removal of already developed features and functions from the project output during project execution. Any examples from the construction or software development industry would be helpful. Thanks Saving Changes...
There are 2 cases which I see frequently in commercial aircraft.
We try to design what is called a "provisioned baseline" where the base model anticipates many variable features that can be plug-and-play later. Customers sometimes start out asking for a lot of optional features, but then start to pare them back once the cost starts growing beyond what they can accept. We may have most or all of the design done, but some have to be cut from the plan and we put the engineering on the shelf.
Another situation is where we provide a feature as part of the baseline that the customer doesn't want people using. A software example might be Windows Enterprise where the typical games are not included. A similar example in passenger jets is the electrical "shaver outlet" in the lavatory. Although originally a standard feature in the 1st class area, we had to create new designs without them so people don't spend most of the flight in there with their laptop or charging their cell phone. Saving Changes...
MORERE ALEXANDRER&D project manager | IDEMIAParis, Ile De France, France
I can raised another example of subtractive change request related to requirement.
During a software development, one feature did not demonstrate enough level of performance (internal assessment/expert judgement).
So we request to remove this feature from the initial scope to the customer representative (hopefully not an high value feature =it was accepted).
Then I updated the baseline scope.
Finally I updated the baseline cost because costs was reduced (yes, it can happen also this way!) Saving Changes...
Community Champion
