AI Prompt for Project Planning
Create a sprint planning framework for graphic designers in interior-design to improve SEO rankings.
More prompts for Project Planning.
Conduct a structured project post-mortem that captures lessons learned, root causes of issues, and concrete recommendations for future projects.
Create a structured project milestone tracker with status indicators, timeline visualization, and automated status report generation.
A comprehensive prompt that creates an entire annual operating system including vision, quarterly OKRs, weekly planning frameworks, daily routines, habit systems, and review templates.
Design a resource allocation plan for a Infrastructure Upgrade project in co-working for venture capitalists.
Build a 6-Month product roadmap for a outdoor-recreation product targeting HR professionals.
Create a sprint planning framework for startup founders in augmented-reality to enhance user experience.
You are an experienced engineering manager coach who helps small business owners master entertainment through practical, step-by-step guidance. Design a sprint planning template and process guide for graphic designers working in the interior-design industry. **Sprint goal:** improve SEO rankings **Sprint duration:** 2-week **Team size:** 5-8 people **Tone:** data-driven and analytical ## Sprint Planning Preparation ### Before the Meeting - Review and groom the product backlog (top 20 items) - Ensure stories have acceptance criteria - Check team capacity (vacations, on-call, meetings) - Review velocity from past 3 sprints - Identify carry-over items from last sprint ### Capacity Planning - Calculate available story points based on: - Team members: 5-8 people - Sprint length: 2-week - Historical velocity range - Known capacity reducers ## Sprint Planning Session Guide ### Part 1: The "What" (first half of session) - Product owner presents sprint goal - Review top backlog items aligned with goal - Clarify requirements and acceptance criteria - Discuss technical approach at high level - Identify dependencies and blockers ### Part 2: The "How" (second half of session) - Break stories into tasks - Estimate tasks in hours - Identify task owners - Flag risks and unknowns - Commit to sprint backlog ## Sprint Backlog Template | Story ID | Title | Points | Tasks | Owner | Status | Blockers | |----------|-------|--------|-------|-------|--------|----------| | [ID] | [Story title] | [Est] | [Count] | [Name] | [Status] | [Any] | ## Definition of Done Checklist - Code complete and reviewed - Unit tests passing - Integration tests passing - Documentation updated - Product owner acceptance - No critical bugs remaining - Performance benchmarks met ## Daily Standup Format Each team member answers: 1. What did I complete since last standup? 2. What will I work on today? 3. What is blocking my progress? Keep to 15 minutes maximum. Park detailed discussions for after standup. ## Sprint Health Indicators - Burndown chart tracking guidance - Scope change monitoring - Blocker resolution time - Team mood/energy check ## Sprint Review and Retrospective Prep - Demo preparation checklist - Retrospective prompts tailored for interior-design teams - Velocity and quality metrics to present Structure as a playbook with: Overview, Prerequisites, Step-by-step Plays, Metrics to Track, and Troubleshooting Guide.
Replace the bracketed placeholders with your own context before running the prompt:
[ID]— fill in your specific id.[Story title]— fill in your specific story title.[Est]— fill in your specific est.[Count]— fill in your specific count.[Name]— fill in your specific name.[Status]— fill in your specific status.[Any]— fill in your specific any.