Product Plan
Work and Production
Everybody gets 1 week off per month, but is expected to work 18 8 hour shifts during the rest i.e. 6 days per week. This is because working remotely necessitates we all be available to each other during work time for easier meetings and consultations. We do not want burn out and we have remoteness issues.
1 Month = 18 * 8 = 144 hours per person per month (£23.14 per hour)
Coding hours
Lead – 2 hours per day ¼ (6 hours to run the team and the office as well as take care of specific management tasks, and meetings, software testing and paperwork)
Programmer 6 hours per day ¾ (2 hours for meetings and writing and reading reports)
Joe coding hours per week = 0
Lead Programmer coding hours per month = 36
Programmer coding hours per month = 108
Hours for the build = 2592
Modules = 70
Build time per module = 37 hours
(Scenario B = 59 hours)
We are going to be planning heavy. We need to be because this build will not be simple.
Each Lead Programmer will employ 1 additional programmer for 4 months and a further programmer for 2 months. They will need to allocate the tasks between their own and their teams skill sets and availability. (864 hours)
This is considerably less than I intended. The teams were going to be 4 strong for all 6 months! You will see that the company structure design has 12 jobs. These will need to be re-allocated between the people you have. Critically, you have half a workforce, and have to write ¼ of the code yourselves.
Company structure
Production Timetable
Testing
First Month Schedule
Week 1
Leads + Joe: Develop Production Plan
Week 2
All leads: Write and post Job Adverts.
All leads: Secondary role. 1st report:
Lead programmer Engine (Office Manager): Computer network + Office budget + Work and holiday schedule.
Lead programmer Interactive (Project Manager): Progress reports and forecasts.
Lead programmer Social (Marketing Manager): Pagelife Public liaison Plan
Week 3
All leads:
LLD + Recruitment.
Week 4
Holiday