AI Prompts for Project Management

You are a PMP-certified senior project manager with 15 years of experience in enterprise software delivery. I need a project charter for a new project. **Context:** * **Project Name:** "Project Phoenix" * **One-Sentence Description:** Migrate the company's on-premise CRM to a new cloud-based SaaS solution. * **Business Goal:** Reduce CRM operational costs by 30% and improve data accessibility for the remote sales team. * **Key Stakeholders:** Jane Doe (VP of Sales), John Smith (Director of IT), Sales Team (as end-users). * **Estimated Timeline:** 6 months. * **Estimated Budget:** $150,000. **Task:** Draft a comprehensive project charter. **Format:** Use the following sections as H2s: 1. Project Purpose & Justification 2. Measurable Objectives & Success Criteria 3. High-Level Requirements & Scope 4. Key Stakeholders & Responsibilities (use a RACI matrix for Jane Doe, John Smith, and the Project Manager) 5. High-Level Project Risks 6. Summary Milestone Schedule (as a markdown table) 7. Summary Budget (as a markdown table) 8. Project Approval Requirements

You are a detail-oriented project scheduler. Your task is to break down a large project into smaller, manageable work packages. **Context:** We are developing a new mobile application for iOS and Android. The key features are: User Authentication, Activity Feed, In-App Messaging, and Profile Management. **Task:** Generate a Work Breakdown Structure (WBS) for the development phase of this project. Decompose the work to at least three levels. Level 1 should be the project name ("Mobile App Development"). Level 2 should be the major deliverables/features. Level 3 should be the work packages required to complete each feature. **Format:** Present the WBS as a nested, indented list. For example: 1\. Mobile App Development 1.1. User Authentication 1.1.1. Design UI/UX for Login/Signup Screens 1.1.2. Develop Backend Authentication Logic 1.1.3. Implement Social Login (Google/Apple) 1.1.4. Test Authentication Flow

You are a senior project manager responsible for leading effective and engaging project kickoff meetings. **Context:** We are kicking off "Project Phoenix," a 6-month CRM migration project. The attendees will be the core project team, the project sponsor (VP of Sales), and the head of IT. This is the first time this group has assembled. **Task:** Create a detailed agenda for a 90-minute project kickoff meeting. The goal is to align everyone on the project's objectives, scope, and roles, and to build initial momentum. **Format:** Structure the agenda in a markdown table with columns for: **Time Allotment (minutes)**, **Topic**, **Presenter**, and **Objective/Key Talking Points**. Include a follow-up email template to send after the meeting that summarizes decisions and action items.

You are a political strategist and expert in stakeholder management. Your strength is identifying who has influence and what they care about. **Context:** We are launching a project to automate a key internal reporting process currently done manually by the finance department. This will free up 3 finance analysts but requires a new software subscription and implementation support from the IT team. The final reports are consumed by the executive leadership team. **Task:** Identify all potential stakeholders for this project. For each stakeholder (or group), analyze their potential interests, influence level (High/Medium/Low), and concerns. **Format:** Produce a markdown table with the columns: **Stakeholder/Group**, **Primary Interests**, **Influence Level**, **Potential Concerns**, and **Suggested Engagement Strategy**.

You are an agile product owner skilled at translating unstructured ideas into well-formed user stories. **Context:** I just got out of a brainstorming meeting for a new e-commerce feature. Here are my raw notes: * Users want to save items for later, not just put them in the cart. * Like a "wishlist" or "favorites." * Should be able to add from the product page and the category page. * Needs to be accessible even after they leave the site. * Maybe they can have multiple lists? Like "Birthday Ideas" or "Office Gear." * Should be able to share a list with someone else via a link. **Task:** Convert these notes into a set of well-formed user stories following the "As a [[user type]], I want [[goal]], so that [[benefit]]" format. Include acceptance criteria for each story. **Format:** For each user story, provide: * **User Story:** * **Acceptance Criteria:** (as a bulleted list)

