Prompts for AI-Powered Agile Project Planning
The Competitive Edge for Modern Project Managers
Below is a set of prompts for Agile project planning. Start with Prompt 1, then proceed in order to build the complete project plan. As you work, apply the best practices outlined in the Prompt and Content Engineering chapter of this book.
Prompt 1 - AI Prompt for Generating Project Ideas
I want you to act as an idea generator for projects. I will provide my interests, skills, and context. Using this input, generate a list of possible projects I could pursue.
Each project should include:
- A clear project title.
- A short description of what the project is about.
- The value or benefit it would create for me, others, or an organization.
- The type of project approach that may suit it best, such as Agile, Scrum, Kanban, Lean, Predictive, or Hybrid.
Here are my inputs:
- My interests: [insert your interests here].
- My skills and strengths: [insert your skills here].
- My context, time, resources, environment: [insert constraints or opportunities].
Please return 5–10 project suggestions tailored to this input. Vary them in scope and complexity so I can compare options. Highlight which projects would deliver quick wins and which could become larger initiatives.
Prompt 2 - Developing a Problem Statement
I want you to help me create a clear and compelling problem statement for my selected project. I will provide you with the project idea text, including title, description, and value. Based on this input, generate a problem statement that includes the following parts:
- Context, a short background that explains the situation and why it matters.
- The Problem, a concise description of the issue or gap that needs to be solved.
- Impact, who is affected by the problem and the consequences if it remains unsolved.
- Desired Outcome, a high-level view of what success would look like once the problem is addressed.
Here is my project idea text: [Insert project idea text here]
Please return a single, well-structured problem statement in plain language that could be used as the foundation for project initiation.
Prompt 3 - AI Prompt for Agile Roadmap Development
Act as a professional Scrum and Agile Project Manager. I will provide you with two inputs, a company profile and a problem statement. Based on these, create a structured Agile roadmap that includes:
- Phases or releases with clear titles.
- Timeline for each phase, relative, such as Month 1–2, Month 3–4.
- Key features or deliverables planned in that phase.
- Value alignment connecting to company vision, the problem statement, and strategic objectives.
- Quick wins versus long-term initiatives clearly identified.
- Notes on how Agile practices will support this roadmap.
Here are my inputs:
- Company Profile: [insert here]
- Problem Statement: [insert here]
Please format the output in a clear, release-style roadmap, showing progression from foundation to advanced value delivery.
Prompt 4 - Product Vision Development
Act as a professional Scrum Product Owner. I will provide you with two inputs, a company profile and a roadmap. Using these, develop a clear and compelling Product Vision statement that includes:
- An inspiring, concise vision statement.
- The target customer or user group.
- The core problem or need the product solves.
- The value and benefits delivered, business and customer.
- How the roadmap phases connect to achieving this vision.
- Alignment with company mission, strategy, and long-term goals.
Here are my inputs:
- Company Profile: [insert here]
- Roadmap: [insert roadmap here]
Please return the output in sections: Product Vision Statement, Target Customer, Problem or Need Addressed, Value Delivered, Strategic Alignment, How the Roadmap Supports the Vision.
Prompt 5 - Elevator Statement Development
Act as a professional Agile Product Manager. I will provide a company profile and a product vision. Using these, create a concise Elevator Statement that includes:
- The target customer or user.
- The core need or problem being solved.
- The key benefit or unique value provided.
- The differentiator that explains why this product matters.
Here are my inputs:
- Company Profile: [insert here]
- Product Vision: [insert here]
Please return a 3–5 sentence Elevator Statement that is inspiring, memorable, and suitable for pitching.
Prompt 6 - Product Architecture Development
Act as a professional Agile Solution Architect. I will provide a roadmap, and you will develop a high-level product architecture that:
- Identifies the main system layers or modules, such as front-end, back-end, data, integrations, and AI services.
- Maps key features from each roadmap phase into these modules.
- Shows relationships and dependencies between components.
- Highlights scalability, security, and integration considerations.
- Explains how the architecture supports iterative and incremental delivery.
Input: Roadmap: [insert roadmap here]
Please return the architecture with sections for Core Modules or Layers, Feature Mapping by Roadmap Phase, Dependencies and Integrations, and Agile Delivery Considerations.
Prompt 7 - Product Datasheet Development
Act as a professional Agile Product Manager. I will provide a roadmap and a product architecture. Using these, create a Product Datasheet that includes:
- Product Name.
- Company.
- Product Overview.
- Target Users.
- Key Features aligned with roadmap and architecture.
- Business Value.
- User Value.
Inputs: Roadmap, Product Architecture, Product Name, Company.
Please return the datasheet as clean text sections with headings for each item.
Prompt 8 - Product Specification Development
Act as a professional Agile Product Owner and Solution Architect. I will provide a roadmap, a product architecture, and a product datasheet. Using these, create a comprehensive Product Specification that includes:
- Product Overview.
- Target Users and Use Cases.
- Functional Requirements grouped by roadmap phases and mapped to architecture.
- Non-Functional Requirements covering performance, security, scalability, usability, and compliance.
- System Architecture Mapping.
- Data and Integration Requirements.
- Dependencies and Constraints.
Inputs: Roadmap, Product Architecture, Product Datasheet.
Please return a well-structured Product Specification with clear sections and bullet points.
Prompt 9 - Product Backlog Development
Act as a professional Scrum Product Owner. I will provide a product architecture, a product datasheet, a product specification, and a roadmap. Using these, create a structured Product Backlog with:
- Epics aligned with roadmap phases.
- Features under each Epic.
- User Stories in the format, As a [user], I want [function], so that [benefit].
- Sequential numbering of User Stories.
- A limit on the number of stories, which I will specify.
- Clear, testable stories connected to user value.
Inputs: Architecture, Datasheet, Specification, Roadmap, Backlog Limit.
Please return the output grouped by Epic, with Features and numbered User Stories listed beneath.
Prompt 10 - Definition of Done Development
Act as a professional Scrum Master. I will provide a Product Backlog. Using this, create a clear and practical Definition of Done for the product that:
- Applies to all User Stories.
- Includes functionality, testing, documentation, integration, and user acceptance.
- Reflects technical standards and business value standards.
- Aligns with Agile principles of transparency, inspection, and adaptation.
Input: Product Backlog: [insert backlog here]
Please return the output as a concise checklist titled Definition of Done for [Product Name].
Prompt 11 - Prompt for Release 1 Planning
Act as a professional Scrum Product Owner. I will provide a Product Backlog. Using this, create a detailed plan for Release 1 that includes:
- Selected Epics, Features, and User Stories that deliver the highest value.
- A clear scope for Release 1 focused on foundations and quick wins.
- An estimated timeline, such as Month 1–2 or Sprint 1–2.
- Dependencies or prerequisites that must be addressed first.
- Acceptance Criteria for Release 1 as a whole.
- Notes on how Agile delivery will ensure progress and adaptability.
Input: Product Backlog: [insert backlog here]
Please return the output with a Release name, timeline, scoped items, dependencies and risks, acceptance criteria, and Agile delivery notes.
Prompt 12 - Sprint Planning and Estimation
Act as a professional Scrum Master. I will provide a Release Plan. Using this, create the plan for Sprint 1 with Story Point estimates that includes:
- A Sprint Goal.
- Selected User Stories from Release 1 that fit Sprint 1.
- Story Point estimates using a relative scale.
- A short task breakdown per story.
- Acceptance Criteria for Sprint 1.
- A Velocity note explaining assumptions.
Input: Release 1 Plan: [insert here]
Please return the output with Sprint name, Sprint Goal, selected stories with estimates and tasks, total committed points, acceptance criteria, and a velocity note.
Prompt 13 - AI Prompt for Risk Brainstorming from Sprint Backlog
Act as a professional Agile Risk Manager. I will provide a Sprint Backlog. Using this, brainstorm potential risks that could affect successful delivery of the Sprint. Each risk should be tied to backlog items or tasks, be described clearly, and rated Low, Medium, or High.
Input: Sprint Backlog: [insert backlog here]
Please return the output as a short Risk Register with each risk, its related backlog item, and a criticality rating.
Prompt 14 - Agile Chart Completion
Act as a professional Agile Coach. I will provide a chart template and actual data such as velocity or completed items. Using these inputs, fill the chart with appropriate values and include both the ideal trend and actual progress. If data is missing, generate a reasonable first draft projection.
Inputs: Chart Type, Template, Actual Data if any.
Please return the output as a tabular dataset for the chosen chart type, with notes on data source and brief observations.
Advanced Project Management — Measuring Project Performance
Move beyond guesswork and status reporting. This course helps you measure real progress, spot problems early, and make confident decisions using proven project performance techniques. If you manage complex projects and want clearer visibility and control, this course is built for you.
This is not abstract theory. You’ll work step by step through Earned Value Management (EVM), learning how cost, schedule, and scope come together to show true performance. You’ll build a solid foundation in EVM concepts, understand why formulas work, and learn how performance data actually supports leadership decisions.
You’ll master Work Breakdown Structures (WBS), control accounts, and budget baselines, then apply core EVM metrics like EAC, TCPI, and variance analysis. Through a detailed real-world example, you’ll forecast outcomes, analyze trends, and understand contingencies and management reserves with confidence.
Learn how experienced project managers monitor performance, communicate results clearly, and take corrective action before projects slip. With practical exercises and hands-on analysis, you’ll be ready to apply EVM immediately. Enroll now and start managing performance with clarity and control.
Lead with clarity, influence, and outcomes.
HK School of Management brings you a practical, no-fluff Leadership for Project Managers course—built for real projects, tight deadlines, and cross-functional teams. Learn to set direction, align stakeholders, and drive commitment without relying on title. For the price of a lunch, get proven playbooks, and downloadable templates. Backed by a 30-day money-back guarantee—zero risk, high impact.
Learn More
HKSM