Model Building Theory: Planual 2.0, Software Development Lifecycle and ALM
In our first Model Building Theory track session titled "Return of the Planual v2.0," @rob_marshall and @Misbah, along with Master Anaplanner @Austinv, talked about the newest version of Planual (the Anaplan manual). The Planual, which debuted at CPX last year, is the first comprehensive set of documented Anaplan best practices based on actual system performance test results and Hyperblock engine optimization.
In this educational session, attendees learned about how Anaplan has made the Planual even easier to navigate and interact with on the Anaplan Community. They also heard about some of the newest best practices and thought leadership that has been recently added, and how model builders can immediately apply this guidance to your next model build.
Key Takeaways: Planual 2.0 is more user-friendly. The manual is not a "How To" document, but more of a best practice guide. The Planual helps you find a perfect balance between size and performance when creating your model.
Director, OEG, Anaplan
Lead Consultant, Wipro Limited
Austin van der Linden
Solution Architect, Anaplan
In our second Model Building Theory track session titled "Expand Your Approach With Software Development Lifecycle and ALM," @byron.mikowicz and @DavidSmith, along with Master Anaplanner Russell Gummelt, discussed how mature businesses implement Software Development Lifecycle in the Anaplan environment, blending the best of Anaplan’s inherent flexibility with decades of technology deployment rigor. The additional rigor of software development and deployment is required as your Anaplan footprint expands—especially when you start including business-critical functionality and sensitive data or plans.
Key Takeaways: Not only does ALM allow for segregation of data access between the user base, but it also allows for continued enhancements and functionality. Building your ecosystem this way enables you to simplify the build of the model (avoid having to use selective access or build out more user roles) since you can control the data seen and managed by business lines through separate workspaces and user access.