You are a project manager providing a weekly status update to executive stakeholders who are busy and care about outcomes, not technical details. **Context:** * **Project:** "Project Phoenix" * **Overall Status:** Yellow (due to a delay in vendor API access) * **Last Week's Accomplishments:** Completed UI mockups for the new CRM dashboard. Finalized data mapping for contact import. * **This Week's Goals:** Begin frontend development. Perform initial test data import. Secure vendor API access. * **Blockers/Risks:** The vendor has not yet provided production API credentials, which is blocking all integration work. This puts the Q4 testing milestone at risk. We have escalated this to our vendor account manager. * **Budget:** On track. **Task:** Draft a concise, professional email update for the project sponsor (VP of Sales). Lead with the most important information. **Format:** Use the following structure: * **Subject Line:** Project Phoenix Status Update - [[Date]] * **Executive Summary:** (2-3 sentences, state the overall RAG status and key message) * **Key Accomplishments This Period** * **Key Goals for Next Period** * **Risks & Blockers:** (Clearly state the issue, the impact, and the mitigation plan. Be specific about what you need from the recipient, if anything.) * **Budget & Schedule:** (Brief summary)

You are a communications coach preparing a project manager for a tough project review meeting. **Context:** The project is 15% over budget and one month behind schedule due to unexpected technical debt discovered during implementation. The project sponsor is not technical and is losing confidence. The goal of the meeting is to regain the sponsor's trust and secure approval for a revised plan. **Task:** Generate a list of key talking points for the project manager. Focus on framing the situation clearly, taking ownership, and presenting a credible path forward. **Format:** Organize the talking points into three sections: 1. **Acknowledge the Situation:** (How to state the facts without making excuses.) 2. **Explain the "Why":** (How to explain the root cause in non-technical terms.) 3. **Present the Path Forward:** (How to outline the revised plan, including new timeline, budget, and the controls you'll put in place to prevent recurrence.)

You are an expert communicator who can explain complex technical topics in simple, relatable terms. **Context:** A project update contains the following sentence: "We've encountered a cascading failure in the microservice authentication layer due to a race condition in the Redis cache, which is causing intermittent 503 errors." **Task:** Rewrite this sentence for an audience of non-technical business stakeholders. Explain the business impact. **Format:** Provide two versions: 1. **Simple Explanation:** A direct, one-sentence translation of the problem. 2. **Analogy:** A relatable analogy to help stakeholders grasp the concept. 3. **Business Impact:** A clear statement of what this means for users or the business.

You are a project manager drafting a formal communication about a change request. **Context:** The marketing team has requested to add a new "Social Media Sharing" feature to a product that is currently in the final testing phase. This was not in the original scope. **Task:** Draft an email to the project stakeholders explaining the change request. The goal is not to approve or deny it, but to inform them of the request and outline the formal change control process that will now begin. **Format:** The email should include: * A clear description of the requested change. * A statement that this is a change in scope. * An explanation of the next steps in the change control process (e.g., "Our team will now analyze the impact on timeline, budget, and resources, and present our findings to the change control board next week."). * Reassurance that no work will be done on the new feature until a formal decision is made.

You are a highly experienced and slightly pessimistic project manager who has seen everything go wrong. Your job is to anticipate problems before they happen. **Context:** Our project is to organize a company's first-ever, three-day international user conference in Lisbon, Portugal. The project involves logistics, marketing, content/speaker management, and sales. The timeline is 9 months. **Task:** Brainstorm a list of potential risks for this project. Think broadly across different categories. **Format:** Organize the risks into a markdown table with the following columns: **Risk Category** (e.g., Logistical, Financial, Reputational, Technical), **Risk Description**, and **Potential Cause**. Generate at least 15 risks.

You are a risk management specialist. **Context:** We've identified a risk for "Project Phoenix": "The primary data migration expert on the team may leave the company mid-project, as they are a contractor whose contract ends in 3 months." **Task:** Create a detailed risk register entry for this specific risk. Analyze it and propose response strategies. **Format:** Provide the following information: * **Risk ID:** (e.g., R001) * **Risk Description:** * **Risk Owner:** * **Impact Assessment:** (Score 1-5) * **Probability Assessment:** (Score 1-5) * **Risk Score:** (Impact x Probability) * **Risk Response Strategy:** (Choose from Avoid, Mitigate, Transfer, Accept) * **Specific Response Actions:** (e.g., For "Mitigate," list actions like "Begin knowledge transfer sessions immediately," "Document all migration processes," "Identify backup personnel.") * **Contingency Plan:** (What we will do if the risk occurs.)

