This Slideshare presentation is a partial preview of the full business document. To view and download the full document, please go here https://flevy.com/browse/business-document/wbs-for-agile-business-intelligence-projects-3645 DOCUMENT DESCRIPTION This template provides a work breakdown structure for business intelligence projects and for requirement effort estimation for a waterfall methodology-based project or user story estimation for an agile-based project. The template is based on project requirement complexity (low, medium and high). For this template, the assumption is that ETL (extract, transform, load) and the front-end visualization portion (reporting) are part of project development. Project Management and contingency hours should be considered while estimating any type of project from 10-20% depending on the project, SOW type, external dependencies, anticipated delays in data sourcing, etc.

1. Guidelines
* This can be used for requirement effort estimation for a waterfall methodology-based project, or user story estim
1. Effort estimation is based on complexities:
· Low complexity – 24
· Medium – 40
· High - 80
2. Low complexity requirements are defined as below:
· 1 dashboard
· Single source
· 4-6 metrics on a dashboard
· 1-3 filters.
· Simple table/ graph reporting
· Requirements are clear
· Involve simple data model
· ETL is not complex
3. Medium complexity requirements are defined as below:
· Involve 2-3 dashboards
· 3+ filters
· Upto 18 requirements/ metrics
· Complex graphs
· Involves join and union
· Involves performance and security requirement
4. Complex requirements are defined as below:
· More than 3 sources
· Multiple business users giving requirements
· Overall metrics 20+
· There can be vague requirements which evolve with time
· 4+ filters
· Multiple joins, union
· Complex ETL, data model
· Complex visualization
· Performance becomes one key factor
· Security requirements
5. BD is Business Days and BI is Business Intelligence.
6. Data sourcing can be delayed many times; the effort in the task can be refined based on first requirement.
7. There might be additional tasks specifically related to third party tools/ API integration that can be customized a
8. Contingency can be based on various factors and range from 10-20% depending on project and SOW type, dep
9. Initiation and closure activities for BI projects are industry standard and can be referred from A Guide to the Pr
10. Sprint can be 40/80/120 BD based on company/ project requirement and accordingly template can have a spr
11. Dependencies of activity will impact the priority and the order in which they are picked up.

2. User Story Complexity Iteration Activities Effort estimated
Planned Start
Date (BD)
Planned End
Date (BD)
Comments
Iteration 1 Get problem statement/ Elicit requirement 2 Day 1 Day 1
Source sample data 2 Day 1 Day 1
Create mockup 4 Day 1 Day 2
Create data model 2 Day 2 Day 2
Demo and feedback 0.5 Day 2 Day 2
Total Effort for Iteration 1 10.5
Iteration 2 Update mockup 1 Day 2 Day 3
Update Data model 1 Day 2 Day 3
ETL/ Source actual data 4 Day 3 Day 3
E2E dashboard build with integration
testing 4 Day 3 Day 4
Demo and feedback 1 Day 4 Day 4
Total Effort Iteration 2 11
Iteration 3 Build final product 1.5 Day 4 Day 4
Demo and signoff 0.5 Day 4 Day 4
Deployment 0.5 Day 4 Day 4
Total Effort Iteration 3 2.5
24 Day 1 Day 4 Actual Days = 4
Iteration 1 Get problem statement/ Elicit requirement 4 Day 1 Day 2
Estimates based on 1
resource
Source sample data 4 Day 1 Day 2
Create mockup 8 Day 2 Day 3
Create data model 2 Day 2 Day 3
Can be parallel to line
item 15 if 2 resources
Demo and feedback 0.5 Day 4 Day 4
Total Effort for Iteration 1 18.5
Iteration 2 Update mockup 2 Day 4 Day 4
Update Data model 1 Day 4 Day 4
Demo and feedback, signoff on model 0.5 Day 4 Day 4
Total Effort Iteration 2 3.5
Iteration 3 ETL/ Source actual data 8 Day 4 Day 6
E2E dashboard build with integration
testing 6 Day 6 Day 7
Can be parallel to line
item 15 if 2 resources
Demo and feedback 0.5 Day 7 Day 7
Total Effort Iteration 3 14.5
Iteration 4 Build final product 2 Day 7 Day 7
WBS strcuture for BI projects planning phase based on low, medium and high complexity requirements
Effective hours = 6
* Activties for initiation and closure are as defined in PMBOK
Requirement 2/User Story
2
Requirement 1/User Story
1
Medium
Low
This document is a partial preview. Full document download can be found on Flevy:
http://flevy.com/browse/document/wbs-for-agile-business-intelligence-projects-3645

