Power Platform Solution Architecture: Final go-live considerations

In this next post as part of my series on solution architecture for the Power Platform, moving towards the end of these posts, we’ll focus on some final considerations around go-live planning we’ll want to have made thoughts about. Recap Solution Architect’s role So… READ MORE [https://lowcodelewis
an illuminated text signage
Photo by Meruyert Gonullu on Pexels.com
In: Low Code Lewis Content 🚀

In this next post as part of my series on solution architecture for the Power Platform, moving towards the end of these posts, we’ll focus on some final considerations around go-live planning we’ll want to have made thoughts about.

Recap

Solution Architect’s role

So let’s recap what a solution architects role is when it comes to implementations. They’re effectively a technical and design owner for the solution implemented and its implementation, and are responsible for the success of the implementation including deployment.

Responsibilities

So to ensure for successful go live, a solution architect should ensure they have planned and delivered a go-live readiness review. This should ideally be somewhat of a templated process which parts can be followed or not followed depending on relevance, to ensure things aren’t missed for go-live that could be relevant at a high level. This should review how ready the solution is for the customer, and how ready the customer is in their organisation for the implementation.

Moving towards go-live

Occasionally there may be issues that go unresolved before the go-live of a solution. Here you should work with the customer to have them understand these and move towards a decision on the next steps for the implementation with go-live being a potential next step still if the unresolved issues aren’t of major risk.

Considerations for issues…

Commonly go-live readiness assessments and plans can miss some of these. Consider these in your go-live plans people!

  • Roll back for problematic deployments
  • Not considering users hardware
  • Real-world testing
  • Data migration prioritisation
  • Delta migration issues

Dealing with issues

So even if you’ve considered all the issues you believe are relevant ready for go-live, sometimes issues can still come up which we’ve either considered or haven’t but still pose a problem. In these scenarios it is the solution architect who is the first person people in the team can go to.

What’s up next?

So friends, in the next few and final posts in this series we’ll move on to looking at considerations for post go-live tasks and what happens with our solution next in terms of operations, support and ongoing iterative development 🚀

Written by
Lewis Baybutt
Microsoft Business Applications MVP • Power Platform Consultant • Blogger • Community Contributor • #CommunityRocks • #SharingIsCaring
Great! You’ve successfully signed up.
Welcome back! You've successfully signed in.
You've successfully subscribed to LewisDoesDev.
Your link has expired.
Success! Check your email for magic link to sign-in.
Success! Your billing info has been updated.
Your billing was not updated.