TEST ARCHED study materials
TEST ARCHED study resources

TEST ARCHED study plan

TEST ARCHED · Give each week a clear focus.

8 weeks · About 7 hours per week

Week 1

Project and Program Fundamentals

  • Define and distinguish project, program, and portfolio in your own words, mapping each to a real example from your own work history

  • Explain the role and accountability boundaries of the project manager, program manager, sponsor, and PMO without notes

  • Diagram the project life cycle and show where phase gates, baselines, and benefits realization sit

  • Build a one-page glossary of 25 core fundamentals terms with a one-line definition for each

Your checkpoint

A one-page fundamentals glossary plus a hand-drawn life cycle diagram photographed or scanned, both reviewed against your own notes for gaps

Week 2

Project and Program Fundamentals & Architecture and Solution Design

  • Compare predictive, iterative, and hybrid delivery approaches and state two selection criteria for each

  • Describe how organizational structure (functional, matrix, projectized) changes a project manager's authority

  • Identify the inputs and outputs of architecture and solution design within the delivery life cycle

  • Write a short argument for which delivery approach fits a project you have actually worked on

Your checkpoint

A two-page comparison table of delivery approaches with a 300-word recommendation memo for a real or realistic project

Week 3

Architecture and Solution Design

  • Explain the purpose and structure of an architecture overview, including logical, physical, and deployment views

  • Distinguish business, data, application, and technology architecture layers and give one artifact for each

  • Describe how non-functional requirements drive design decisions and where to record them

  • Outline a design review process including participants, entry criteria, and decision records

Your checkpoint

A one-page architecture overview for a hypothetical system covering all four layers plus three design decisions with rationale

Week 4

Architecture and Solution Design & Requirements and Scope Definition

  • Trace a requirement from elicitation through design decision to a verification method

  • Compare elicitation techniques (interviews, workshops, observation, document analysis) and state when each is strongest

  • Write three well-formed functional requirements and two non-functional requirements with measurable acceptance criteria

  • Explain how scope baseline, work breakdown structure, and traceability matrix connect

Your checkpoint

A requirements traceability matrix with at least eight requirements, each linked to a design element and a verification method

Week 5

Requirements and Scope Definition & Delivery and Implementation Management

  • Distinguish scope creep from approved change and describe the control that prevents each

  • Build a work breakdown structure to three levels for a small project and estimate effort per work package

  • Describe how a delivery schedule, critical path, and resource plan interact

  • Explain stage-gate or sprint review governance and what decisions are made at each checkpoint

Your checkpoint

A three-level work breakdown structure with effort estimates and a one-page schedule narrative identifying the critical path

Week 6

Delivery and Implementation Management & Quality Assurance and Verification

  • Define verification and validation and give two activities that serve each

  • Design a test approach covering unit, integration, system, and acceptance levels with entry and exit criteria

  • Describe defect lifecycle states and the metrics that reveal quality trends

  • Explain how quality gates in delivery reduce rework cost and where they belong in the life cycle

Your checkpoint

A one-page test strategy with entry and exit criteria per test level plus a defect severity and priority matrix

Week 7

Risk, Change, and Issue Management & Quality Assurance and Verification

  • Build a risk register with probability, impact, response strategy, and owner for at least ten risks

  • Distinguish risk, issue, and change and state the correct escalation path for each

  • Describe a change control board process from request to decision to implementation

  • Explain how root-cause analysis and lessons learned feed back into risk planning

Your checkpoint

A ten-item risk register with scored exposure, response plans, and owners, plus a one-page change control flow

Week 8

Stakeholder Communication and Governance & Risk, Change, and Issue Management

  • Map stakeholders by influence and interest and choose an engagement approach for each quadrant

  • Draft a status report that distinguishes progress, forecast, risks, and decisions needed

  • Explain governance structures including steering committee, escalation thresholds, and reporting cadence

  • Assemble a personal one-page summary of the seven domains with your weakest two flagged for review

Your checkpoint

A one-page stakeholder engagement plan plus a sample status report, followed by a timed 40-question self-test scored and reviewed

Milestones

Week 2: Explain the difference between project, program, and portfolio and justify a delivery approach choice aloud in under five minutes without notes

Week 4: Produce a traceability matrix unaided in 45 minutes and defend each requirement-to-verification link

Week 6: Score at least 70 percent on a self-written 30-question quiz covering domains 1 through 5, and log every missed item with its cause

Week 8: Score at least 80 percent on a timed 40-question mixed-domain self-test and confirm the risk register and stakeholder plan meet the deliverable checklist