3. Show and tell, sign off 0.5 Day 7 Day 7
Deployment 1 Day 7 Day 7
Total Effort Iteration 4 3.5
40 Day 1 Day 7 Actual days = 7
4
Contigency of 10 %
can be added due to
delay in sourcing/
resource attrition etc
Iteration 1 Get problem statement 6 Day 1 Day 2
Source sample data -1 4 Day 1 Day 2
Create mockup 8 Day 2 Day 3
Create data model 4 Day 2 Day 3
Demo and feedback 0.5 Day 4 Day 4
Total Effort for Iteration 1 22.5
Iteration 2 Source sample data -2 2 Day 4 Day 5
Update mockup 4 Day 5 Day 5
Update Data model 2 Day 5 Day 6
Demo and feedback 0.5 Day 5 Day 6
Total Effort Iteration 2 8.5
Iteration 3 Get signoff on model 0.5 Day 5 Day 6
ETL/ Source actual data 24 Day 6 Day 9
E2E dashboard build with integration
testing 20 Day 9 Day 13
Can be parellel to line 58
if 2 resources
Demo and feedback 0.5 Day 13 Day 13
Total Effort Iteration 3 45
Iteration 4 Build final product 2 Day 13 Day 13
Show and tell, sign off 1 Day 13 Day 13
Deployment 1 Day 13 Day 13
Total Effort Iteration 4 4
80 Day 1 Day 13 Actual days = 13
Requirement 3/User Story 3
This document is a partial preview. Full document download can be found on Flevy:
http://flevy.com/browse/document/wbs-for-agile-business-intelligence-projects-3645

4. 4
Contigency of 10 %
can be added due to
delay in sourcing/
resource attrition etcComplex
This document is a partial preview. Full document download can be found on Flevy:
http://flevy.com/browse/document/wbs-for-agile-business-intelligence-projects-3645

5. Assumptions
1. Applicable to Business intelligence (BI) projects having ETL and visualization components.
2. Days are assigned based on actual business days (BD) excluding weekends.
3. Approximately 6 hrs. being considered as productive hrs. (keeping in mind meeting, training and other non-b
4. Template can be further customized for agile/waterfall methodology based on requirement, tools and techno
5. Industry standard for waterfall methodology requires business requirements to be pre-documented at the sta
6. For agile projects, product backlog and priority should be defined, and accordingly user story should be picke
7. Effort is estimated based on a single resource.
8. 10% effort should be considered for project management.
9. Contingency is considered 10% based on anticipated delays in data sourcing, requirement clarity, third-party
This document is a partial preview. Full document download can be found on Flevy:
http://flevy.com/browse/document/wbs-for-agile-business-intelligence-projects-3645

6. 1
Flevy (www.flevy.com) is the marketplace
for premium documents. These
documents can range from Business
Frameworks to Financial Models to
PowerPoint Templates.
Flevy was founded under the principle that
companies waste a lot of time and money
recreating the same foundational business
documents. Our vision is for Flevy to
become a comprehensive knowledge base
of business documents. All organizations,
from startups to large enterprises, can use
Flevy— whether it's to jumpstart projects, to
find reference or comparison materials, or
just to learn.
Contact Us
Please contact us with any questions you may have
about our company.
• General Inquiries
support@flevy.com
• Media/PR
press@flevy.com
• Billing
billing@flevy.com