Guide section 24 of 31
Definition of Ready for Power BI Page Development
A page is ready when the team can implement and test it without unresolved design or data assumptions.
Business
- Primary business question/decision is agreed.
- Target users and usage frequency are understood.
- Requirements have been validated with the relevant business stakeholders.
- Comparison basis, thresholds, terminology and expected action are agreed.
UX / Design
- Figma page is complete at the agreed level of fidelity.
- Page archetype/template is selected.
- Information hierarchy and component mapping are explicit.
- Native Power BI component mapping is known.
- Custom visuals, if any, are explicitly approved.
- Interactions, drill, drillthrough, tooltip, navigation and reset are defined.
- Filter defaults and active-state presentation are defined.
- Empty/no-data/selected states are documented where relevant.
- Accessibility is checked.
- Mobile/embed/print requirements are known.
- Design-system token mapping is known.
Data
- Required data is available or a dependency is explicitly owned.
- Measures are defined.
- Dimensions and hierarchies are defined.
- Time grain is defined.
- Targets, budget, norms and benchmark logic are defined.
- Number/date formatting semantics are agreed.
Power BI Development
- Visuals and interactions are feasible in the chosen runtime.
- Performance implications are understood.
- Theme/Power UI/PBIP reuse path is known.
- Preview/custom visual dependencies are documented.
- Export/print behavior can be tested.
Product / PM
- Scope is agreed.
- Dependencies and unresolved questions have owners.
- Acceptance criteria are defined.
- The page is scheduled only after business, design, data and development readiness align.
Recovered 19-check compact checklist
- [ ] Business question is clear
- [ ] Requirements are validated
- [ ] Data is available
- [ ] Measures are defined
- [ ] Dimensions are defined
- [ ] Filters are defined
- [ ] Default filter state is defined
- [ ] Visuals are specified
- [ ] Native Power BI component mapping is known
- [ ] Custom visuals are explicitly approved
- [ ] Interactions are defined
- [ ] Drill-down / drillthrough is defined
- [ ] Tooltip behavior is defined
- [ ] Responsive/embed requirements are known
- [ ] Accessibility is checked
- [ ] Figma design is complete
- [ ] Design-system tokens are mapped
- [ ] Print/export requirements are known
- [ ] Edge cases are documented