You are a project manager who needs to escalate a critical issue to leadership. You must be concise, factual, and action-oriented. **Context:** A critical third-party component for our software build has been delayed by its vendor by 4 weeks. This completely blocks the main development path. The project is now projected to be 4 weeks late and incur $20,000 in team idle time costs. **Task:** Draft an issue escalation brief (no more than one page) for the VP of Engineering. **Format:** Use the following structure, leading with the most critical information: * **Subject:** URGENT: Decision Needed on Project X - Critical Vendor Delay * **The Ask:** (e.g., "Requesting your approval to authorize the 'Option 2' response by EOD Tuesday.") * **Issue Summary:** (1-2 sentences) * **Business Impact:** (What specific goals or deadlines are at risk?) * **Root Cause:** * **Proposed Options:** (Provide 2-3 options in a table with columns for **Option**, **Pros**, **Cons**, **Cost/Time Impact**.) * **Recommendation:** (Clearly state which option you recommend and why.)

You are a facilitator leading a "premortem" exercise. The goal is to imagine the project has failed, and then work backward to figure out what could have caused the failure. **Context:** Our project is to roll out a new mandatory time-tracking software to all 500 employees in the company. **Task:** Imagine it is six months from now, and the rollout has been a complete disaster. Adoption is below 10%, employees are complaining, and leadership is demanding to know what went wrong. Lead a brainstorming session by generating a list of plausible reasons for this failure. **Format:** List at least 10 distinct potential reasons for failure, grouped by category (e.g., Technical, Communication, Training, Political). For each reason, frame it as if it already happened. (e.g., "The software was not compatible with the sales team's mobile devices, so they never used it.")

You are a Scrum Master facilitating a sprint planning session. **Context:** * **Team:** 4 developers, 1 QA * **Sprint Length:** 2 weeks * **Team Capacity:** 120 story points (based on historical velocity) * **Product Backlog (Top 5 Items with Story Points):** 1. [[PBI-101]] Implement password reset flow (8 points) 2. [[PBI-102]] Add sorting to customer dashboard (5 points) 3. [[PBI-103]] Integrate with Stripe for payments (20 points) 4. [[PBI-104]] Fix login page CSS bug (3 points) 5. [[PBI-105]] Refactor user authentication service (13 points) **Task:** 1. Propose a sprint goal. 2. Select a set of Product Backlog Items (PBIs) for the upcoming sprint that respects the team's capacity. Justify your selection. 3. Break down the largest item selected ([[PBI-103]]) into smaller technical tasks for the development team. **Format:** * **Proposed Sprint Goal:** * **Proposed Sprint Backlog:** (List of PBIs and total story points) * **Task Breakdown for [[PBI-103]]:** (Bulleted list of technical tasks)

You are a Scrum Master trying to make the daily stand-up more effective and less robotic. **Context:** The team has fallen into a rut where the daily stand-up is just a monotone status report. I want to ask questions that encourage collaboration and problem-solving. **Task:** Generate a list of 10 alternative questions to the standard "What did you do yesterday? What will you do today? Any blockers?". The questions should be designed to uncover dependencies, foster teamwork, and focus on the sprint goal. **Format:** A numbered list of questions.

You are an experienced Agile Coach facilitating a sprint retrospective for a team that just finished a difficult sprint where they missed their goal. Team morale is low. **Context:** The goal is to have an honest but psychologically safe conversation about what happened and how to improve. **Task:** Design a 60-minute retrospective agenda. Choose a specific retrospective format (e.g., Starfish, 4Ls, Mad Sad Glad) and create questions to guide the discussion. **Format:** * **Retrospective Format:** (Name of the format) * **Agenda:** (Table with Time, Activity, and Purpose) * **Key Facilitation Questions:** (List of questions to ask during the main activity)

You are a Product Owner preparing for a backlog refinement session. **Context:** The team has a "Definition of Ready" (DoR) checklist that all user stories must meet before they can be pulled into a sprint. The DoR includes: * Story is clear and concise. * Acceptance criteria are defined. * Dependencies are identified. * Story is sized by the team. * UI/UX mockups are attached (if applicable). **Task:** Review the following draft user story and identify what is missing based on the Definition of Ready. Generate clarifying questions to ask the stakeholders to get the story ready. **Draft Story:** "As a user, I want to be able to search the site so I can find things." **Format:** 1. **DoR Analysis:** (Bulleted list of which DoR criteria are not met). 2. **Clarifying Questions:** (A list of questions for stakeholders to fill the gaps).

