通常,当只有一个开发人员拥有模型中的所有更改时,Anaplan中的建模很简单。但是,随着用户群的增长,用例和增强要求的次数也是如此。这意味着几个开发人员可能正在同时开发同一Anaplan模型内的功能。当多个开发人员发布了许多更改时,如何最大程度地减少对生产模型的影响?当我们遇到这一挑战时,要保持敏捷,我们必须开发一个流程,以便快速向用户释放新功能,但具有足够的控制,以最大程度地减少下游影响和破坏。钥匙是开发一个由团队采用的框架,以确保发布的任何内容都通过相关的评论和批准。在下面,我分享了与并发开发人员建模有关的过程。我们的开发框架我们的开发框架在以下图中表示。每个盒子描述了开发生命周期中的不同模型。总而言之,开发人员可以自由地更改开发模型,并将其同步到UAT模型进行测试。 Only UAT and CAB-approved changes are then added into the pre-production mode to be synced to the production model. It is important to re-develop these changes in a pre-prod as UAT models contain a lot of unfinalized development, and cannot be synced directly to prod. DEV = Development Model (standard, offline model) Used for development of functionality, structural changes, and unit testing, and generally contained less production data to minimize model size. Once a developer was happy with the changes, this would be synced via ALM to the UAT model. UAT = User Acceptance Testing Model (deployed, online model) UAT models are generally a more recent copy of the production model so that changes were tested with the most relevant production data. Our UAT model was linked up with the testing environment of other systems to easily test downstream system impact. Once in the UAT model, the changes would be peer-reviewed by another developer. This is a technical review to check if changes have been developed most efficiently and to model standards. After the change has passed tech review, it goes to the end user for testing and sign-off. All changes that have been UAT approved and are expected to have downstream impacts will go to the Change Advisory Board (CAB), where system owners evaluate and approve the expected impacts of the change. PRE-PROD = Pre-production Model (standard, offline model) The pre-prod model is a copy of the production model two weeks before the scheduled deployment date. Developers carefully re-develop changes into pre-prod, complete unit tests and production data variance checks to ensure that the outcome and impacts of the change is expected. It also gives a chance for developers to test against the most up-to-date production data. PROD = Production Model (deployed, online model) During the deployment window, changes from pre-prod will be synced to prod via ALM with variance checks and any production data changes. End users will need to do a Production Verification Test (PVT) following deployment to check that the change is working as expected in prod. This framework does require double development, but it works for our organization and allows us to deliver new functionality quickly. Have you had challenges developing in Anaplan with larger teams? Add your tips in the comment section below! About the author: Julie Le Julie Le is a Certified Master Analanner and has over five years of experience in Anaplan involving large-scale implementations and teams.
... 查看更多