How are you going to develop your models? Who is going to develop the models? Do you need to segregate responsibilities for development, test and production models?
Fortunately, Anaplan’s Application Lifecycle Management (ALM) feature provides a framework for the answers to these valuable questions.
ALM is the process of managing the development lifecycle of your applications (aka models) from initial design to deployment to end users. It can be broadly categorized into five stages:
Design an application that meets your business requirements. You will create user stories, schema diagrams, modules, data flows, wireframes, and prototypes.
In the Build stage, you create the lists and modules that make up the application. At this stage, use sanitized data; don't be concerned about loading production data into your application.
Test the application for performance and user acceptance. To isolate testing from production, utilize a separate test workspace containing test models and use mock data or a subset of sanitized production data.
Deployment introduces the application to end users with full production data. Generally, your production application will be separate from your development and test applications. Importing production data from an external system or data hub might be part of your deployment process.
Post-deployment, as you build out an application to address further requirements, the development lifecycle can be repeated as often as necessary. Post-deployment development might include:
Fixes to resolve issues, either discovered in production or deferred in the build or test stage.
Additional functionality provided by new dashboards, modules, lists, or formulas.
New models to support additional business requirements.
We know that change is inevitable. Here are some tips to follow during deployment:
Create a structure for change
Establish Central Responsibilities
Establish Functional Representatives in Business
Designate a Central Solutions Architect
Establish a Process for Changing / Creating a New Model
Consider segregation of duties for Dev and Prod models/workspaces
Create a change control process
Establish process for collecting change requests
Clarify requirements with end users
Calculate development estimates (aka level of effort)
Define a triage process to prioritize developments
Refer to Business Owner for approval
Agree on development or sprint plan
Define a communication plan to the end users
If a data hub (see above) is used, consider the following:
Set Imported hierarchies as "Production lists"
Set up imports from live data hub into development model to eliminate need for import source remapping on deployment
Use a development or production filter for the above to minimize the size of the development model lists