Problem Statement
The goal is to help a Head of Information Systems convert initiative details into a structured, enterprise‑grade delivery plan. The workflow must translate high‑level program inputs into actionable scope, milestones, RAID items, RACI assignments, communications planning, and operational readiness artifacts. This ensures predictable delivery, vendor alignment, and clear accountability across teams.
Steps
Ingest Initiative Inputs
INGESTCollect and parse the initiative summary, participating teams, constraints, key dates, and vendor dependencies. Normalize the input into structured fields for downstream processing.
Define Scope and Boundaries
EXECUTEAnalyze inputs to produce a clear, bounded scope statement with in-scope and out-of-scope items. Ensure alignment with constraints such as budget, timelines, and vendor obligations.
Generate Milestones and Acceptance Criteria
EXECUTECreate milestone stages aligned to the initiative’s timeline and dependencies. Each milestone includes measurable acceptance criteria and identifies required teams or vendors.
Build RAID Log and RACI Matrix
EXECUTEIdentify risks, assumptions, issues, and dependencies from the input and inferred factors. Assign Responsible, Accountable, Consulted, and Informed parties, ensuring each deliverable has a single accountable owner.
Produce Communications and Readiness Plans
EXECUTEDraft a stakeholder-specific communications plan and an operational readiness checklist including training, SLAs, cutover steps, and rollback criteria.
Validate Plan for Completeness
EXECUTECheck that scope is bounded, milestones have acceptance criteria, RACI has one accountable per item, communications target all stakeholders, and readiness includes cutover and rollback steps.
Prompt Configurations
Enterprise Delivery Plan Generator
You are an enterprise delivery coordinator. Using the provided initiative summary, teams, constraints, key dates, and vendor dependencies, generate the following outputs in a structured, enterprise-focused tone: (1) delivery plan with scope boundaries and milestones (each with acceptance criteria), (2) RAID log, (3) RACI matrix with exactly one accountable per deliverable, (4) stakeholder-tailored communications plan, and (5) operational readiness checklist including training, SLAs, cutover steps, and rollback criteria. Do not invent data not supported by the input. Make reasonable inferences typical for large IT programs and clearly label each section.
Example Inputs/Outputs
Initiative: Implement new HRIS system. Teams: HR, IT Apps, InfoSec, Vendor Implementation Team. Constraints: Go-live by Q3, limited HR resources, fixed vendor budget. Key dates: Data migration window in July. Vendor dependencies: SLA requires 10-day turnaround for configuration changes.
Generated plan including a bounded scope (HRIS deployment for core HR only, excluding payroll), milestones (configuration, data migration, UAT, cutover), RAID items (risk: limited HR availability), a RACI matrix with HR Director as accountable for UAT, communications plan for HR staff and executives, and readiness checklist including training, vendor SLA confirmation, and rollback strategy.