Skip to main content
Prompts PMP Agile Fail-Proof Project Plan Generator

model planning template risk: low

PMP Agile Fail-Proof Project Plan Generator

The prompt directs the model to role-play as a Senior Project Manager certified in PMP and Agile Scrum Master to create a fail-proof execution plan for a described project. It spec…

PROMPT 

ROLE: Act as a Senior Project Manager certified in PMP and Agile Scrum Master with Fortune 500 experience.

INPUT: My current project is: "${describe_project}".

GOAL: I need a fail-proof execution plan.

REASONING STEPS (CHAIN OF THOUGHT):

Deconstruction: Break down the project into Logical Phases (Phase 1: Foundation, Phase 2: Development, Phase 3: Launch/Delivery).

Critical Path: Identify the tasks that, if delayed, delay the entire project. Mark them as ${critical}.

Resource Allocation: For each phase, list the tools, skills, and human capital required.

Pre-mortem Analysis: Imagine the project has failed 3 months from now. List 5 probable reasons for failure and generate a mitigation strategy for each one NOW.

FORMAT: Markdown table for the schedule and bulleted list for the risk analysis.

INPUTS

describe_project REQUIRED

Description of the current project.

e.g. Building a new e-commerce website with user authentication and payment integration.

REQUIRED CONTEXT

  • project description

ROLES & RULES

Role assignments

  • Act as a Senior Project Manager certified in PMP and Agile Scrum Master with Fortune 500 experience.
  1. Break down the project into Logical Phases (Phase 1: Foundation, Phase 2: Development, Phase 3: Launch/Delivery).
  2. Identify the tasks that, if delayed, delay the entire project. Mark them as ${critical}.
  3. For each phase, list the tools, skills, and human capital required.
  4. Imagine the project has failed 3 months from now. List 5 probable reasons for failure and generate a mitigation strategy for each one NOW.
  5. Output schedule as Markdown table.
  6. Output risk analysis as bulleted list.

EXPECTED OUTPUT

Format
markdown
Schema
markdown_sections · Schedule (Markdown table), Risk analysis (bulleted list)
Constraints
  • Markdown table for the schedule
  • bulleted list for the risk analysis

SUCCESS CRITERIA

  • Deconstruct project into specified phases.
  • Identify and mark critical path tasks.
  • Allocate resources for each phase.
  • Perform pre-mortem analysis with 5 failure reasons and mitigations.

FAILURE MODES

  • Fixed phases may not suit all project types.
  • Critical path marking depends on vague ${critical} placeholder.
  • Pre-mortem reasons could be generic without project specifics.

CAVEATS

Dependencies
  • Requires project description in '${describe_project}'.
Missing context
  • Project-specific details like timeline, budget, or team size if not fully covered in '${describe_project}'.
Ambiguities
  • Unclear exact contents and structure of the 'Markdown table for the schedule' – does it include phases, critical path, resources?

QUALITY

OVERALL
0.90
CLARITY
0.90
SPECIFICITY
0.90
REUSABILITY
0.95
COMPLETENESS
0.85

IMPROVEMENT SUGGESTIONS

  • Specify table columns explicitly, e.g., 'Phase | Tasks | Duration | Resources | Critical (Yes/No)' for the schedule table.
  • Clarify the marker for critical path, e.g., replace '${critical}' with '**CRITICAL**' or similar.
  • Add flexibility for phase names: 'Adapt phases to fit the project type while using Foundation, Development, Launch as defaults.'

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR MODEL