Project Life Cycle Phases PK0-005 Practice Quiz

• A. To provide the justification for undertaking the project, documenting the business need, expected benefits, estimated costs, risks, and the decision criteria that authorize the investment of organizational resources
• B. To assign team members to the project and define their individual responsibilities
• C. To create the project schedule with all tasks, milestones, and dependencies
• D. To define the technical architecture and technology stack for the solution

BUSINESS CASE: the foundational document created in the discovery/concept phase that answers the question 'WHY should we do this project?' BUSINESS CASE COMPONENTS: PROBLEM/OPPORTUNITY STATEMENT: what problem is being solved or opportunity being captured?; BUSINESS OBJECTIVES: what specific, measurable outcomes are expected?; BENEFITS ANALYSIS: quantitative (revenue increase, cost savings, efficiency gains) and qualitative (customer experience, competitive positioning, regulatory compliance); COST ESTIMATES: total investment required (capital + operational costs); OPTIONS ANALYSIS: multiple approaches considered with trade-offs; RISKS: key risks and uncertainties; ROI / FINANCIAL ANALYSIS: return on investment, payback period, NPV, IRR; RECOMMENDATION: which option is recommended and why. PURPOSE: enables decision-makers (sponsors, steering committees, executives) to approve or reject the project authorization; ensures organizational resources are invested in projects that deliver sufficient value; provides the strategic rationale that will govern the project throughout its lifecycle.

• A. ROI = 25%, for every $1 invested, the project returns $0.25 in net benefit annually; the payback period is 4 years ($200K ÷ $50K/year)
• B. ROI = 400%, the project pays for itself 4 times
• C. ROI = 250%, the investment generates 2.5× returns
• D. ROI = 0%, only internal rate of return matters for IT projects

ROI CALCULATION: ROI = (Net Benefits / Investment) × 100% = ($50,000 / $200,000) × 100% = 25%. INTERPRETATION: the project returns 25 cents for every dollar invested per year; PAYBACK PERIOD: $200,000 ÷ $50,000/year = 4 years to fully recover the investment; after 4 years, the project generates pure net benefit. BUSINESS CASE DECISION: whether 25% ROI is acceptable depends on: the organization's required rate of return (hurdle rate); alternative investment opportunities; strategic value beyond the quantified financial return; risk profile. A 25% annual ROI is generally considered favorable for an IT project with manageable risk. ADDITIONAL FINANCIAL METRICS used alongside ROI in business cases: Net Present Value (NPV): accounts for time value of money (future benefits discounted to present value); Internal Rate of Return (IRR): the discount rate at which NPV = 0; Payback Period: how quickly the investment is recovered.

• A. Only interview the department manager, they know the current state best
• B. Only review existing process documentation, written procedures capture the current state accurately
• C. Design the future state first, then document the current state to highlight the gap, starting with the desired outcome is more efficient
• D. Conduct a multi-method current state assessment: observe actual claims processing (process shadowing), interview claims adjusters and supervisors, review performance metrics (cycle time, error rates, rework frequency, customer complaints), map current workflows including all exceptions and workarounds, inventory current technology systems and their integration points, document pain points and their business impact, and measure current vs. target performance gap

