Power Platform Project Governance

In this next post within my series on solution architecture for working with Power Platform, we’ll focus on project governance and a solution architects role in ensuring a project is correctly governed end-to-end. We’ll look at various elements and things to consider as part… READ MORE [https://low
judge signing on the papers
Photo by EKATERINA BOLOVTSOVA on Pexels.com
In: Low Code Lewis Content 🚀

In this next post within my series on solution architecture for working with Power Platform, we’ll focus on project governance and a solution architects role in ensuring a project is correctly governed end-to-end. We’ll look at various elements and things to consider as part of the governance of a project to deliver a Power Platform solution and hopefully this will answer some questions around where the role of a solution architect sits when it comes to project governance! 🚀

Why is governance needed?

So when it comes to the execution of a project, there needs to be an element of ‘governance’ wrapped around that project. This isn’t project management as such, or the focus on actual execution of tasks within the project, but is more focused on things like changes in the scope of the project, how we actually handle certain things, ensuring we don’t over-promise and create large expectations and much more.

Project governance should be put in place for any project in order to at the very least be able to assess any risks posed to delivery, any issues that arise, and any scope changes to what is supposed to be being delivered.

What is project governance?

So when it comes to governing a delivery project, we’re aiming to ensure we don’t miss any gaps in addressing the needs we just talked about… the things like assessing risks, issues, changes and more. The actual element of implementing governance around a project looks at ‘how‘ we approach these different things.

To implement project governance, and be successful in governing a project, a solution architect should be able to answer questions on…

  • How we address risks – What is the process?
  • How we approach issues
  • How we deal with difficult conversations such as requirements negotiation (don’t be a “no” person!)
  • How we approach design and scope changes
  • How do we handle resourcing and smooth delivery effectively
  • What are the processes for any of these things?
  • How do we ensure the things above are logged and audited in the event that we need to report this to the customer or our own colleagues?
  • The list goes on…

The solution architects role

Now, what I’m not saying here is the solution architect is the sole person responsible for providing all forms of governance and governance definition for projects the organisation delivers, or that the architect is assigned to.

There are a few places where the solution architect is imperative in being involved in this element of project delivery though…

  • Governance definition – Ensuring governance aligns with the needs of working with the Power Platform
  • Being the communicator – Often a solution architect is the person the customer has the most contact with and is between other team members such as consultants and delivery engineers / developers, and so should be responsible for communicating when handling things like issues, risks and changes. This can also be done in co-ordination with roles like project managers.
  • Be the resolution to difficult issues and news
  • Help parties come to a common resolution and idea

What’s coming up?

So people, there’s lots to come in this series on solution architecture! So stay tuned for all sorts of fun things where in next posts we’ll start to look at some methods for keeping projects on track, implementing good project governance, and playing the role of a solution architect within the realm of project governance! 🧑‍⚖️

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.