PMP project description examples
Four complete example project descriptions for the PMP application, covering IT, construction, a military fielding, and an agile software project, with notes on why each works.
Reading a few finished descriptions is the fastest way to understand what a good one looks like. The four below are invented for illustration. They follow the eight-part structure explained in the guide to writing project descriptions.
Do not copy them. PMI reviewers see the same borrowed phrases again and again, and your description has to be true of your own project. Use these to see the shape, then write about what you actually did.
Example 1: IT system migration (predictive)
The overall objective of the project was to migrate 240 employees at four offices from an on-premises email server to a cloud email service within five months, with no more than four hours of downtime per office. As the project manager, I was responsible for the full life cycle of the project from business case to closure. I developed the plan, led a team of six, and was accountable to the chief operating officer for scope, schedule, and budget. The key deliverables of the project were a project charter, a migration plan, a communications plan, a risk register, the migrated mailboxes, user training sessions, and a decommissioning report for the old server. While working with stakeholders, I interviewed office managers to capture requirements, agreed cutover dates with each office, and issued weekly status reports to the executive sponsor. While working with my team, I assigned roles to two engineers, a trainer, and three office coordinators, ran weekly planning meetings, and resolved a dispute over cutover sequencing by reviewing the dependencies with the team. While working on the project, I built and baselined the schedule, tracked spending against a budget of $85,000, managed the vendor's migration service under a fixed-price contract, and verified each office against a quality checklist before sign-off. Throughout the project, I confirmed data retention requirements with legal counsel, processed three change requests through the change board, and updated the risk register as issues arose. The overall outcome of the project was a success. The project resulted in all 240 users migrated two weeks early and 6 percent under budget, with a maximum downtime of three hours.
Why it works. The objective contains numbers a reviewer can hold on to. The budget, the contract type, and the change board show process without a lecture on methodology. The result answers the objective point for point.
Example 2: Construction fit-out (predictive)
The overall objective of the project was to convert 1,100 square meters of leased warehouse space into a temperature-controlled storage facility within 26 weeks and a budget of $1.4 million. As the project manager, I was responsible for delivering the project on behalf of the tenant from design approval through handover. I coordinated the design consultant, general contractor, and landlord, and I reported monthly to the operations director. The key deliverables of the project were an approved scope statement, a master schedule, a procurement plan, a cost report, the completed facility, commissioning records, and an operations handover package. While working with stakeholders, I held coordination meetings with the landlord and the local building authority, clarified approval requirements early, and kept the tenant's operations team informed of dates that affected their move. While working with my team, I set expectations with the site superintendent and subcontractor leads, held weekly site meetings, and mediated a sequencing conflict between the mechanical and electrical trades. While working on the project, I managed the schedule using critical path analysis, reviewed contractor payment applications against progress, and controlled quality through staged inspections. Throughout the project, I tracked permit and safety compliance, managed risk through a weekly review, and handled a supplier delay by approving an alternate product through the change process. The overall outcome of the project was a success. The project resulted in handover in week 25 at $1.37 million, and the facility passed commissioning on the first attempt.
Why it works. Construction descriptions often drown in technical detail. This one mentions the trades once and spends its words on coordination, approvals, cost, and risk.
Example 3: Military equipment fielding (hybrid)
This is how a fielding might read after the military terms have been translated. The glossary shows the translations used.
The overall objective of the project was to field a new satellite communications system to a 600-person organization, replacing 18 legacy terminals and qualifying 40 operators within six months. As the project manager, I was responsible for planning and leading the fielding from the initial notification through the final transfer of equipment accountability. I led a team of nine and reported to the organization's senior leader. The key deliverables of the project were a fielding plan, a training schedule, a risk assessment, updated property records, 18 operational terminals, 40 qualified operators, and revised operating procedures. While working with stakeholders, I coordinated with the equipment program office, the supply and training departments, and five subordinate teams, and I briefed senior leadership every two weeks to keep expectations aligned. While working with my team, I assigned clear responsibilities to section supervisors, held a short daily coordination meeting during the delivery phase, and resolved competing demands on the same operators between two teams. While working on the project, I sequenced deliveries and training around the organization's existing commitments, tracked progress against milestones, and adjusted the plan in two-week increments as delivery dates shifted. Throughout the project, I confirmed security and accountability requirements, maintained a risk register, raised a delayed shipment to leadership for a decision, and recorded lessons learned for the next fielding. The overall outcome of the project was a success. The project resulted in all 18 terminals operational and 40 operators qualified one month early, with full accountability of the turned-in equipment.
Why it works. There is not a single acronym. "Senior leader", "section supervisors", and "the equipment program office" tell a civilian reviewer exactly who was involved without naming a unit or a rank.
Example 4: Software product (agile)
The overall objective of the project was to deliver a mobile ordering feature for a regional restaurant group's existing app, serving 22 locations, within a four-month release window. As the project lead, I was responsible for guiding a cross-functional team of eight from discovery through launch. I facilitated planning, managed the release plan, and represented the team to the product sponsor. The key deliverables of the project were a product vision statement, a prioritized backlog, a release plan, working software increments every two weeks, a test summary, and a launch readiness checklist. While working with stakeholders, I ran discovery workshops with restaurant managers, agreed priorities with the sponsor at each review, and shared progress through fortnightly demonstrations. While working with my team, I facilitated sprint planning and retrospectives, helped the team agree working norms, and cleared impediments such as a blocked payment sandbox. While working on the project, I managed scope through backlog prioritization by customer value, tracked velocity to forecast the release date, and coordinated a payment vendor's integration work. Throughout the project, I confirmed payment security requirements with the compliance lead, tracked risks on a visible board, and adapted the release plan when an app store policy changed. The overall outcome of the project was a success. The project resulted in launch at all 22 locations on the planned date, and mobile orders reached 14 percent of sales within eight weeks.
Why it works. It uses agile vocabulary where it is accurate and still shows planning, scope control, and risk. Notice "project lead" in the second sentence. If you were not called a project manager, you can say what you were.
A weak example, and how to fix it
I was the project manager for the network upgrade. I was responsible for all aspects of the project including planning, executing, monitoring and controlling, and closing. I worked with stakeholders and managed the team. I managed risks, issues, scope, schedule, and cost. The project was completed successfully.
Every statement may be true, and none of it shows anything. There is no objective, no number, no deliverable, and no sign of what the applicant actually did. It also reads as a list of textbook terms, which is the pattern reviewers are most used to seeing.
To fix a description like this, go through it sentence by sentence and ask "such as?". "I worked with stakeholders" becomes "I agreed the outage windows with the three department heads". "I managed risks" becomes "I kept a risk register and arranged a spare circuit after identifying the single carrier as the main threat".
Patterns worth copying
- A number in the first sentence and a matching number in the last.
- Deliverables listed as nouns.
- One specific incident somewhere in the middle: a conflict, a delay, a change.
- Leadership verbs throughout.
- No acronyms that a stranger would have to look up.
When you are ready to write your own, the drafting tool can turn your notes into a first draft in this format.