PMI CD-P study plan

Deconstruct the CD-P exam blueprint into a one-page domain map that states the weight of each domain and lists the tasks a citizen developer performs at each stage of the lifecycle

Practice writing problem statements that separate symptoms from root causes for three workplace scenarios, each in under 100 words

Identify the stakeholder roles (business sponsor, process owner, IT gatekeeper, data steward) in two real or realistic scenarios and record what each role must approve

Draft five discovery questions that would surface scope, data sensitivity, and integration constraints before any build starts

Convert three loosely stated business pain points into measurable success criteria with baseline, target, and time frame

Sketch a data model (entities, relationships, required fields) for a simple request-tracking app before opening any tool

Map the user journey of a single persona through that app and annotate where validation, notifications, and approvals occur

Compare build-versus-buy-versus-IT-ticket options for one scenario and justify the chosen path in writing

Compare the core capability categories of citizen developer platforms (low-code app builders, form and workflow tools, spreadsheet-to-app tools, RPA, and embedded BI) without assuming any single vendor

Explain how environments, solutions or containers, and publishing pipelines differ from a personal sandbox to a shared production workspace

Build a working two-table app with a form, a filtered gallery view, and one conditional field

Configure one role-based access rule and verify it by testing with a second account

Implement one automated workflow triggered by a record change and handle its failure path explicitly

Write test cases covering happy path, boundary values, blank required fields, and unauthorized access, then execute and log results

Apply input validation and error messaging that tells the user what to fix rather than only that something failed

Version the app by saving a named checkpoint and document what changed between versions

Design a UAT plan naming real users, scripts, acceptance thresholds, and a sign-off record

Assess the app against a data-classification checklist and flag any field holding personal, financial, or regulated data

Write a deployment runbook covering promotion steps, rollback, owner handoff, and support contact

Identify three risks of an unreviewed citizen app (orphaned ownership, shadow data copies, uncontrolled connectors) and pair each with a control

Draft a governance operating model that defines intake, tiered review by risk level, and post-launch ownership transfer

Build a tiering rubric that routes low-risk apps to self-service and high-risk apps to IT review, with explicit criteria

Prepare a five-slide business case for a sponsor that states cost, cycle-time saved, and residual risk

Rehearse a 10-minute stakeholder conversation in which IT raises a security concern and you respond with a concrete remediation plan

Rebuild the week-3 app in a second platform category to compare build effort, limits, and governance features

Diagnose and fix three deliberately introduced faults (broken filter, missing permission, misfiring trigger) and record root cause for each

Audit the app for delegation, connector credentials, and hard-coded values, then remediate at least two findings

Document an ALM routine for updating a live app without disrupting users

Complete two full-length timed practice sets and score each domain separately to expose weak areas

Re-teach the two lowest-scoring domains from your own notes without consulting the source material

Consolidate one-page summary sheets per domain covering key terms, decision rules, and common traps

Simulate the exam-day routine: review the summary sheets, then write out the lifecycle from intake to retirement from memory