You are a project manager creating the final closure report for a major project. **Context:** * **Project:** "Project Phoenix" * **Original Goals:** Reduce CRM costs by 30%, improve data access. * **Final Outcome:** The project was completed 2 weeks late and 10% over budget. The new CRM is live. Early feedback is positive, and operational costs are projected to decrease by 25%. Data access has significantly improved. **Task:** Draft a comprehensive project closure report. **Format:** Include the following sections: * **Executive Summary:** (Overall outcome and key takeaways) * **Performance Analysis:** (A table comparing planned vs. actual for Scope, Schedule, and Budget) * **Achievement of Objectives:** (How well the project met its original goals) * **Lessons Learned:** (What went well, what didn't go well, and what to do differently next time) * **Final Sign-off:**

You are a PMO analyst creating a standardized survey to capture lessons learned from all completed projects. **Context:** The survey will be sent to all project team members and key stakeholders. The goal is to gather honest, constructive feedback. **Task:** Generate a list of 10 survey questions. Include a mix of quantitative (rating scale) and qualitative (open-ended) questions. **Format:** A numbered list of questions. Indicate the question type (e.g., Scale 1-5, Open Text).

You are a qualitative researcher. You have been given transcripts from five "lessons learned" interviews with project team members. **Context:** I will provide you with the transcripts. [[Paste transcripts here]]. **Task:** Read through all the transcripts and identify the top 3-5 recurring themes, both positive and negative. For each theme, provide 2-3 direct, anonymous quotes from the transcripts that support it. **Format:** **Theme 1:** [[Theme Title]] * Quote: "..." * Quote: "..." **Theme 2:** [[Theme Title]] * Quote: "..." * Quote: "...

You are my strategic advisor and an expert project manager. I am going to describe a difficult situation I'm facing on my project. I want you to listen, ask clarifying questions, and then help me brainstorm 3 potential courses of action, listing the pros and cons of each. Do not offer solutions until I have fully described the situation. Do you understand?

You are an expert editor and communications coach. I will provide a piece of text I have written (e.g., an email, a status report). Your task is to critique it and rewrite it to be more clear, concise, and impactful for an audience of [[describe audience]]. After you provide the rewritten version, give me a bulleted list of the specific changes you made and why. Here is the text: [[Paste text here]].

You are a career coach for project managers. Based on the latest industry trends, create a 90-day professional development plan for a project manager who wants to improve their skills in AI and data analytics. Include specific recommendations for online courses, books, certifications, and practical on-the-job activities. Format the plan as a week-by-week table.

You are a project management consultant specializing in team roles and responsibilities. Based on the following list of tasks and team roles, generate a RACI (Responsible, Accountable, Consulted, Informed) matrix. **Context:** * **Tasks:** 1. Draft Project Charter, 2. Approve Budget, 3. Develop Code, 4. Test Software, 5. Report Status to Executives. * **Roles:** Project Manager, Project Sponsor, Software Developer, QA Analyst, Business Analyst. **Task:** Create a markdown table with tasks as rows and roles as columns. Fill in each cell with R, A, C, or I. Provide a brief justification for your choices on the "Approve Budget" task.

You are a proposal manager with expertise in analyzing Requests for Proposal (RFPs). I will paste the text of an RFP. Your task is to extract and summarize the key information. **Context:** [[Paste RFP text here]] **Task:** Analyze the provided RFP text and extract the following information. **Format:** * **Client Name:** * **Project Objective:** (1-2 sentences) * **Key Deliverables:** (Bulleted list) * **Mandatory Requirements:** (BulAleted list of all "must," "shall," or "will" statements) * **Evaluation Criteria:** (How the proposal will be scored) * **Key Dates & Deadlines:** (Table with Item and Date) * **Questions for Client:** (List of ambiguities or points that need clarification)

You are an expert PMO director. Based on the following project brief, draft a complete project charter. **Project Brief:** - **Goal:** Launch a new mobile app for our e-commerce store. - **Scope:** Includes iOS and Android apps, integration with existing Shopify backend, user accounts, and push notifications. Out of scope: internationalization, loyalty program. - **Stakeholders:** Head of Marketing, Head of Engineering, CEO. - **Timeline:** 6-month target. - **Budget:** $250,000. **Output Format:** A markdown document with sections for: Project Goals, Scope (In/Out), Key Deliverables, Stakeholders, High-Level Timeline, Estimated Budget, and Potential Risks.

You are the Project Manager for 'Project Alpha'. Using the following raw data points, write a concise and professional weekly status update email for executive stakeholders. Adopt a confident but realistic tone. **Data Points:** - **Project Health:** Yellow (was Green). - **Completed this week:** User login feature, database schema finalized. - **Planned for next week:** Begin work on payment gateway integration. - **Blockers:** The design team is 2 days behind on providing the final mockups for the checkout flow. This puts the payment gateway work at risk. - **Budget:** 45% spent (40% planned). - **Action:** I am meeting with the Head of Design tomorrow to resolve the mockup delay. **Output Format:** An HTML email with a clear subject line, a top-line summary (Overall Status, Budget, Timeline), a section for 'Accomplishments', a section for 'Next Steps', and a section for 'Risks & Blockers' that clearly states the problem and my action plan.

You are an Agile coach. This is our sprint burndown data: Day 1: 50 points Day 2: 48 points Day 3: 47 points Day 4: 40 points Day 5: 39 points Day 6: 38 points Day 7: 38 points (weekend) Day 8: 38 points (weekend) Day 9: 30 points Day 10: 25 points The ideal line goes from 50 to 0. Analyze our progress. Are we on track? What are potential interpretations of the data, and what questions should I ask the team in our next daily standup?

You are an AI assistant with access to all project data for 'Project Phoenix'. Analyze the project's tasks, comments, change logs, and meeting transcripts. Generate a draft 'Lessons Learned' report. **Output Format:** A markdown document with three sections: 1. **What Went Well?** (Identify areas of high performance, positive feedback, and tasks completed ahead of schedule). 2. **What Could Be Improved?** (Identify bottlenecks, recurring issues from comments, tasks that were frequently delayed, and negative sentiment). 3. **Recommendations for Future Projects** (Provide 3-5 concrete, actionable recommendations based on the analysis).

Act as a senior project manager for a software development team. Our goal is to launch a new mobile app feature, "User Profiles V1," in Q4. The key components are front-end UI, back-end API, and database schema. Generate a full project plan as a task list with estimated durations, dependencies, and assignees for Design, Engineering, and QA.

Act as a senior automation consultant. I need to design a workflow for processing inbound leads from our website's contact form. **My Goal:** Qualify leads, enrich them with company data, notify the right sales rep, and add them to our CRM without manual intervention. **My Tools:** - Website Form: Webflow - Email: Google Workspace - Internal Chat: Slack - CRM: HubSpot - Data Enrichment: Clearbit **Your Task:** 1. **Outline the workflow step-by-step**, from the initial trigger to the final action. 2. **Identify the trigger and all necessary actions.** 3. **Specify where conditional logic (paths/filters) is needed.** For example, how do we handle personal emails vs. business emails? What if a lead is already in the CRM? 4. **Recommend the best primary automation tool** (Zapier, Make, or n8n) for this specific job, and justify your choice based on the complexity and tools involved. 5. **List all potential failure points** and suggest how to build error handling into the workflow.

Act as a senior project risk manager with 20 years of experience in the software development industry. You are an expert in Agile methodologies. Review the following project data: - **Project Goal:** [[Insert brief project description]] - **Meeting Transcript:** [[Paste a raw transcript of a recent team meeting]] - **Current Project Plan:** [[Paste a high-level summary of the project plan/timeline]] Based on this information, generate a draft risk register in a markdown table with the columns: 'Risk ID', 'Risk Description', 'Probability (Low/Medium/High)', 'Impact (Low/Medium/High)', and 'Potential Mitigation'. Focus specifically on identifying risks related to team morale, unspoken technical debt, and potential stakeholder misalignment mentioned in the transcript.

Act as an expert project manager. You are creating a detailed project plan to launch a new B2B SaaS feature called "AI Analytics Dashboard." The target launch date is 12 weeks from now. Your inputs are: - **Team:** 1 Product Manager, 2 Backend Engineers, 1 Frontend Engineer, 1 UX/UI Designer, 1 QA Tester. - **Key Deliverables:** 1. Finalized UX/UI mockups. 2. A functional backend that processes user data and generates insights. 3. A responsive frontend dashboard that visualizes the insights. 4. Full QA testing and bug-fix cycle. 5. Internal documentation for the support team. 6. A marketing launch announcement. Based on these inputs, generate a comprehensive project plan in a markdown table with the following columns: **Phase**, **Task**, **Owner (Role)**, **Estimated Duration (Weeks)**, and **Key Dependencies**. Organize the plan into logical phases (e.g., Discovery & Design, Development, Testing & Deployment, Launch).

Act as a senior project manager with PMP certification. Draft a comprehensive project charter for the following project. Ensure all key sections are included: Project Purpose, Measurable Objectives, High-Level Requirements, High-Level Risks, Summary Milestone Schedule, and a Stakeholder List. The output should be clear, concise, and ready for an executive kickoff meeting. **Project Details:** * **Project Name:** "Project Phoenix" - CRM System Implementation * **Goal:** Replace our legacy, on-premise CRM with a new cloud-based solution (Salesforce) for our 75-person sales team. * **Budget:** $250,000 * **Timeline:** 6-month target for full rollout. * **Key Stakeholders:** VP of Sales, Head of IT, Director of Customer Success.

Act as a strategic communications consultant. You are given a list of roles involved in a new software rollout project. Create a stakeholder register in a markdown table with the following columns: Stakeholder (Name/Role), Department, Influence (High/Medium/Low), Interest (High/Medium/Low), and Potential Expectations/Concerns. **Project Roles:** * CFO * VP of Sales * Sales Operations Manager * Individual Sales Reps (x75) * Head of IT * IT Security Analyst * Director of Customer Success * Marketing Manager

Act as an experienced risk management officer. For a project involving the migration of customer data from a legacy system to a new cloud-based CRM, brainstorm a list of at least 10 high-level risks. Categorize each risk into one of the following areas: Technical, Operational, Financial, or People.

Act as a PRINCE2-certified project manager. Generate a three-level Work Breakdown Structure (WBS) for a website redesign project. The major deliverables are: 1. Discovery & Design, 2. Development, 3. Content Migration, 4. Testing & QA, 5. Launch. Decompose each deliverable into major work packages and then into specific activities. Present the WBS in a nested list format.

Act as an expert Agile Product Owner. I will provide a feature request. Your task is to write three distinct user stories based on this request, each with at least three acceptance criteria written in the "Given-When-Then" format. **Feature Request:** "Users should be able to filter the product list on our e-commerce site. They need to be able to filter by price, color, and size.

Act as a certified risk management professional. Create a detailed risk register for a new office construction project. The output must be a markdown table with columns for: Risk ID, Description, Category, Probability (1-5), Impact (1-5), Risk Score (P*I), Mitigation Strategy, and Owner. Generate at least 5 detailed risks.

Act as a communications director. Using the stakeholder register provided below, draft a comprehensive communication plan. The plan should be a markdown table detailing: Stakeholder Group, Key Message, Communication Method (e.g., Email, Weekly Meeting, Dashboard), Frequency, and Owner. **Stakeholder Register:** * **Executive Leadership (CFO, VP):** High Influence, Low Interest. Need high-level status on budget and milestones. * **Sales & CS Leadership:** High Influence, High Interest. Need details on feature changes and training schedules. * **Sales Reps & CS Agents:** Low Influence, High Interest. Need hands-on training and clear instructions. * **IT Department:** Medium Influence, Medium Interest. Need technical specs and integration details.

Act as a senior program manager. Draft a weekly project status update email for executive stakeholders. The tone should be professional, concise, and focused on outcomes. Use the following bullet points as input. * **Project:** Project Phoenix (CRM Implementation) * **Status:** Green * **Last Week:** Completed data schema mapping, vendor contract signed. * **This Week:** Begin initial data migration tests, schedule developer environment setup. * **Blockers:** None. * **Decisions Needed:** None.

Act as an expert facilitator. Create a detailed agenda for a 60-minute project kickoff meeting for a new software development project. The attendees include the project sponsor, the development team, and the product owner. The agenda should include timings for each section, the topic, and the lead for that topic. Key sections to include are: Introductions, Project Vision & Goals, Scope Review, Roles & Responsibilities, and Next Steps.

You are an expert executive assistant. Read the following meeting transcript and provide a summary that includes: 1. A brief, one-paragraph overview of the discussion. 2. A bulleted list of all key decisions made. 3. A markdown table of all action items, with columns for "Action Item," "Owner," and "Due Date." **Transcript:** "[Paste your raw meeting transcript, notes, or recording summary here.]

Act as a PMO analyst. A change request has been submitted for our e-commerce website project. Draft an impact analysis. The output should be a structured document with sections for: 1. Change Request Description 2. Impact on Scope 3. Impact on Schedule (estimated days) 4. Impact on Budget (estimated cost) 5. Recommendation (Approve/Reject/Defer) **Change Request:** "The marketing team wants to add a customer reviews and ratings feature to the product pages. This was not in the original scope.

Act as a project manager. Draft a concise and professional email to a risk owner. The goal is to alert them that a risk's status has changed and to confirm they are activating the agreed-upon mitigation plan. * **Risk:** "Key vendor for API integration might deliver late." * **Risk Owner:** John Smith, Head of Engineering * **Trigger:** The vendor has missed their first internal milestone. * **Mitigation Plan:** "Begin parallel development of a temporary internal workaround.

Act as a program manager reporting to a steering committee. Generate a bi-weekly status report based on the following data. The report should have three sections: 1) Overall Status, 2) Key Accomplishments This Period, and 3) Top 3 Risks/Issues. **Data:** * **Overall Status:** Yellow (due to budget concerns) * **Schedule:** Green (on track for Dec 1 launch) * **Budget:** Red (15% overspent due to unexpected hardware costs) * **Accomplishments:** User Acceptance Testing (UAT) is 80% complete; Finalized training materials. * **Risks:** Budget overrun may impact Q4 feature enhancements.

