| Course | PM FPX 5018 Project Management Foundations |
|---|---|
| Assessment | Assessment 1 |
| Paper type | Organizational project management analysis |
| Length | About 1,110 words, 5 pages |
| Format | APA 7 student paper |
| School | Capella University |
| Program | MS in Project Management |
| Updated | September 2026 |
Free sample paper for PM FPX 5018 Assessment 1
Project Management Maturity at a Regional Insurer: One Organization Described Precisely, a Named Frame to Measure Against, Practice Reported as It Is, Each Gap With Its Consequence, Causes in Structure and Incentives, and Graduate Sources Doing Real Work
Student Name
Capella University
PM FPX 5018: Project Management Foundations
Instructor Name
Month Day, Year
One Organization, Described Precisely
Great Plains Mutual, a composite regional property and casualty insurer, employs about 650 people and writes personal auto and homeowners policies in five Midwestern states. It runs about 40 projects a year: system upgrades, new product launches, regulatory changes, and process improvements. There is no project management office. Projects are led by business analysts or department managers as part of their regular jobs. Funding is approved annually within each department's budget. An executive committee reviews projects over 250,000 dollars. This assessment covers the operations division, which includes claims, underwriting, and policy services, and ran 22 of last year's projects with a combined budget of about 4.1 million dollars.
A Named Frame to Measure Against
The frame is Kerzner's (2019) project management maturity model, which describes five levels: common language, in which the organization recognizes the importance of project management and shares basic terms; common processes, in which it develops and uses consistent processes; a singular methodology, in which processes are integrated into one method; benchmarking, in which it compares its practice with others; and continuous improvement, in which it uses lessons and benchmarks to improve. Each level has characteristics that can be checked against evidence, which makes it more useful here than a general description of good practice.
Practice Reported as It Is
Evidence came from project documents for 22 projects, interviews with 12 project leads and 4 executives, and last year's financial results by project, gathered over six weeks in the spring by the assessor, who is not part of the division. Practice as found: 9 of 22 projects had a written charter; terms such as scope, baseline, and change request were used inconsistently, with "scope" meaning the budget in some departments and the requirements in others; status was reported in each department's own format, from spreadsheets to email summaries; 6 of the 14 projects completed last year finished more than 20% over budget; no project had a lessons-learned record; and project leads had no formal training in project management, apart from 2 who had earned certifications on their own. A department that uses "scope" to mean the budget and another that uses it to mean requirements are not managing the same thing.
Each Gap Carries Its Consequence
Measured against the model, Great Plains' operations division is at an early stage of the first level, common language, with some elements missing. Gap 1, no shared vocabulary: consequence, executives cannot compare project status across departments, and at least two projects were approved with different understandings of what they would deliver. Gap 2, charters for fewer than half of projects: consequence, projects without charters were twice as likely to finish more than 20% over budget, 5 of 8 compared with 1 of 6 among chartered projects that finished. Gap 3, no common status format: consequence, the executive committee spends most of its monthly meeting clarifying reports rather than making decisions. Gap 4, no lessons learned: consequence, the same integration problem with the policy administration system delayed three projects in two years. Gap 5, no training: consequence, project leads rely on personal experience, which varies widely.
Causes Traced Into Structure and Incentives
The gaps are not caused by individual project leads, and they would not be fixed by training alone. Structure: projects are funded within department budgets, so no one owns the portfolio across departments, and there is no function responsible for common methods. Project leads report to department managers whose priorities are operational, so project work loses when it competes with daily work. Incentives: department heads are evaluated on staying within their annual budgets, not on project outcomes, so a project that finishes over budget is absorbed quietly rather than examined. Shenhar and Dvir (2007) argue that projects should be managed with attention to business results, not only to time and budget; at Great Plains, neither results nor budget adherence is measured at the project level, which leaves no pressure to improve.
What Maturity Would Require Here
Reaching the model's first level fully and moving toward the second would require a shared vocabulary and minimal standard documents, charter, status report, and closeout with lessons, applied to every project over a threshold, and someone accountable for maintaining them. Kerzner (2019) notes that organizations often try to jump to a full methodology before establishing common language, and that such efforts tend to fail because the underlying understanding is missing.
What Would Show Progress
Progress toward the first and second levels would show in measures the division can collect: the share of projects over 100,000 dollars with an approved charter, rising from 9 of 22 toward all of them; one status format used by every project reported to the executive committee; a closeout record with lessons for every completed project; and the share of projects finishing more than 20% over budget, which should fall as charters and status reporting improve. These measures are simple enough to track without a new office, which matters in an organization with no project management function.
Who Would Need to Act
Because the causes sit in structure and incentives, the actions belong to the executive committee, not to project leads. The committee controls funding, sets department heads' objectives, and could name an owner for common project methods. Project leads can adopt better practices on their own, and some have, but without a change at the top their efforts remain isolated. The assessment is therefore addressed to the committee, with the project leads' interviews as evidence.
Limits of the Assessment
The assessment covers one division and one year. It relies on documents that exist; projects with poor documentation may have been managed better than the records show. The comparison of chartered and unchartered projects involves small numbers and does not prove that charters caused better outcomes; projects with charters may also have had more engaged sponsors. A second year of data, collected with the same measures, would give a firmer view.
Conclusion
Great Plains' operations division sits at the start of the first maturity level, with inconsistent terms, few charters, no common reporting, no lessons learned, and no training. Each gap has a measurable consequence, including more frequent budget overruns on unchartered projects. The causes lie in departmental funding, reporting lines, and incentives that do not measure project outcomes, which is where improvement must begin.
References
Kerzner, H. (2019). Using the project management maturity model: Strategic planning for project management (3rd ed.). Wiley.
Shenhar, A. J., & Dvir, D. (2007). Reinventing project management: The diamond approach to successful growth and innovation. Harvard Business School Press.
What the PM FPX 5018 Assessment 1 instructions ask for
The first assessment in PM FPX 5018 asks you to analyze how an organization manages projects. You describe the organization, including its sector, size, structure, governance and project portfolio, choose a framework to measure against, such as the PMI Organizational Project Management Maturity Model or a comparable standard, report how projects are actually run, identify gaps between practice and the framework, explain the consequences of each gap and trace their causes into structure, incentives and culture. At the graduate level, sources should include peer-reviewed research on project management maturity, used to support claims rather than decorate them.
Inside the PM FPX 5018 Assessment 1 example
The example fixes the organization first and never lets it drift. It opens with the case: sector, size, structure, governance and the project portfolio the organization runs. The second block establishes the analytical frame, naming the standard or maturity model the practice will be measured against and citing it, which is the move that separates graduate work from an account of a workplace. The third block reports current practice across authorization, planning, execution, control and closure, with evidence for each claim. The fourth block sets that practice beside the frame and states the gaps, each with the consequence the organization is already living with. The fifth block explains why the gaps exist, reaching into structure, culture and incentives rather than stopping at insufficient training. The closing block states which gap matters most and prepares the argument the next assessment has to make.
Where the marks sit in the PM FPX 5018 Assessment 1 scoring guide
The scoring guide looks at how the organization is described, the framework, the account of practice, the gaps, the causes and the use of sources. The description reaches Distinguished when precise enough to anchor every later claim. The framework scores higher when named and used consistently as the standard. Practice earns credit when reported as it is, with examples, not as policy says it should be. Each gap is expected to come with its consequence, such as late product launches or budget overruns. Causes should reach into structure and incentives, like project managers without authority over staff. Graduate sources should do real work in the argument. Proficient analyses list gaps; Distinguished ones explain why the gaps persist and who could close them.
Common PM FPX 5018 Assessment 1 mistakes, and how to avoid them
Maturity analyses often describe the organization's official process and treat it as practice, which hides the gaps the assessment is meant to find. Another weakness is listing gaps without saying what each one costs the organization. Causes are attributed to poor project managers rather than to the structures that shape their behavior. The framework is named once and then forgotten. Sources are cited for definitions only. The organization drifts, with examples drawn from different companies. Holding to one organization throughout, measuring each area against the chosen framework and giving every gap a consequence and a cause, produces an analysis a sponsor could act on and prepares the methodology choice in Assessment 2.
Get a PM FPX 5018 Assessment 1 example written to your instructions
Upload the Assessment 1 instructions and the scoring guide from your PM FPX 5018 courseroom, plus the organization you have chosen or been assigned. We write a custom example to those criteria, framed against a cited standard and sourced at graduate level, and return it in 24 to 48 hours. The first is free of charge. The paper above is an original model document written by our desk, not a submitted student paper and not an official Capella University document.
More PM FPX 5018 papers and MS in Project Management samples
- PM FPX 5018 Assessment 2: Methodology Comparison
- PM FPX 5018 Assessment 3: Professional Practice Paper
PM FPX 5018 Assessment 1 questions, answered
Can I write about my own employer?
In many sections yes, and it usually produces a sharper paper, provided your instructions allow it. Keep confidential material out, describe roles rather than individuals, and be explicit that part of your evidence is personal observation. Where you can support a claim with published material about the organization or its sector, do that as well, since a graduate criterion is reading for support.
How is PM FPX 5018 different from an introductory project management course?
The unit of analysis changes. An introductory course asks what the practices are; this one asks which approach fits a particular organization and why, and expects the answer defended with scholarly sources. Explaining process groups or knowledge areas earns little here. The graduate criteria are reading for judgment about a case, supported by literature you have actually engaged with.
What sources count at this level?
Peer-reviewed research, recognized professional standards, and organizational or sector material that can be verified. Practitioner blogs and vendor pages can orient you, but they cannot carry a load-bearing claim in a graduate paper. Check your instructions for the number and recency expected, and keep every source in the text doing work rather than sitting in the reference list.
Where can I find a free PM FPX 5018 Assessment 1 sample paper?
The full maturity analysis of the regional insurer is on this page, with a named framework, practice reported as it is, each gap carrying its consequence and causes traced into structure and incentives.
What is a project management maturity model in PM FPX 5018 Assessment 1?
A framework describing levels of capability in how an organization manages projects, from ad hoc to optimized. The analysis measures current practice against it to find gaps.