How to Score 836 Points in Harvard Project Management Simulation Scenario A

Learn the strategy used to score 836 points in Scenario A of the Harvard Project Management Simulation: Scope, Resources, Schedule, including scope, team size, skill, outsourcing, prototypes, coaching, meetings, and overtime.

mbasimu expert

8/19/20263 min read

How to Score 836 Points in Harvard Project Management Simulation Scenario A

Scoring 836 points in Scenario A of the Harvard Project Management Simulation: Scope, Resources, Schedule requires a balanced approach to project scope, team resources, skills, outsourcing, prototypes, communication, and overtime. The strategy used from Week 1 through Week 14 focused on maintaining a target scope of Level 4, a target team size of 15, improving team skill over time, using extensive outsourcing, maintaining four prototypes, and managing meetings and coaching carefully.

From Week 1 through Week 4, the target team size was maintained at 15 with a team skill level of Medium. Extensive outsourcing was used throughout the project, while four prototypes were maintained. Coaching was used more heavily during the early weeks, with three coaching sessions and one stand-up meeting per week. Status meetings were kept at zero, while overtime was encouraged. This combination provided additional team support while maintaining a consistent project structure.

Beginning in Week 5, the team skill level was increased to Medium-High while maintaining the team size at 15. Coaching was reduced from three sessions to two per week, with one stand-up meeting continuing throughout the project. This reflected a gradual shift from intensive team development toward maintaining productivity as the project progressed.

From Week 5 through Week 7, the team remained at Medium-High skill with four prototypes, extensive outsourcing, and encouraged overtime. The strategy continued to emphasize consistent team communication through one stand-up meeting while avoiding unnecessary status meetings.

From Week 8 through Week 12, the same core structure was maintained: 15 team members, Medium-High team skill, extensive outsourcing, four prototypes, one stand-up meeting, and encouraged overtime. Two coaching sessions were maintained during this period. In Week 12, coaching was reduced to one session as the project moved closer to completion.

During Weeks 13 and 14, the project entered its final stage. The team remained at 15 members with Medium-High skill, extensive outsourcing, and four prototypes. Coaching was reduced to zero, while one stand-up meeting continued. This helped maintain communication without adding unnecessary management activity during the final weeks.

The overall strategy behind the 836-point result was consistency and gradual adjustment rather than making major changes throughout the project. The target scope was maintained at Level 4, the team size remained stable at 15, and outsourcing was kept at an extensive level. Team skill was improved from Medium to Medium-High, while coaching was gradually reduced as the team became more capable and the project approached completion.

The use of four prototypes throughout the simulation also provided a consistent development approach. One stand-up meeting was maintained every week, while status meetings were avoided. Overtime was encouraged throughout the project to provide additional flexibility when required.

The progression from Week 1 to Week 14 can therefore be summarized as a controlled project-management strategy: begin with stronger coaching and a Medium-skilled team, improve the team to Medium-High skill, gradually reduce coaching as performance improves, maintain a stable team size, use extensive outsourcing, keep four prototypes, and maintain regular stand-up communication.

This approach produced a score of 836 points in Scenario A. The strategy demonstrates the importance of balancing scope, resources, schedule, team development, outsourcing, and communication rather than focusing on a single project-management factor. The decisions should nevertheless be adapted to the specific scenario conditions and simulation results, as different starting conditions or objectives may require different choices.


Harvard Project Management Simulation: More Scenarios

Looking for strategies for the other scenarios? Explore the complete Harvard Project Management Simulation guides: