Lean Six Sigma Black Belt Define Phase: Project Charter 1 Flashcards
6 cards from real Lean Six Sigma Black Belt Certification practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 6 Lean Six Sigma Black Belt Define Phase: Project Charter 1 flashcards as text
A project charter lists the following: 'Reduce customer wait time in the billing department.' What is missing that would make this a well-formed problem statement?
Answer: Quantifiable baseline data and the magnitude of the gap
A strong problem statement must include baseline performance data and the size of the performance gap so the team understands the current state. Identifying root causes or solutions is premature in the Define phase, and naming a process owner is a team-roles element, not the problem statement.
Which charter component formally authorizes the Black Belt to access resources, cross functional data, and personnel needed to execute the project?
Answer: Sponsor signature and authority section
The sponsor signature and authority section of the charter grants the Black Belt organizational permission to pull resources and cross departmental cooperation. Without this formal authorization, the Black Belt lacks the mandate to engage stakeholders or requisition support.
A Black Belt notices the project charter goal reads: 'Improve process yield.' A Master Black Belt reviews the charter and flags this as insufficient. What specific deficiency is the Master Black Belt most likely identifying?
Answer: The goal lacks a numeric target, a baseline, and a deadline
A well-formed project goal must be SMART — Specific, Measurable, Achievable, Relevant, and Time-bound. 'Improve process yield' lacks a numeric baseline, a target improvement percentage, and a completion date, making it unmeasurable and unverifiable.
During the Define phase, stakeholder analysis reveals that the VP of Operations has high influence but low interest in the project. What is the recommended engagement strategy reflected in the project charter's communication plan?
Answer: Keep the VP informed with high-level updates and monitor for shifting priorities
Stakeholders with high influence but low interest should be 'kept satisfied' — meaning periodic high-level updates rather than deep engagement. Over-communicating wastes their time and can invite unwanted scope changes; under-communicating risks losing their passive support.
What is the purpose of including a high-level project timeline with milestones in the project charter?
Answer: To provide an initial schedule baseline that sets expectations and enables sponsor oversight
The high-level timeline in the charter establishes a preliminary schedule baseline so sponsors and stakeholders can set expectations and monitor phase-gate progress. It is intentionally high-level and subject to refinement — not a rigid contract or a substitute for detailed planning.
A Black Belt is finalizing a project charter and must document the financial benefit expected upon project completion. The finance department has not yet validated the savings estimate. What is the appropriate action?
Answer: Include the estimated benefit and clearly mark it as preliminary, pending finance validation
Project charters typically require a financial benefit estimate at chartering time even when finance has not completed a formal validation. Marking the estimate as preliminary maintains transparency and integrity while satisfying the charter requirement. Omitting it or inflating it would undermine trust and governance.