Act as a PMO lead responsible for continuous improvement. Based on the raw notes from a project retrospective below, draft a formal lessons learned report. The report should have three sections: "What Went Well," "What Could Be Improved," and "Recommendations for Future Projects." Synthesize the notes into clear, actionable themes. **Retrospective Notes:** * "Daily stand-ups were efficient." * "The design team felt disconnected from the developers in the first half." * "We didn't get stakeholder sign-off on the mockups early enough, caused rework." * "UAT was smooth because the test scripts were excellent." * "Next time, we should have a shared channel for design and dev from day one.

Act as a project manager. Generate a final project closure report. The report should summarize the project's performance against its original goals. Include sections for: Final Scope, Final Schedule, Final Budget, and Overall Outcome. **Project Data:** * **Project:** "Project Phoenix" * **Original Goal:** Replace legacy CRM by Dec 1 for $250k. * **Final Scope:** All original scope delivered, plus an additional analytics dashboard. * **Final Schedule:** Launched Nov 15 (2 weeks early). * **Final Budget:** $240k ($10k underspend). * **Overall Outcome:** Successful. Sales team adoption is at 95%.

Act as a Scrum Product Owner. You are writing a user story for a development team. Use the following raw notes from a stakeholder meeting to create a complete user story. **Raw Notes:** "Users are getting lost. After they log in, they don't know where to go. We need some kind of main screen, a dashboard, that shows them their most recent projects and maybe their upcoming tasks. It should be the first thing they see after logging in. They need to be able to click on a project and go right to it." **Your Task:** 1. Write a user story with a clear title, role, goal, and benefit. 2. Draft at least 3-5 specific, testable acceptance criteria (AC) in Gherkin format (Given/When/Then). 3. Identify at least one potential dependency or question for the team to discuss.

Act as an experienced Scrum Master preparing for Sprint Planning. Our team has 5 engineers. The sprint is 2 weeks long (10 working days). **Team Availability:** - Engineer A: 100% - Engineer B: 100% - Engineer C: 5 days vacation (50% available) - Engineer D: 80% available (1 day per week on support) - Engineer E: 100% **Historical Data:** - Average velocity over last 3 sprints: 25 story points. **Your Task:** 1. Calculate the total available "person-days" for the upcoming sprint. 2. Adjust the historical velocity based on the calculated capacity to provide a forecasted capacity for this sprint. 3. Review the following PBI titles and flag any with potential risks (e.g., dependencies, new technology, ambiguity): - "Integrate with third-party payment gateway (Stripe)" - "Refactor user authentication module" - "Fix button alignment on contact page" - "Research new charting library for reporting dashboard