Module Progression Plan or MPP for short is a studiocrafted self made acronym. It applies to the idea and principles of updates to a web site or web application.
There are a number of criteria before a MPP can be implemented and each MPP is treated as new with additions and scopes.
Version numbers are fine but when you need to articulate each update more for maintaining and evolving your project, MPPs can play a vital role.
How do you define a MPP?
Break your project into components or "modules" and describe each aspect. For example a WordPress theme can have many modules from custom actions or filter functions, to initialisation or plain view files. The view file is relatively simple for example as you can associate a style sheet with that which then becomes part of the module.
Within each module you need to identify if it is updatable and can be progressed, and if so how do you approach this. If not, you do need an alternative solution. For example if you have a custom action method for WordPress you need to think is this updatable within the next version update? If so how is the update applied? This will later be described in your plan.
With any module and its progression you should now see parity. You should have a plan for incremental smaller MPPs and also for larger. The plan can include the deployment technique, code dependencies and changes for example.
Overall MPPs are great, they're slightly more than 'change logs' and usually require documentation. It creates a clear picture and is nice to have when there is time available.
If you're looking to save money over the long term with a larger online development that needs a maintenance and build plan please do contact me for a discussion or send your project details via the advanced project form.