A-Media Limited: Project Scheduling and Risk Management Custom Case Solution & Analysis

Evidence Brief: A-Media Limited

Financial Metrics

Total Project Budget: 1,500,000 INR (Source: Paragraph 4)
Penalty for Delay: 50,000 INR per week beyond the 20-week deadline (Source: Exhibit 1)
Crashing Costs: Task C (Design) costs 15,000 INR to reduce by 1 week; Task E (Coding) costs 40,000 INR to reduce by 1 week (Source: Exhibit 2)
Current Estimated Cost: 1,100,000 INR based on normal durations (Source: Exhibit 2)
Profit Margin Target: 25 percent (Source: Paragraph 6)

Operational Facts

Project Scope: 11 distinct activities labeled A through K (Source: Exhibit 2)
Normal Duration: 24 weeks total if following the linear path (Source: Exhibit 2)
Critical Path Activities: A (Specs), B (Approval), D (Architecture), F (Development), H (Testing), K (Deployment) (Source: Exhibit 2)
Resource Pool: 8 full-time engineers, 2 UI designers, 1 project manager (Source: Paragraph 8)
Geography: Operations based in Bangalore, India; Client based in Singapore (Source: Paragraph 2)

Stakeholder Positions

Rajesh Kumar (Project Manager): Concerned about the 4-week gap between the normal schedule and the client deadline. Advocates for crashing Task F (Source: Paragraph 12)
Sanjay Gupta (CEO): Insists on maintaining the 25 percent margin. Refuses to authorize additional headcount (Source: Paragraph 14)
Client (Retail Solutions): Stated the 20-week deadline is non-negotiable due to their own product launch (Source: Paragraph 3)

Information Gaps

Resource Elasticity: The case does not specify if the 8 engineers are interchangeable across Task F and Task H (Source: Researcher Note)
Quality Metrics: No data provided on the expected defect rate if Task H (Testing) is shortened (Source: Researcher Note)
Client Flexibility: No information on whether a phased delivery (MVP) would waive the delay penalty (Source: Researcher Note)

Strategic Analysis

Core Strategic Question

How can A-Media compress the project timeline by 16.6 percent to meet the 20-week deadline while protecting the 25 percent profit margin and avoiding the 50,000 INR weekly penalty?

Structural Analysis

The Critical Path Method (CPM) analysis reveals a 24-week duration. The project is structurally flawed relative to the client deadline. The bottleneck resides in Task F (Development), which accounts for 33 percent of the total timeline. Porter’s Value Chain analysis suggests that the primary value is created in the Architecture and Development phases, meaning any time reduction there carries the highest risk to final product integrity.

Strategic Options

Option 1: Cost-Optimized Crashing. Reduce Task D by 1 week and Task F by 3 weeks.
- Rationale: Targets the critical path at the lowest incremental cost.
- Trade-offs: Increases project cost by 135,000 INR.
- Resource Requirements: Requires 2 additional junior developers for Task F.
Option 2: Parallel Processing. Execute Task G (Documentation) and Task H (Testing) simultaneously rather than sequentially.
- Rationale: Reduces timeline without direct crashing costs.
- Trade-offs: High risk of rework if testing reveals major architectural flaws.
- Resource Requirements: Requires immediate availability of the technical writing team.
Option 3: Scope De-prioritization. Negotiate the removal of Task J (Advanced Analytics) to save 3 weeks.
- Rationale: Eliminates work rather than rushing it.
- Trade-offs: Potential long-term client dissatisfaction and loss of future contracts.
- Resource Requirements: Senior leadership intervention for negotiation.

Preliminary Recommendation

A-Media should pursue Option 1. The total crashing cost of 135,000 INR is significantly lower than the 200,000 INR penalty for a 4-week delay. This path preserves the 25 percent margin goal more effectively than accepting the penalty or risking the rework costs associated with Option 2.

Implementation Roadmap

Critical Path

The implementation must focus on the 20-week compressed schedule. The sequence is as follows:

Weeks 1-4: Complete Task A and B. No deviation allowed.
Weeks 5-6: Task D (Architecture) must be crashed by 1 week. This is the first milestone.
Weeks 7-15: Task F (Development) must be crashed by 3 weeks. This requires overlapping the start of Task F with the end of Task D.
Weeks 16-19: Task H (Testing) must remain at full duration to ensure quality.
Week 20: Final Deployment (Task K).

Key Constraints

Senior Engineer Bandwidth: Task D requires the Lead Architect. If this individual is over-allocated, the 1-week reduction will fail, delaying the entire chain.
Communication Overhead: Adding resources to Task F will increase coordination requirements. The PM must transition from technical oversight to pure coordination.

Risk-Adjusted Implementation Strategy

To mitigate the risk of Task F overrun, A-Media will implement a daily scrum specifically for the crashed activities. If Task F is not 50 percent complete by Week 10, the PM must trigger a contingency plan to move resources from non-critical activities like Task G. The plan assumes a 10 percent buffer in the budget to handle potential overtime costs not captured in the initial crashing estimate.

Executive Review and BLUF

BLUF

A-Media must crash the project schedule by four weeks to avoid a 200,000 INR penalty that would erode the project margin to 11 percent. By investing 135,000 INR to compress Task D and Task F, the firm secures a 20-week delivery and maintains a profit margin above 20 percent. This is the only path that satisfies the client deadline while remaining more profitable than the status quo. Delay is not an option as the penalty exceeds the cost of speed. APPROVED FOR LEADERSHIP REVIEW.

Dangerous Assumption

The analysis assumes that crashing Task F (Development) by 25 percent will result in a linear time reduction. In software engineering, adding more personnel to a late project often makes it later due to training requirements and communication complexity. If the new developers are not productive within 48 hours, the 135,000 INR investment will be lost without achieving the time saving.

Unaddressed Risks

Staff Attrition: The intense pressure of a crashed schedule increases the probability of engineer burnout. A single resignation in the Senior Developer pool during Week 12 would render the 20-week deadline impossible to meet.
Technical Debt: Crashing Task F likely leads to shortcuts in code documentation and modularity. This creates a long-term maintenance liability for A-Media that is not reflected in the current project budget.

Unconsidered Alternative

The team did not evaluate a performance-based incentive for the existing team. Instead of spending 135,000 INR on additional resources, A-Media could offer a 75,000 INR bonus pool shared among the current 8 engineers for hitting the 20-week mark. This aligns incentives, avoids the communication overhead of new hires, and saves 60,000 INR in direct costs.