Change Management Process

MangoApps product management & our customers have a lot of ideas and requests for new MangoApps functionality. So at MangoApps we follow the following change management process to effectively focus and prioritise enhancements that drive user adoption and have the biggest impact in your organization.

Here are the 12 steps process we follow at MangoApps to effectivity execute change management:

Block_Diagram_02_2

  1. Check Alignment with Product Roadmap
    • In this step the MangoApps product management & executive team evaluates which change requests & features will be implemented based on their alignment with the business plan and the overall level of effort required.
    • Here an executive champion for the feature/change is also decided to help guide & ensure effectiveness through-out the change management process.
  2. Do Feature/Change Requirements & Communication Plan
    • In this step the feature/change wire-frames, mockups and functional requirements are done. These are reviewed internally with leads and with customers collecting there input.
    • In this step the product management team also comes up with the communication plans to help define the message to your users to drive adoption.
  3. Define Feature/Change Scope & Impact
    • Once we have the feature/change defined, this step is used to determine the scope and impact of the change to the product.
    • The feature/change is also reviewed for impact across different functional areas and it is scoped out with specific use cases in mind.
  4. Prioritise it in a Major vs Minor Release
    • Incorporating every enhancement request and idea is just not feasible. That’s why defining the overall impact is important in helping to decide which enhancements to
      implement, which to target for a later date, and which to reject.
    • The feature/change requests that get approved are scheduled for a minor or major release and added to the project release wiki which is then used to track the next steps, progress, and status.
  5. Build & Test
    • In this step the weekly sprints are defined, the Open APIs specifications are done and the overall software design & development happens.
    • Design considerations & optimisations to ensure performance & security of the feature/change across all platforms – web, mobile & native clients is taken into account at this step.
    • Test setups and scenarios are built for functional, performance & security testing.
    • Automation test scripts are updated.
  6. Release Feature/Change for Quality Assurance (QA) & Security Review
    • Once the feature is build it is internally released for quality & security tests to the QA team.
    • In this step all issues, bugs reported are fixed and compliance with quality guidelines is met.
  7. Deploy it to MangoApps Staging & Internally Use It
    • In this step the software feature/change is deployed on the MangoApps staging environment.
    • We at MangoApps use the staging environment internally and this allows everyone in the company to test and experience the new features/changes before deploying them to your production environments. This step is critical to a smooth and surprise-free deployment.
  8. Collect User Input & Make Adjustments/Improvements
    • Private-cloud & on-premise customers also get to see a preview of the upcoming major release in the staging environment and provide early feedback to help make low-effort and high-value adjustments to the feature/change, answer questions like when they’ll happen, how users will be trained and what’s in it for me?
    • Here we also take advantage of the staging environment to provide a real-work training environment to our private & on-premise customers which they can use to set end-user expectations of the changes that are coming.
  9. Build Documentation, Support Material & Release Notes
    • In this step the documentation & product management teams work to create help articles, blog posts and how it works articles.
    • Documentation & help posts for existing modules that are impacted by the change are also updated to ensure that our customers get up-to date and accurate information.
    • Release Notes are shared with customers generally 2 weeks in advance from the production release date.
  10. Deploy to Shared Cloud Across 6 World-Wide Data Centres
    • Once the new release is ready and the training/documentation materials are in place, it’s time to push the new release to the production data-centres world-wide.
    • Mobile clients are submitted to their respective app stores.
    • Automation test suites are run all data centers to ensure a full sanity of the new release.
  11. Deploy to Private & On-Premise Customers
    • This step starts about 2 weeks after the shared clouds production deployments are completed.
    • More details on this step are listed here 
  12. Follow up & Support
    • In this step we measure the success of the new release and identify areas that can be enhanced further in the future.
    • After our customers deploy, reconnect with their power users or survey a broader base of their user community we take feedback to start the cycle again.
    • Here we encourage you to share specific examples of business process improvements that resulted from the change in your organization. You can share this on the dedicated support projects you are part of or directly with your account success manager and help further accelerate the innovation & user adoption in future releases of MangoApps.