AI 프롬프트: 프로젝트 관리

I need to plan a sprint for my team.

Project: [project name and goal]
Team members: [list roles and availability]
Backlog items: [list 10-15 user stories or tasks with estimates]
Sprint length: [1 week / 2 weeks]
Previous sprint velocity: [story points completed if known]

Create:
1. A prioritized sprint backlog with story point assignments
2. Task breakdown for the top 5 items (subtasks with time estimates)
3. Dependencies between tasks and the critical path
4. Risk flags — items likely to spill over and why
5. Daily standup focus areas for each day of the sprint
6. Sprint goal statement in one sentence

I have a large task that needs to be broken down:

Task: [describe the big deliverable]
Deadline: [when it's due]
Team members available: [who can work on this]
Technical constraints: [tools, platforms, dependencies]
Definition of done: [what 'complete' looks like]

Break this into:
1. A work breakdown structure with 3 levels of detail
2. Estimated hours for each subtask
3. Which subtasks can run in parallel vs. must be sequential
4. The minimum viable version that could ship in half the time
5. Acceptance criteria for each subtask
6. A Gantt-style timeline showing the critical path

Analyze the risks for this project:

Project: [name and description]
Timeline: [start and end dates]
Team: [size and experience level]
Budget: [total budget]
External dependencies: [vendors, APIs, approvals needed]
Stakeholders: [who cares about this project]

Provide:
1. A risk register with 8-10 risks ranked by likelihood and impact
2. For each risk: trigger condition, impact description, and mitigation plan
3. The top 3 risks that could kill the project entirely
4. Early warning indicators for each critical risk
5. A contingency plan for the single most likely risk
6. A risk review cadence recommendation

Help me manage stakeholders for this project:

Project: [name and one-sentence summary]
Stakeholders: [list each person with their role, department, and interest in the project]
Project phase: [kickoff / in-progress / nearing launch]
Biggest political challenge: [what makes this project politically tricky]

Create:
1. A stakeholder map: power vs. interest grid with each person placed
2. Communication plan: what each stakeholder needs to know, how often, and in what format
3. A RACI matrix for key project decisions
4. Scripts for managing a stakeholder who wants to expand scope
5. An escalation framework: when and how to escalate issues
6. A 'pre-mortem' — what stakeholder-related failure looks like and how to prevent it

Generate a project status report from these details:

Project: [name]
Reporting period: [this week / this month]
Milestones completed: [list what shipped]
Milestones in progress: [list what's being worked on]
Blockers: [anything stuck and why]
Budget status: [on track / over / under]
Team morale: [any concerns]

Write:
1. An executive summary (3 sentences: overall status, biggest win, biggest concern)
2. A red/yellow/green status for: scope, timeline, budget, quality, team
3. Key accomplishments with business impact
4. Risks and blockers with owner and resolution plan
5. Next week's priorities
6. One decision needed from leadership (with recommendation)

Help me run a retrospective for my team:

Project/sprint: [what just finished]
Team size: [number of people]
What went well: [list 3-5 wins]
What didn't go well: [list 3-5 problems]
Previous retro action items: [what was decided last time]
Team dynamic: [any tension or morale issues]

Design a retro that includes:
1. A creative format beyond 'start/stop/continue' (with facilitation instructions)
2. 5 targeted questions to surface the real issues
3. A prioritization method for deciding which problems to fix
4. Action items template: specific, owned, and time-bound
5. A follow-up plan to ensure action items actually happen
6. A 'team health' pulse check with 5 dimensions to rate