Power Platform Solution Architecture: Finalising requirements

In this next post on solution architecture for the Power Platform, I’d going to wrap things up around the requirements gathering process by discussing considerations for finalising requirements we’ve captured, refined and categorised. Check out the posts below if you haven’t already read them…… REA
crop faceless men shaking hands in studio
Photo by Armin Rimoldi on Pexels.com
In: Low Code Lewis Content 🚀

In this next post on solution architecture for the Power Platform, I’d going to wrap things up around the requirements gathering process by discussing considerations for finalising requirements we’ve captured, refined and categorised. Check out the posts below if you haven’t already read them…

Wrapping up

So now let’s just have a quick think about the things we should be considering before considering requirements as final and getting finalised sign off from the customer in perhaps say a review meeting…

You might want to consider some of the following things…

Detail

Are your requirements detailed enough? Do they point to the success and goal statements you set out in that initial proposal document at the start of the engagement that the customer signed off? Are they good enough to have been able to break down tasks from for estimating?

Under estimated tasks?

So friends, DO NOT DO THIS ONE please… It’s so important to estimate tasks correctly and provide adequate amount of time on tasks to ensure they can be implemented within the scope and plan of a project. Review the estimates that have been put against work items either at the user story or task level and ensure these fit what you’re trying to do.

Prioritised?

So friends, as we discussed in a previous post on requirements capturing, make sure these things get prioritised so your consultants and developers have something they’re working against and know what is important on the board! This should not be a pick and choose game 🙂

Over the scope?

Before finalising requirements and signing off on the project plan for your implementation its imperative that you ensure it fits within the scope defined and agreed upon by the customer. If it doesn’t, it may be time to re-think a thing or two with the customer, or head back to your sales and pre-sales team to figure out what was a little underestimated on or missed in that stage…

And much more…

So people, these are just a few of the things you might want to consider before finalising requirements. It’s important to ensure you’re happy with requirements and that all stakeholders are happy before proceeding with implementation. This includes your consultants and delivery development resources so include them on this stuff! Then once you’re happy, you can move into the next stage of your engagement! 🚀

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.