The ultimate Microsoft Fabric, Power BI, Azure AI, and SQL learning event: Join us in Stockholm, September 24-27, 2024.
Save €200 with code MSCUST on top of early bird pricing!
Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
Hi
I am trying to put together an initial technical requirements or prompts for things that would be good to know about at the start of a new power PI project as outlined below.
Ideally, this document would be completed by a product manager with help from other individuals after the project definition document has been completed. The topics outlined below are likely to end up as a quick reference cheat sheet that will be continuously updated throughout the project cycle.
Please can you provide any feedback or links to useful resources?
Initial Technical Requirements:
Project:
List names of users, distribution lists (DL), or Azure Active Directory groups (AAD) that will be involved in the project stages listed below.
List people who can help with the development
What additional software might you need?
List old products that may still be running when this project is done
Data:
List data source needed for the project and characteristics
Data source wrangling and Maintenance
Report Build:
Where will the file be stored
Report page outline
Product version control
Deployment:
Where will the end users consume the product
Workspace details
Solved! Go to Solution.
I think it always depends on your particular use case as to how much you need depending on resources (small teams many of the functions you mention here are sometimes just one person) , what skills and tools you have available to you.
additional things i might be thinking about are
test cases created related to test driven development https://www.amplework.com/blog/test-driven-development-and-best-practices/
CI/CD (continious integration/deployment) depending on the type of project you are doing orr acceess to tools
definitely where the artifacts needs to be kept in source control at the very least
a good approach to a development lifecycle will bring out the correct information also at the same time
ie requirements / profile data / data quality / prototype / iterate
interfacting with the data owners who may or may not be on the project.
also i really like data goblins checks lists he has quite a few and are really helpful too
https://data-goblins.com/checklists
Proud to be a Super User!
I think it always depends on your particular use case as to how much you need depending on resources (small teams many of the functions you mention here are sometimes just one person) , what skills and tools you have available to you.
additional things i might be thinking about are
test cases created related to test driven development https://www.amplework.com/blog/test-driven-development-and-best-practices/
CI/CD (continious integration/deployment) depending on the type of project you are doing orr acceess to tools
definitely where the artifacts needs to be kept in source control at the very least
a good approach to a development lifecycle will bring out the correct information also at the same time
ie requirements / profile data / data quality / prototype / iterate
interfacting with the data owners who may or may not be on the project.
also i really like data goblins checks lists he has quite a few and are really helpful too
https://data-goblins.com/checklists
Proud to be a Super User!
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Check out the August 2024 Power BI update to learn about new features.
User | Count |
---|---|
123 | |
85 | |
76 | |
55 | |
49 |
User | Count |
---|---|
135 | |
127 | |
78 | |
64 | |
63 |