Project Management Framework for Case Studies

Project Management Case Study Framework

Si ves en el caso…Te piden…Pon esto
Todo mezclado: posts, campañas, webs, tareasProjects vs OperationsSeparar operations = rutina / projects = cambio con inicio-fin
Brief vago: “we need marketing/growth”InitiationHacer Project Brief: objectives, sponsor, scope, budget, timeline, KPIs
Muchas ideas y todo “important”Scope + BacklogDefinir scope, separar essential/optional, crear prioritized backlog
Mercado cambia, feedback, A/B testsAgileHacer backlog + Sprint 1 + Sprint 2 con sprint goals
Muchas tareas abiertas, pocas terminadasKanban / WIPHacer Kanban board + WIP limits + detectar bottleneck
Entregables hechos pero siguen cambiosClosureDiferenciar delivery vs acceptance, poner acceptance criteria y closure plan
Te preguntan Asana/Trello/SlackToolsTool + purpose + risk + what not to do
Crisis, backlash, legal, greenwashingRiskHacer risk matrix: probability/impact + response: avoid/mitigate/transfer/accept
CEO pide cambio al finalScope changeMostrar trade-offs: time, budget, quality, risk. Proponer MVP/post-launch backlog
Fecha y budget fijos pero cosas cambianHybrid governanceTabla fixed vs flexible + quién aprueba qué
Te piden presupuestoBudgetCost vs price vs margin + tabla de budget + fórmula margin
Muchos proyectos y no caben todosPortfolioElegir según value, cost, risk, alignment, capacity y justificar excluidos
Entregado on time/budget pero revenue malPerformanceOperational success vs strategic success + project KPIs vs business KPIs

Frase comodín para casi todos: El problema no es solo operativo, sino de Project Management: falta de structure, prioritization, governance y clear decision-making.

Core Project Management Concepts

Project Management is the process of transforming an idea into a valuable result under constraints such as time, budget, scope, resources, risk, and stakeholder expectations. It is not only about organizing tasks, but about making decisions, setting priorities, and creating value.

A project is temporary and produces a unique outcome, while operations are ongoing and repetitive activities that keep the business running. Projects create change; operations maintain stability. A common mistake is treating projects like operations, because this creates endless work, unclear priorities, and no formal closure. At the beginning of a project, initiation is essential. The project manager must clarify why the project exists, what problem it solves, what success looks like, who the sponsor is, who makes decisions, and what constraints exist. Good initiation reduces ambiguity before execution starts.

Scope defines what is included and excluded from the project. If new requirements are added without adjusting time, budget, or resources, this is called scope creep. To avoid this, the project manager must make trade-offs visible and ask for approval when changes affect the project.

A deliverable is a tangible or verifiable output, such as a landing page, campaign assets, a media plan, or a final report. A WBS (Work Breakdown Structure) breaks the project into smaller parts so the team can understand what needs to be done and estimate work more realistically.

There are three main ways to manage projects. Predictive planning is useful when requirements are stable and control is important. Agile is useful when there is uncertainty, feedback, and change. Hybrid governance combines both: strategic elements such as budget, launch date, and compliance remain fixed, while execution elements such as messaging, creatives, and channels can adapt. In Agile, a backlog is a prioritized list of value-oriented work. It is not just a task list. A good backlog item should be specific and linked to value, for example: “Create and test three TikTok ad concepts to identify the strongest message.” The product backlog contains all potential work, while the sprint backlog contains the work selected for one sprint according to priority, capacity, and the sprint goal.

Execution should focus on flow, not just activity. A Kanban board helps visualize work through columns such as Backlog, Ready, In Progress, Review, Waiting for Approval, and Done. WIP limits prevent the team from starting too many tasks at the same time. If work gets stuck in one column, that is a bottleneck. Project management tools support visibility, but they do not replace judgment. Asana is useful for tasks, deadlines, and responsibilities. Trello is useful for simple Kanban boards. Slack is useful for quick communication, but should not be the system of record. Jira is useful for Agile backlog and sprints. Notion is useful for documentation, decisions, and lessons learned. Risk management means identifying what could go wrong before it damages the project. Risks can be strategic, financial, reputational, legal, resource-related, schedule-related, or stakeholder-related. Each risk should be evaluated by probability and impact. The four main responses are: avoid, mitigate, transfer, or accept. Stakeholder management is about understanding who has power, interest, and decision authority. High-power and high-interest stakeholders must be managed closely. High-power and low-interest stakeholders should be kept satisfied. Low-power and high-interest stakeholders should be kept informed. Low-power and low-interest stakeholders should be monitored. A budget translates strategy into resources and money. The project manager must distinguish between cost, which is what the agency pays; price, which is what the client pays; revenue, which is total income; and margin, which is revenue minus cost. A good budget includes internal resources, paid media, tools, influencers, contingency, and margin. A project can be successful operationally but weak strategically. Operational success means the project was delivered on time, within budget, and within scope. Strategic success means it created real business value, such as revenue, leads, conversions, awareness, or customer retention. Delivery and acceptance are not the same. Delivery means the team has produced the output. Acceptance means the authorized stakeholder has validated that the deliverable meets the criteria. A project is not professionally closed until deliverables are accepted, responsibilities are transferred, and lessons learned are documented. The project manager is not only a scheduler or task organizer. The PM acts as an integrator, connecting strategy, scope, stakeholders, budget, risks, team capacity, and priorities. Their role is to create alignment, protect focus, manage trade-offs, and drive value.

For any case study, use this structure: First, identify the real problem. Then, name the relevant project management concepts. After that, use evidence from the case. Finally, give a clear recommendation and explain the trade-off.

A strong exam sentence is: “The main issue is not a lack of effort, but a lack of structure, prioritization, and governance.”

Another useful sentence: “The project manager should make trade-offs visible instead of accepting all requests.”

And for final conclusions: “The recommendation should balance strategic alignment, financial discipline, resource capacity, and risk exposure.”

Risk Management Strategies

ProbabilityImpactPriority
HighHighCritical
HighMediumHigh
MediumHighHigh
MediumMediumMedium
LowLowLow

Risk Matrix: The most dangerous risks are high probability and high impact.

Risk Response Strategies

  • Avoid: Remove the risk. Example: Stop or pause the campaign.
  • Mitigate: Reduce probability or impact. Example: Change the message, check with legal, add evidence.
  • Transfer: Move the risk to someone else. Example: Use a PR agency, legal advisor, or insurance.
  • Accept: Accept and monitor the risk. Example: Continue if the risk is low.

Frase fácil: The PM can avoid, mitigate, transfer, or accept the risk.

The PM should use a risk matrix to identify the most serious risks and choose the right response: avoid, mitigate, transfer, or accept. Stakeholders should be managed according to their power and interest.

Essential Budget Formulas

  • Internal Cost: Hours × Cost/h
  • Client Billing: Hours × Price/h
  • Revenue: Sum of all client billing
  • Margin (€): Revenue – Cost
  • Margin (%): (Margin / Revenue) × 100
  • Influencers: Price/month × months
  • Tools: Price/user/month × users × months
  • Media Budget: Sum of all channels
  • Subtotal: Internal costs + influencers + media + tools + other costs
  • Contingency: Subtotal × %
  • Total Project Cost: Subtotal + contingency
  • Budget Left: Maximum budget – total project cost

Key Takeaways

The project is financially viable if the total project cost is below the maximum budget.