| Course | PM FPX 1000 Project Management Principles |
|---|---|
| Assessment | Assessment 2 |
| Paper type | Project life cycle overview |
| Length | About 1,140 words, 6 pages |
| Format | APA 7 student paper |
| School | Capella University |
| Program | BS in Business, Project Management |
| Updated | September 2026 |
Free sample paper for PM FPX 1000 Assessment 2
Choosing a Life Cycle for a Customer Portal Project: One Life Cycle Adopted, Phases With Exit Deliverables, Criteria Stated Before the Choice, the Rejected Alternative Taken Seriously, and What the Chosen Approach Costs
Student Name
Capella University
PM FPX 1000: Project Management Principles
Instructor Name
Month Day, Year
The Project
Prairie Gas Supply, the composite propane distributor from the proposal memo, has approved its portal project: roughly 14,000 households will be able to book deliveries, check what they owe, and settle bills online, with the portal tied into billing and dispatch. The budget is about 140,000 dollars, the portal must be live by November 1 before the winter peak, and the work will be done by a vendor configuring its existing portal platform plus Prairie Gas's IT staff building the integrations.
Choice Criteria Stated Before the Choice
The criteria were written down before any life cycle was chosen, so the choice could be checked against them. Criterion 1, fixed deadline: go-live cannot slip past November 1, because a late portal misses the season that justifies it. Criterion 2, stability of requirements: how well the features can be defined at the start. Criterion 3, vendor contract: the vendor prices its work as a fixed-fee configuration with defined deliverables. Criterion 4, integration risk: the 12-year-old billing system must be connected, and its behavior is only partly documented. Criterion 5, customer involvement: whether customers or staff can give feedback during the build.
One Life Cycle Adopted, Not Surveyed
The project adopts a predictive life cycle, in which scope, schedule, and cost are planned at the start and work proceeds through defined phases. The Project Management Institute (2021) describes predictive approaches as suited to projects where requirements can be defined early and change is expected to be limited. The portal's features are well understood: they match what the service center does today and what competitors offer. The vendor's fixed-fee contract depends on defined deliverables. The deadline is fixed. Only criterion 4, the integration risk, argues for more flexibility, and it is handled inside the predictive plan, as described below. The paper adopts one life cycle and defends it, rather than describing four and choosing none.
Phases Carry Exit Deliverables
Each phase ends with a deliverable that must be accepted before the next phase begins. Phase 1, initiation, October to November: exit deliverable, the signed project charter. Phase 2, requirements, December to January: exit deliverable, a requirements document listing every portal function, approved by the sponsor and the customer service, dispatch, and finance leads. Phase 3, integration discovery, January to February: exit deliverable, a working test connection that reads a sample customer's balance from the billing system and posts a test payment. This phase is placed early because it carries the most risk. Phase 4, configuration and integration build, March to July: exit deliverable, a complete portal in a test environment connected to test copies of billing and dispatch. Phase 5, testing, August to September: exit deliverable, a test report showing all critical test cases passed and user acceptance by six service representatives and 20 volunteer customers. Phase 6, launch, September to October: exit deliverable, the portal live for all customers, with 500 customers invited to use it first during September. Phase 7, closeout, November: exit deliverable, a closeout report and handover to operations.
Handling the Integration Risk Inside the Plan
The integration risk is the reason an adaptive approach was considered, and the predictive plan responds to it without abandoning the approach. Phase 3 is a short discovery phase that proves the connection works before the vendor configures the full portal. If it fails, the sponsor learns in February, with eight months left, rather than in August. This borrows the idea of early learning from adaptive approaches while keeping the fixed-scope, fixed-fee structure the vendor contract requires.
The Rejected Alternative Handled Seriously
An adaptive, iterative approach was the main alternative and deserves a fair hearing. Its strengths are real: it would deliver working portal features every few weeks, let customers try them early, and adjust priorities as the team learns. If Prairie Gas were building a portal from scratch with uncertain customer needs, it would likely be the better choice. It was rejected for three reasons tied to the criteria. First, the vendor's pricing is fixed-fee for defined deliverables, and an adaptive contract would be time-and-materials, which the sponsor's budget authority of 150,000 dollars does not easily accommodate. Second, the features are stable and well understood, so the main benefit of adaptive work, discovering what users want, is smaller here. Third, the IT staff who would build integrations are also responsible for running daily operations and cannot commit to continuous sprint cycles through the winter. The rejection is specific to this project, not a judgment that adaptive approaches are worse. Adaptive work would be the right choice for a different portal. It is not the right choice for this one.
How the Phases Connect to the Contract
The vendor contract mirrors the phases. The vendor is paid 20% on approval of requirements, 20% on a working test connection at the end of integration discovery, 40% on delivery of the complete test portal, and 20% after launch. Tying payments to phase deliverables gives Prairie Gas leverage if a phase slips and gives the vendor a clear definition of done at each step. It also means the sponsor's approval at each gate has financial weight, which keeps gate reviews from becoming formalities.
Who Approves Each Gate
The sponsor approves the charter and the requirements document. The project manager and IT lead jointly approve the integration discovery result, because it is a technical judgment, and report it to the sponsor. The sponsor approves the move to launch after reviewing the test report. Naming who approves each gate prevents the common failure in which phases blur together because no one formally closed the previous one.
What the Chosen Approach Costs
The predictive approach has costs, stated openly. Customers will not see the portal until September, so feedback arrives late, and changes found in user acceptance testing will be expensive or deferred. The requirements phase takes about two months of staff time, roughly 120 hours from customer service, dispatch, and finance leads. Any change after requirements approval must go through a change process, which slows responses to new ideas. If the integration discovery phase reveals problems, the fixed plan may need to be rebaselined, with sponsor approval.
Conclusion
The portal project adopts a predictive life cycle with seven phases, each ending in a defined deliverable, because the deadline is fixed, requirements are stable, and the vendor contract is fixed-fee. Integration risk is handled by an early discovery phase. An adaptive approach was taken seriously and rejected for reasons specific to this project, and the predictive approach's costs, late customer feedback and slower change, are stated.
References
Project Management Institute. (2021). A guide to the project management body of knowledge (PMBOK guide) (7th ed.). Project Management Institute.
PM FPX 1000 Assessment 2 instructions, in plain terms
Assessment 2 in PM FPX 1000 has you choose and describe a project life cycle for the project from Assessment 1. You set out the criteria for choosing, such as how stable the requirements are, how much the customer needs to see early versions and contract terms, select a predictive, iterative, incremental, agile or hybrid life cycle, describe its phases and what each produces, explain who approves the move from one phase to the next and discuss the alternative you rejected. The PMBOK Guide and texts on project life cycles support the choice. The overview should read as a decision, not a catalog of models.
How this PM FPX 1000 Assessment 2 example is built
The example is ordered so the choice arrives before the detail. It opens by naming the project and the life cycle selected in a single sentence, which prevents the paper from reading as a catalog of models. The second part sets out the criteria used to choose, such as how stable the requirements are and how expensive a late change would be. The third part is the phase map, and it is the longest, since each phase needs its work, its exit deliverable and its decision point. The fourth part runs the comparison, taking the strongest rejected alternative and saying exactly where it would have failed this project. The closing part names the risk the chosen life cycle carries and what the manager does about it, because every life cycle costs something.
Reading the PM FPX 1000 Assessment 2 scoring guide
The scoring guide rates the criteria, the choice, the phases, the gates, the treatment of the alternative and the costs. Criteria reach Distinguished when stated before the choice, so the choice follows from them. The choice scores higher when one life cycle is adopted and justified for this project. Phases earn credit when each ends with a named deliverable. Gates are judged on whether an approver is named for each. The rejected alternative should be treated fairly, with its strengths acknowledged. Costs of the chosen approach, such as less flexibility, should be stated. Proficient overviews describe a life cycle; Distinguished ones show why it fits this project better than the alternatives.
Common PM FPX 1000 Assessment 2 mistakes, and how to avoid them
Life cycle papers often describe four or five models in turn and choose one at the end, which reads as a survey instead of a decision. Another weakness is choosing agile because it is popular, without checking whether the contract or the requirements suit it. Phases are listed without deliverables, so no one knows when a phase is done. Gate approvals are missing. The rejected option is dismissed in a sentence. The costs of the choice go unmentioned, as if one life cycle had no drawbacks. A table of phases with the deliverable, the approver and the approximate duration for each makes the overview concrete and leads into the constraint analysis in Assessment 3.
Get a PM FPX 1000 Assessment 2 example written to your instructions
Send the Assessment 2 instructions and the scoring guide from your PM FPX 1000 courseroom, along with the project you carried through the first assessment. We write a custom example to those criteria, with the phase map and the fit argument worked out, and return it in 24 to 48 hours. The first custom sample is free. 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 1000 papers and BS in Business, Project Management samples
- PM FPX 1000 Assessment 1: Project Selection Memo
- PM FPX 1000 Assessment 3: Constraint Analysis
- PM FPX 4000 Assessment 2: Domain Analysis
- PM FPX 4080 Assessment 2: Sprint Plan
- PM FPX 4020 Assessment 2: Scope Statement
- PM FPX 4070 Assessment 2: Statement of Work
PM FPX 1000 Assessment 2 questions, answered
Can I use the same project from Assessment 1?
In many sections that is the intent, and it helps, because the life cycle argument then rests on a project the reader already understands. Confirm it in your instructions first. If you do carry it forward, rewrite rather than paste, since the earlier memo argued that the work is a project and this one argues how it should be phased.
Is a predictive life cycle a weaker answer than an agile one?
No. The stronger answer is the one that matches the work. Construction, regulated implementations and projects with fixed contractual deliverables are usually better served by a predictive arrangement, while unstable requirements and early user feedback favor adaptive work. What the criterion rewards is the reasoning attached to the choice, not the fashionableness of the model.
How many phases should the overview show?
As many as the work genuinely has, which for most course projects lands between four and six. The count matters less than whether each phase produces something and ends at a decision. Phases invented to fill a diagram tend to have no exit deliverable, and an empty phase is visible to a reader immediately.
Where can I find a free PM FPX 1000 Assessment 2 sample paper?
This page holds the complete life cycle overview for the customer portal, with criteria stated first, one life cycle adopted, phases with exit deliverables, gate approvers and the rejected alternative taken seriously.
What is a hybrid life cycle in PM FPX 1000 Assessment 2?
An approach that combines predictive planning for parts of the project with stable requirements and iterative or agile methods for parts that are still changing, such as the portal's user interface.