Create enough features in the first release to make it possible to migrate one product from the existing system to the new one. Later releases then grow the number of products that can be migrated.
- If there is a large variation in features that are needed for different products this pattern reduces MRP significantly
- Internal users will often be organized around products. That makes it easier to achieve a situation where few users have to work with both systems in parallel.
- This pattern does not work well if there are strong interdependencies between products. This is the case if one customer typically interacts with products of more than one type
- Users will be annoyed if they have to look for a product in both systems. This can be mitigated by using the Umbrella pattern or the Facilitate switching principle.
- If migration of one product is complex, MRP can become too large.