In this final post as part of my series on solution architecture for the Power Platform, we’ll look specifically at considerations for handover to a CoE team or continuous development team.
If you didn’t check out the previous post, check it out now before continuing!
Now let’s jump into some considerations for handover to a continuous development team! 🚀
Have the correct people in place
Prior to actually actioning anything with people or getting a continuous development team familiar with our implementation we need to make sure we have the appropriate resources in place which have the technical understanding of components we have used in the solution. So, if a solution uses C# plugins, we need to have people in support potentially who understand C#, and these consultants should potentially act as escalations to those working in support who may have skills gaps in more technical areas.
So now, the first thing we should be doing to kick off a movement into a new development team who will handle continuous development for a solution after go-live is demonstration, education and workshopping sessions with the new team on the solution in place.
You should consider the following during workshopping sessions…
- Solution architect lead/ownership and transferring this role if appropriate
- High level architecture run through of the solution
- Demonstration of the functional capabilities (behavioural requirements)
- Demonstration of some of the configuration and logic implementation
- Code base and repository
- Environment strategy
- ALM strategy
- More… (think the things we have visited in this series on solution architecture! 😉)
So guess what… chances are you’re probably not going to get every question answered and all knowledge transferred within your workshopping sessions…. I’m pretty certain of this…
Consider the need for an extended handover period with a series of cadence based sessions in place to review the status of moving into continuous improvement and how it is going for the first short period, including outstanding questions.
Solution architect ownership
So as a solution architect if you are working in a consultancy you are most likely aligned to a department, which commonly can be Professional Services or Managed Services teams. This may mean that as the solution moves into support and continuous development it will change ownership from PS to MS. This will most likely mean there is a transfer in ownership from the original solution architect to a Managed Services aligned architect. You should consider what is needed in this handover and ensure it is conducted with great communication! 💬
What’s coming up?
So guess what friends… 👀 This will be the last Power Platform or technical / strategy type post in #365PostsIn365Days in 2023 which is now almost finished! Stay tuned in the next few days for some summaries on the content throughout this year including category, series, and solution build spotlights before a final complete overview and round up! 🆙 💖