THOROUGH CURRENT STATE ANALYSIS: PROCESS OBSERVATION (shadowing): watching claims adjusters process actual claims reveals the real workflow, including informal steps, system workarounds, exception handling, and bottlenecks that no document captures; STAKEHOLDER INTERVIEWS: multiple levels (adjusters, supervisors, IT, compliance) provide different perspectives; QUANTITATIVE PERFORMANCE METRICS: cycle time per claim; error rate; rework frequency; cost per claim; customer complaint rate; backlog size; these numbers make the current state pain objective and quantifiable; PROCESS MAPPING: document all steps including decision points, exceptions, and hand-offs; the gap between documented procedure and actual practice is itself a finding; TECHNOLOGY INVENTORY: current systems, their limitations, integration gaps (systems that don't talk to each other = manual re-entry = error source); DATA QUALITY ASSESSMENT: the current state of data, how much is available, how accurate, how complete; PAIN POINT DOCUMENTATION: specific, business-impact-quantified pain points ('Claims adjusters spend 45 minutes per claim on manual data entry; error rate of 12% requires 30% of claims to be manually reworked'), these become the business case's justification.

• A. The client SOW defines the scope of work the consulting firm is expected to perform; the client TOR defines the objectives, authority, methodology, and expected outcomes of the engagement; together they serve as preexisting context that shapes the entire project, the discovery phase validates whether the client's documented expectations align with the actual current state and the achievable future state, and surfaces any gaps or unrealistic assumptions in the client's documents
• B. Client-provided SOW and TOR are irrelevant, the consulting firm will define the project's scope and objectives independently
• C. The client SOW and TOR replace the need for a business case, client documents are always sufficient for project authorization
• D. Client-provided documents should be ignored until contract signing, they have no official status during discovery

CLIENT SOW AND TOR IN DISCOVERY PHASE: CLIENT SOW: defines the specific work the consulting firm is contracted to perform; deliverables, timeline, quality standards, acceptance criteria; this is the CONTRACT SCOPE BASELINE, what the client expects to receive; in the discovery phase: review the SOW to understand the contracted scope; identify any ambiguities or gaps in the SOW that need clarification before work begins; surface any scope elements in the SOW that appear unrealistic based on initial discovery findings. CLIENT TOR: defines the objectives, authority, methodology, expected outcomes, and reporting structure of the engagement; particularly relevant for assessment, audit, or advisory engagements; defines the scope of the consulting firm's authority (what can they access? whom can they interview?). DISCOVERY PHASE ROLE: validate that the client's documented expectations in the SOW and TOR are achievable; identify if the client's assumptions in these documents are incorrect (e.g., the SOW assumes current state X, but the actual current state is Y); flag discrepancies between the client's documented expectations and actual organizational reality early, before they become mid-project scope disputes.

• A. Discovery: develop the project charter; Initiation: create the business case, business cases are created after the project is authorized
• B. Discovery: project schedule, WBS, risk register; Initiation: business case, detailed planning precedes business justification
• C. Discovery and initiation are the same phase, there is no meaningful distinction
• D. Discovery: business case development, ROI analysis, current state analysis, future state definition, options analysis, preliminary scope statement, CapEx/OpEx classification; Initiation: project charter, RACI, stakeholder identification and assessment, project objectives, communication channels, initiation activities occur AFTER the project is authorized based on the discovery phase deliverables

PROJECT LIFECYCLE PHASE DISTINCTIONS: DISCOVERY/CONCEPT PHASE, purpose is to evaluate WHETHER to do the project: Business case (why should we do this?); ROI and financial analysis; Current state documentation (what exists today?); Future state definition (what do we want to achieve?); Options analysis (how might we achieve it?); Preliminary scope statement (conceptual boundaries); CapEx vs. OpEx financial modeling; Preexisting contracts/vendor review; Preliminary risk identification; Phase OUTPUT: a business case document presented to decision-makers for project authorization. INITIATION PHASE, purpose is to formally START the authorized project: Project charter (formally authorizes the project, names the PM); Stakeholder identification and assessment; RACI matrix development; Project objectives formalization; Communication channels establishment; Records management plan; Access requirements; Kickoff meeting planning; Phase INPUT: approved business case from discovery. SEQUENCING LOGIC: you cannot meaningfully write a project charter until the business case defines what the project is trying to achieve; you cannot identify and engage stakeholders effectively until the project is authorized (via business case approval).

• A. The business case needs: benefits validation (how confident is the 40% deflection estimate? what is the basis?); total cost of ownership (development $600K + hosting, licensing, ongoing maintenance, support staff costs); risk assessment (what if adoption is lower than expected?); options analysis (portal vs. IVR enhancements vs. chatbot); strategic alignment (does a self-service portal align with the customer experience strategy?); implementation timeline and cost ramp-up; NPV/payback period calculation using discounted cash flows; qualitative benefits (brand enhancement, customer satisfaction scores)
• B. No additional information is needed, $800K savings vs. $600K cost makes the business case obvious
• C. Only the technology vendor selection is needed, once a vendor is chosen, the business case writes itself
• D. The project schedule is needed to complete the business case, timelines determine ROI

COMPLETE BUSINESS CASE ADDITIONAL REQUIREMENTS: BENEFITS VALIDATION: the 40% call deflection estimate needs a basis, is it from industry benchmarks? Competitor analysis? Pilot data? The confidence level in this number drives the business case's reliability; TOTAL COST OF OWNERSHIP (beyond development $600K): annual hosting/infrastructure costs; software licenses; ongoing development and enhancements; customer service team training on new portal features; content management for portal knowledge base; these recurring costs could significantly reduce the $800K/year net savings; RISK ASSESSMENT: probability that deflection is lower than 40%; user adoption risk (customers prefer phone to self-service); technology failure risk; customer experience risk if portal is confusing; OPTIONS ANALYSIS: the business case should compare 2-3 approaches: portal vs. IVR enhancements vs. AI chatbot; STRATEGIC ALIGNMENT: does a self-service portal align with the company's customer relationship strategy? Some companies intentionally create high-touch service as a differentiator; NPV/PAYBACK ANALYSIS: time value of money, when do benefits materialize? Development takes time; adoption ramps up; discounting future cash flows produces NPV and IRR; QUALITATIVE BENEFITS: customer satisfaction score improvement; net promoter score impact; competitive positioning.

• A. 'We will have a much better claims processing system with fewer errors and happier customers', future state should be aspirational and inspiring
• B. 'We will use the latest AI technology to completely automate claims processing', technology choice defines the future state
• C. The future state should be defined only by the technology vendor, they know what is achievable better than the business
• D. A SMART future state: cycle time reduced to 3 days (75% improvement); error rate reduced to <1%; cost per claim reduced to $40 (53% reduction); customer satisfaction ≥85/100, with business context: enabling 40% growth in claims volume without adding headcount, saving $15M annually in processing costs

EFFECTIVE FUTURE STATE DEFINITION, SMART outcomes: SPECIFIC: each metric is precisely defined (cycle time, error rate, cost, satisfaction); MEASURABLE: all four metrics can be objectively measured after implementation; ACHIEVABLE: benchmarked against industry standards and competitor performance; RELEVANT: each metric addresses a current state pain point (12-day cycle → 3 days; 12% errors → <1%); TIME-BOUND: 'achieved by go-live date' or 'within 6 months of go-live'; BUSINESS CONTEXT: quantifying the business value ($15M annual savings, capacity for 40% volume growth) transforms the future state from a technical goal into a business investment story. The future state metrics become: the project's acceptance criteria at go-live; the KPIs tracked in the post-implementation period; the basis for measuring project ROI; the benchmark for continuous improvement post-project.

• A. The business case is trivial, cost savings will obviously exceed investment
• B. Financial analysis: Annual savings: 17 FTE × ($65K/month × 12 / 25 FTE) = 17 × $31,200/year = $530,400/year; Error reduction savings: estimate $2,000/error × (3,000 × 8% = 240 errors/month) × 12 = $5.76M/year, but this is unreliable without better data on actual cost per error; Simple payback: $1.5M ÷ $530K (conservative, labor savings only) ≈ 2.8 years; Key assumptions and risks: actual FTE reduction depends on redeployment vs. reduction; error cost savings need validation; customer retention impact of faster processing; implementation complexity risk
• C. Reject the project, $1.5M is too expensive for any manufacturing automation
• D. Approve the project immediately without financial analysis, the COO requested it so it must be justified

BUSINESS CASE FINANCIAL ANALYSIS: LABOR SAVINGS: Cost per FTE = $65,000/month ÷ 25 FTE = $2,600/month per FTE; 17 FTE × $2,600/month = $44,200/month = $530,400/year saved; Note: this assumes the 17 FTE are ELIMINATED (not redeployed); if redeployed to new roles, the savings are different, this is a KEY ASSUMPTION. ERROR REDUCTION SAVINGS (estimate): Current: 3,000 orders × 8% = 240 errors/month; Target: 3,000 × 0.5% = 15 errors/month; Reduction: 225 fewer errors/month; Cost per error needs analysis, may include: order rework time, customer service calls, expedited shipping, customer goodwill credits; even at $500/error: 225 × $500 × 12 = $1.35M/year in error savings. FINANCIAL SUMMARY: Annual benefit (conservative, labor only): $530,400/year; Annual maintenance cost: $150,000/year; Net annual benefit: $380,400/year; Simple payback: $1,500,000 ÷ $380,400 = 3.9 years; With error savings ($1.35M): Net annual benefit = $530K − $150K + $1.35M = $1.73M; Payback: $1.5M ÷ $1.73M = ~10 months, VERY strong. KEY ASSUMPTIONS: FTE reduction assumes labor reduction, not redeployment; Error cost estimate requires validation with customer service and operations data; Implementation achieves full productivity within 6 months; 3,000 orders/month volume is stable or growing. RISKS: vendor delivery risk; user adoption risk; implementation disruption to ongoing operations.