Prompt Details
Model
(v3)
Token size
280
Example input
[USER WILL PASTE THEIR PROJECT DETAILS HERE]: We are building a mobile banking app. Team of 8 developers, 2 QA engineers, 1 UX designer. Deadline: 5 months. Budget: $500,000. Must integrate with existing backend APIs.
Example output
Project Description: "We are building a mobile banking app. Team of 8 developers, 2 QA engineers, 1 UX designer. Deadline: 5 months. Budget: $500,000. Must integrate with existing backend APIs."
RISK REGISTER
Risk #1: API integration delays due to undocumented endpoints
Category: Technical
Probability: High | Impact: High | Score: 9 | Priority: 1
Risk #2: UX design changes causing development rework
Category: Scope
Probability: Medium | Impact: High | Score: 8 | Priority: 2
Risk #3: QA capacity insufficient for full regression testing
Category: Resource
Probability: High | Impact: Medium | Score: 6 | Priority: 3
Risk #4: Third-party vendor security audit delays
Category: External
Probability: Medium | Impact: Medium | Score: 4 | Priority: 4
Risk #5: Team burnout due to tight deadline
Category: Resource
Probability: Medium | Impact: Medium | Score: 4 | Priority: 5
TOP 5 RISK MITIGATION STRATEGIES
Risk #1: API Integration Delays
Mitigation: Start integration testing in Month 2, not Month 4. Assign dedicated backend developer to audit API documentation immediately.
Contingency: Build mock API endpoints for critical services in case real APIs are delayed.
Trigger: If API documentation is not finalized by end of Week 2, escalate to vendor management.
Risk Owner: Lead Backend Developer
Risk #2: UX Changes
Mitigation: Freeze designs by end of Month 1. Implement a "change request" process requiring PM approval for any UX changes.
Contingency: Allocate 2 weeks of buffer at the end of the project for design-related rework.
Trigger: More than 3 UX change requests in a single week.
Risk Owner: UX Designer & PM
Risk #3: QA Capacity
Mitigation: Hire 1 contract QA engineer for Months 4-5. Prioritize test automation from Day 1.
Contingency: Reduce scope of non-critical features to allow more QA time for core functionality.
Trigger: QA team reports more than 20% test cases not executed in Week 3.
Risk Owner: QA Lead
EXECUTIVE SUMMARY
Overall risk profile is MODERATE-HIGH. Two critical risks (API integration and UX changes) require immediate attention. If mitigated early, the project has a 75% chance of meeting the 5-month deadline. Recommend weekly risk review meetings with the full team.
By purchasing this prompt, you agree to our terms of service
V3
PMP-Grade Risk Analysis in Seconds.
This prompt turns your project description into a professional risk register. Includes:
• Risk identification across 5 categories
• Priority scoring (Probability × Impact)
• Actionable mitigation strategies
• Contingency plans & red flags
Designed by a PMP-certified manager with Adobe & Aylo experience. Ideal for software, IT, and product projects.
Copy, paste, and mitigate risks like a pro.
...more
Added 2 weeks ago
