BCT(B) study plan

Map the full requirements lifecycle from elicitation through sign-off, and list the inputs, outputs, and decision gates for each stage.

Draft a stakeholder-elicitation plan for a sample project, choosing techniques (interviews, workshops, observation, document analysis) and justifying each choice against stakeholder type and risk.

Write ten testable functional requirements and ten non-functional requirements for a provided business scenario, applying unambiguous, verifiable wording.

Classify each of the twenty requirements as functional, non-functional, or constraint, and flag any that are untestable as written.

Build a requirements traceability matrix that maps business objectives to stakeholder needs, requirements, and acceptance criteria.

Model the current-state process for a sample order-to-cash workflow using a swimlane diagram, identifying at least six handoffs and three bottlenecks.

Redesign the same process as a future-state model, and quantify the expected improvement in cycle time or handoff count.

Write a requirements-verification checklist and use it to peer-review a colleague's or sample requirements set, logging every defect found.

Compare three process-improvement approaches (lean, six sigma, and automation-first) and recommend one for a given scenario with written justification.

Define five process performance metrics with formulas, data sources, and target thresholds.

Profile a sample dataset for completeness, accuracy, and consistency, and document every data-quality issue with its business impact.

Select and justify the correct chart type for five different analytical questions, explaining why alternatives would mislead.

Construct a decision matrix that scores three candidate solutions against weighted criteria, and document the weighting rationale.

Write a cost-benefit analysis for the top-scoring option, including a simple payback calculation and stated assumptions.

Translate the week 1 requirements into solution acceptance criteria and identify any requirements the proposed solution does not satisfy.

Draft a gap analysis that lists every unmet requirement with a mitigation or scope-change recommendation.

Design a stakeholder communication plan that assigns each stakeholder group a channel, cadence, message type, and owner.

Facilitate a 30-minute mock requirements workshop with a peer, practicing open questions, parking-lot capture, and conflict resolution.

Produce a one-page executive summary of the week 4 solution recommendation, written for a non-technical sponsor.

Prepare and deliver a five-minute verbal defense of the recommendation, then log the three toughest questions received and your answers.

Build a work breakdown structure for a solution-delivery effort and estimate effort for each work package.

Identify the top five project risks, score them on likelihood and impact, and assign a response strategy to each.

Draft a change-readiness assessment covering sponsor commitment, impacted-user groups, training needs, and resistance risks.

Create a stakeholder resistance map with a tailored engagement tactic for each high-resistance group.

Apply a professional code of conduct to five short ethical scenarios, stating the relevant principle, the risk, and the recommended action for each.

Identify conflicts of interest and confidentiality obligations in a sample engagement, and write the disclosure or handling steps.

Integrate the prior weeks' artifacts into a single end-to-end case study narrative with a consistent scope and stakeholder set.

Review the case study against a self-built checklist of all seven domains and note any domain with thin coverage.

Complete two timed 60-question practice sets, and score each by domain to identify the three weakest areas.

Rework every missed question from the practice sets by writing the underlying principle and the reason the chosen answer was wrong.

Rehearse the case study presentation in ten minutes, then revise the summary to fix the two weakest explanations.

Produce a final one-page formula and framework sheet covering requirements, metrics, and evaluation criteria, and self-test it from memory.