Resource Histogram
The Resource Histogram illustrates the distribution of work among team members over the project's duration. It helps identify periods of high or low workload, enabling the Project Manager to balance resources effectively.
Methodology
1.	Project Timeline Division: The 8-month project duration is divided into 16 two-week periods.
2.	Task Scheduling: Tasks are mapped to these periods based on their start and finish dates.
3.	Workload Calculation:
o	For each task assigned to a team member, we calculate the number of hours they work during each period.
o	A standard work schedule of 8 hours per day and 5 workdays per week (40 hours per week).
o	If a task spans multiple periods, the workload is distributed accordingly.
Resource Histogram Data
Total Work Hours per Team Member:
o	Leo (PM): 984 hours
o	Bill (SD): 1,776 hours
o	Lisa (D1): 1,336 hours
o	Andy (D2): 1,552 hours
o	Kent (D3): 1,288 hours
Work Hours Distribution:
Below is the distribution of work hours for each team member across the 16 periods.
Period Definitions:
o	Period 1: Days 1-14
o	Period 2: Days 15-28
o	Period 3: Days 28-41
o	Period 4: Days 42-55
o	Period 5: Days 56-69
o	Period 6: Days 70-83
o	Period 7: Days 84-97
o	Period 8: Days 98-111
o	Period 9: Days 112-125
o	Period 10: Days 126-139
o	Period 11: Days 140-153
o	Period 12: Days 154-167
o	Period 13: Days 168-181
o	Period 14: Days 182-195
o	Period 15: Days 196-209
o	Period 16: Days 210-223
Work Hours per Team Member per Period:
(Note: The following is an estimated distribution based on task assignments and durations.)
Period	Leo (PM) Hours	Bill (SD) Hours	Lisa (D1) Hours	Andy (D2) Hours	Kent (D3) Hours
1					
2					
3					
4					
5					
6					
7					
8					
9					
10					
11					
12					
13					
14					
15					
16					
Total	984	1,776	1,336	1,552	1,288
Explanation:
o	Periods 1-3: Leo and Bill focus on analysis and design tasks. Leo (PM) spends time on requirements analysis and feasibility studies.
o	Periods 4-5: Lisa and Kent begin UI/UX design tasks, while Andy starts initial development tasks.
o	Periods 6-10: Core development phase where all developers are heavily involved in coding and integration.
o	Periods 11-12: Andy and Kent focus on testing and deployment preparation.
o	Periods 13-16: Leo resumes significant involvement for UAT, training, and project closure. Lisa assists with training materials.

Work Breakdown Structure (WBS) with Resource Assignments
WBS	Task Name	Duration (Days)	Duration (Hours)	Assigned To
1	Analysis Phase			
a	Background study on e-payment implementation	18	144	Bill
b	Requirements Analysis	20	160	Bill, PM
c	Technical Feasibility Study	22	176	Bill, PM
2	Design Phase			
d	System Design	25	200	Bill, PM
e	Module Design	15	120	Bill, Lisa
f	Interface Design	25	200	Lisa, Kent
g	Database Design	15	120	Bill, Andy
h	UI Design	15	120	Lisa, Kent
i	Security Design	20	160	Bill, Andy
j	Integration Testing	12	96	Andy, Kent
k	System Testing	12	96	Andy, Kent
3	Implementation Phase			
l	Coding Core Modules	30	240	Lisa, Andy
m	Coding Module E	20	160	Lisa
n	Coding Module F	20	160	Kent
o	Develop UI	12	96	Lisa, Kent
p	Database Implementation	25	200	Bill, Andy
q	Security Implementation	30	240	Bill, Andy
r	Testing Module N	25	200	Kent
s	Testing Module S	25	200	Lisa
t	Final Integration	20	160	All Team Members
4	Deployment Phase			
u	Deployment Preparation	5	40	PM, Andy
v	System Deployment	5	40	Andy
w	User Training	5	40	Lisa
x	Project Handover	12	96	PM, Bill
y	Post-Deployment Support	20	160	Andy, Kent
z	Project Closure	19	152	PM

Could you finish the Work Hours per Team Member per Period table base on the Work Breakdown Structure (Even if they are on furlough we still pay them, the total is there so you can verify your calculations)?