We're giving away 30 tickets for FREE! Share your story, your vision, or your hustle and tell us why YOU deserve a ticket.
Apply nowWin a FREE 3 Day Ticket to FabCon Vienna. Apply now
what is generic estimates (in days) for a single person to deliver Power BI report based on complexity criteria (low,medium,high) . i know it all depends on requirements however just wanted to know generic estimate perspective
Complexity Level | Estimate in Days |
Low | ? |
Medium | ? |
High | ? |
Solved! Go to Solution.
@powerbiexpert22 , It also depends on whether the transformation of data was needed or not usually these estimates are also true above 20 reports
Complexity Level | Estimate in Days per report |
Low | 1-3 |
Medium | 4-8 |
High | 7-10 |
There are many other factors like sources, data cleanup etc
I'm approaching a decade in the field, and even today I can't accurately estimate the time it takes to prepare a report. It depends on many factors: the quality of the data, the level of drill-downs, the complexity of the calculated logic, and how much of it comes 'pre-cooked' from the database versus what you need to calculate within the tool.
In addition to all of this, as a data visualization expert, I have a commitment to get as close as possible to 'data pixel perfection' despite the tool's limitations. For me, the design phase usually takes longer than building the model and writing the DAX calculations.
The quickest report I've created took 2.5 workdays, and the more complex ones took up to 3 weeks. Therefore, during expectation-setting discussions with clients, if I'm required to provide an estimate, I always say it’s very rough, and the only thing I can commit to is raising flags if the pace is slower than expected.
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly
I'm approaching a decade in the field, and even today I can't accurately estimate the time it takes to prepare a report. It depends on many factors: the quality of the data, the level of drill-downs, the complexity of the calculated logic, and how much of it comes 'pre-cooked' from the database versus what you need to calculate within the tool.
In addition to all of this, as a data visualization expert, I have a commitment to get as close as possible to 'data pixel perfection' despite the tool's limitations. For me, the design phase usually takes longer than building the model and writing the DAX calculations.
The quickest report I've created took 2.5 workdays, and the more complex ones took up to 3 weeks. Therefore, during expectation-setting discussions with clients, if I'm required to provide an estimate, I always say it’s very rough, and the only thing I can commit to is raising flags if the pace is slower than expected.
If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly
@powerbiexpert22 , It also depends on whether the transformation of data was needed or not usually these estimates are also true above 20 reports
Complexity Level | Estimate in Days per report |
Low | 1-3 |
Medium | 4-8 |
High | 7-10 |
There are many other factors like sources, data cleanup etc
User | Count |
---|---|
67 | |
61 | |
47 | |
35 | |
32 |
User | Count |
---|---|
87 | |
71 | |
57 | |
51 | |
45 |