For the business analyst
Show why any requirement exists, and who signed it off
In AlignX a requirement is a record linked to the business case that funds it, the clauses it must satisfy and the project that delivers it. Open one and follow those links up to the objective behind it and across to the approval that signed it off.
Requirements by priority 
Done, defined up front 
Sign-off on the record
One requirement, followed on the record
Start at the objective and follow the links down: to the case, the requirement, the rules it must meet and the approval.
The questions you're asked
Three questions every analyst gets, and the record in AlignX that answers each one.
Where you work in AlignX
- Business analysisRequirements from epic to detail, with acceptance criteria, scope statements, clauses and sign-off.
- Portfolio managementThe business cases and projects your requirements serve, and the objectives behind them.
- Governance, risk and complianceThe framework and standard clauses your requirements are traced to.
What happens after you book
- A walkthrough on your questionWe take the requirement you find hardest to explain today and follow it through AlignX.
- One real reviewWe walk one business case's requirements through AlignX with you, before you commit.
Questions business analysts ask
No. Requirements don't sync to either today. Your delivery teams keep their backlog, and the requirement records which project delivers it.
See the reason behind every requirement
Book a walkthrough and bring the requirement nobody can explain any more.
Runs in your own Power Platform environment.