Lite Delivery Playbook Overview

Lite Delivery Playbook Overview. Predictable delivery for small initiatives with 2-5 person teams.

[Audio] This slide introduces the Lite Delivery Framework and explains when and why we use it. Lite Delivery is designed for small initiatives with 2–5 people where work is predictable, but Extreme‑Lite is no longer sufficient. Typically, this means: More than one contributor Multiple work items A need for basic planning, quality checks, and value tracking, but still without full project management overhead. The framework follows a simple, disciplined lifecycle: Discover – clarify the problem and define a clear value hypothesis Plan – create a lightweight backlog and delivery structure Deliver – execute the work while tracking progress, quality, and value signals Release – confirm readiness using clear go/no‑go gates Measure – validate outcomes and capture learning after release A critical principle of Lite Delivery is that every artefact supports a decision. We do not create documents for documentation's sake. Another key rule is single‑workbook execution: All Lite artefacts live as sheets in one Excel workbook This enables the Executive Dashboard to aggregate automatically If artefacts are split across files, the model breaks Lite Delivery is fully aligned with the Value Delivery Framework: Value is defined upfront in the Charter Tracked during delivery via Value Pulse Confirmed after release using Value Outcome If an initiative starts to require: Heavy coordination Detailed scheduling Complex risks or stakeholder conflicts that is a signal to escalate to Medium Delivery, not to overload Lite. Lite Delivery gives us predictability, transparency, and value focus— with the minimum governance required to stay in control..

[Audio] This slide introduces the Project Charter OnePager, which is the formal entry point into Lite Delivery. The Project Charter is mandatory and must be completed before any other Lite artefact is created. This is a hard rule. If the Charter is not clear, everything that follows will be unstable. The purpose of the OnePager is to capture, on a single page, the essential decisions needed to justify starting delivery: What problem or opportunity we are addressing Why it matters from a value perspective What success looks like in measurable terms The Charter is not a detailed business case. It is a decision artefact that answers one question: Is this initiative worth executing using Lite Delivery? Key elements of the Charter include: Problem or Opportunity – clearly articulated in business terms, not solution language Solution Idea – a high-level approach, not detailed design Expected Value – aligned to Value Delivery Framework dimensions Success Criteria – how we will know the initiative succeeded High-Level Scope – what is in and, just as importantly, what is out Assumptions and Constraints – anything that could materially affect delivery Roles and Ownership – clear accountability for delivery and value Another critical role of the Charter is method selection. This is where we confirm that Lite Delivery is the right fit: Team size is small Work is predictable Governance needs are lightweight If, during Charter creation, we discover: Unclear ownership Conflicting objectives Significant uncertainty or dependencies that is an early signal to rethink the approach or escalate, not to push forward. In Lite Delivery, the Charter also acts as the anchor for value tracking: Value hypotheses defined here feed directly into Value Pulse Those same hypotheses are later validated in Value Outcome Think of the Project Charter as the contract for delivery: If it is weak or vague, the initiative will drift If it is clear and focused, Lite Delivery works exactly as intended Only once the Charter is completed and agreed do we move on to: Backlog Delivery planning Quality and value tracking.

[Audio] This slide introduces the Lite Backlog, which is the core execution artefact in Lite Delivery. The Lite Backlog is not a large, long-term requirements list. It is a small, deliberately constrained set of work items that the team commits to delivering within a short, predictable window. Each backlog item must clearly answer two questions: What are we delivering? Why does it matter from a value perspective? That "why" is critical. Every work item must connect back to the value hypotheses defined in the Project Charter. If an item cannot be traced to value, it does not belong in a Lite Backlog. Prioritization is explicit and intentional. Items are ranked so the team always focuses on the highest-value work first, not on what is easiest or most comfortable. Acceptance criteria are lightweight but non-negotiable. They define, in VDF-aligned terms, what "done" actually means: What must be true for this item to be considered complete. What evidence or outcome confirms completion. Status tracking is simple and transparent: To Do In Progress Done There are no custom statuses, no ambiguity, and no manual health coloring. A key principle here is automated GO / NO‑GO status. The overall signal is derived directly from the work item statuses: If items are progressing as expected → GO If critical items are blocked or incomplete → NO‑GO This prevents optimistic reporting and keeps the signal objective. Backlog items can also be assigned to releases, allowing phased delivery without introducing heavy planning or scheduling overhead. The Lite Backlog exists to support daily execution and weekly decision-making: What are we working on? Are we making progress? Are we still on track to deliver value? If the backlog starts to grow large, becomes difficult to prioritize, or requires complex coordination, that is a signal to escalate to Medium Delivery, not to overload Lite. In short, the Lite Backlog keeps delivery: Focused Value-driven Transparent while remaining lightweight and disciplined..

[Audio] This slide introduces the Lite Delivery Plan. The Lite Delivery Plan explains how the initiative moves through the Lite lifecycle without introducing detailed schedules, task breakdowns, or heavyweight planning. This is an important distinction. In Lite Delivery, the plan is not a Gantt chart and not a task-level schedule. Its purpose is to provide structure and predictability, not micromanagement. The plan is organized around the Lite lifecycle phases: Discover Plan Deliver Release Measure For each phase, the Delivery Plan answers a small set of essential questions: What is the objective of this phase? What key activities must happen to achieve that objective? Who is responsible? What is the target time window, expressed in weeks rather than exact dates? What is the current status? By using time windows instead of fixed dates, Lite Delivery stays realistic and flexible, while still setting clear expectations. Progress through the plan is tracked using simple status indicators. There is no percentage completion, no complex dependencies, and no artificial precision. Just like other Lite artefacts, the Delivery Plan supports automated GO / NO‑GO signals: If phases are progressing as expected → GO If phases are stalled, blocked, or slipping → NO‑GO This makes the Delivery Plan especially useful during: Weekly delivery syncs Release readiness checks Executive reviews The Delivery Plan also acts as a bridge between strategy and execution: The Charter defines why we are doing the initiative The Backlog defines what we are delivering The Delivery Plan shows how the workflows through the lifecycle Importantly, the Delivery Plan is kept intentionally lightweight. If the team starts needing: Detailed task sequencing Day-by-day scheduling Complex dependency management that is a signal to escalate to Medium Delivery, not to overload the Lite model. In short, the Lite Delivery Plan provides: Clear lifecycle structure Predictable flow Transparent status while avoiding the overhead that would slow down small, predictable initiatives..

[Audio] This slide introduces the Lite Test Strategy. The Lite Test Strategy is a lightweight quality agreement, not a full test plan. Its purpose is to clearly define how quality and risk will be addressed without introducing unnecessary testing overhead. In Lite Delivery, we do not create exhaustive test documentation. Instead, we agree what needs to be tested, why, and to what depth, based on risk. The Test Strategy focuses on a small number of essential elements. First, we identify the test areas that matter for this initiative. This could include functional behavior, integrations, performance, security, or user acceptance, only where relevant. Next, we define the test objective for each area. This makes it explicit what risk we are trying to mitigate and what "good enough" quality means in context. We then agree on the test approach. This might be manual testing, automation, peer review, or a combination, but it is always proportional to the risk and complexity involved. Ownership is clear. Each test area has a named owner and defined evidence that confirms testing has been completed. If there is no owner and no evidence, quality is assumed to be unverified. A critical element is coverage level. For each test area, we explicitly state whether coverage is: Full Partial Spot check This avoids the common problem of "implicit assumptions" about testing depth. Just like other Lite artefacts, the Test Strategy supports objective GO / NO‑GO decisions. If agreed testing is complete and evidence exists → GO If critical testing is missing or incomplete → NO‑GO This ensures that quality signals are fact-based, not optimistic or informal. The Lite Test Strategy is intentionally simple and visible. It works well in: Weekly delivery syncs Release readiness discussions Executive reviews If testing requirements become detailed, contested, or highly regulated, that is a signal to escalate to Medium Delivery, not to overload Lite. In short, the Lite Test Strategy ensures: Clear quality expectations Risk-aware testing decisions Objective release readiness while keeping testing lightweight, proportional, and fit for purpose..

[Audio] This slide introduces Value Pulse Lite. Value Pulse is how we track emerging value signals during delivery to confirm that value is trending in the expected direction, before we reach release. This is a critical concept in Lite Delivery. We do not wait until the end to ask whether value was delivered. Instead, we continuously check whether value is starting to materialize as expected. Value Pulse is directly anchored to the value hypotheses defined in the Project Charter. We are not inventing new metrics here. We are monitoring early signals that indicate whether those original assumptions still hold. The purpose of Value Pulse is decision support, not reporting. It helps teams and stakeholders answer a simple but important question: Are we still on track to deliver the intended value? Value Pulse focuses on observable signals, not perfect measurements. These could be early usage indicators, operational improvements, stakeholder feedback, or proxy metrics, whatever makes sense for the initiative. Trends are intentionally simple: Up Stable Down We care more about direction than absolute precision at this stage. The system can suggest an overall Pulse status based on these trends, but professional judgment is still allowed. If context matters, it should be explained, not hidden. Value Pulse is used actively during: Weekly delivery syncs Checkpoints before release Conversations about scope, priority, or corrective action If value signals start trending down, this is an early warning, not a failure. It gives the team a chance to: Adjust scope Refocus effort Correct assumptions before delivery momentum is lost. Just like other Lite artefacts, Value Pulse supports objective GO / NO‑GO thinking: If value signals are trending as expected → confidence increases If signals consistently diverge → intervention is required Importantly, Value Pulse does not replace Value Outcome. Value Pulse asks: Are we heading in the right direction? Value Outcome later asks: Did we actually get there? If value tracking becomes complex, disputed, or requires heavy analytics, that is a signal to escalate to Medium Delivery, not to overload Lite. In short, Value Pulse Lite ensures that: Value remains visible during delivery Assumptions are tested early Decisions are informed, not reactive while keeping value tracking lightweight, practical, and actionable..

[Audio] This slide introduces Lite Value Outcome. Lite Value Outcome is the post‑release validation artefact. Its purpose is to confirm whether the intended value was actually achieved, not just delivered. Up to this point, Lite Delivery has focused on: Defining value in the Project Charter Tracking emerging signals through Value Pulse Value Outcome is where we close the loop. Here, we move from signals and assumptions to evidence. The Value Outcome asks four simple but critical questions: First, what value did we originally intend to deliver? We explicitly trace each outcome back to the value hypotheses defined in the Project Charter. Nothing new is introduced here. Second, what metric or evidence did we agree would demonstrate success? This could be quantitative or qualitative, but it must be observable and agreed upfront. Third, what was the actual result, measured after enough time has passed for value to materialize? We are not looking for instant results, but for stable, credible evidence. Finally, how does actual value compare to the target? This comparison is the basis for an objective outcome decision. Based on this comparison, the system supports a clear recommendation, such as: Value achieved → Done Value partially achieved → Improve Value exceeded or scalable → Scale The goal is not to judge effort. The goal is to learn whether the initiative delivered meaningful value. Lite Value Outcome also captures key learnings: What worked What didn't What assumptions proved correct or incorrect These insights are essential inputs for: Future initiatives Continuous improvement Scaling decisions Just like other Lite artefacts, Value Outcome supports fact‑based GO / NO‑GO thinking: If value was delivered as intended → confidence increases If value fell short → decisions are informed, not emotional Importantly, Value Outcome is not a heavy benefits realization report. It is a focused, lightweight validation designed to support clear decisions. If outcome measurement becomes complex, long‑term, or analytically heavy, that is a signal to escalate to Medium Delivery, not to overload Lite. In short, Lite Value Outcome ensures that: Delivery is closed with evidence Value claims are validated Learning is captured explicitly so that Lite Delivery ends not just with completion—but with clarity and accountability for value..

[Audio] This slide introduces the Lite Executive Dashboard. The Lite Executive Dashboard provides aggregated visibility across all Lite artefacts to support fast, informed executive decisions, without manual data entry. The dashboard is not a separate reporting tool. It is a read-only decision surface that automatically pulls data from all other Lite artefact sheets in the same workbook. This is why single‑workbook execution is a non‑negotiable rule in Lite Delivery. If artefacts are split across files, the dashboard cannot function reliably. The purpose of the dashboard is clarity, not detail. It answers a small set of executive‑level questions: Are we on track? Is delivery progressing as expected? Are quality and readiness under control? Is value trending in the right direction? The dashboard consolidates signals from across the Lite model, including: Backlog completion and progress Delivery Plan phase status Test Strategy coverage and readiness Value Pulse trends Value Outcome classification, when available A key feature is GO / NO‑GO gate visibility. Rather than subjective status reporting, the dashboard reflects automated signals derived directly from the underlying artefacts. If the source data indicates: Progress, readiness, and value alignment → GO Blockers, gaps, or unresolved risks → NO‑GO This ensures that executive conversations are fact‑based, not optimistic. The dashboard is used actively during: Weekly or bi‑weekly executive check‑ins Release readiness decisions Portfolio or initiative reviews A critical rule is that the dashboard must never be edited directly. All updates happen by maintaining the underlying artefacts: If the backlog changes, the dashboard updates If delivery slips, the dashboard reflects it If value trends shift, the dashboard shows it This reinforces disciplined behavior: Teams focus on maintaining artefacts correctly Executives trust the signal because it is system‑generated The Lite Executive Dashboard does not replace discussion or judgment. It creates a shared, objective starting point for those conversations. If the dashboard starts needing: Manual adjustments Explanatory workarounds Custom metrics or analytics that is a signal to escalate to Medium Delivery, not to overload Lite. In short, the Lite Executive Dashboard ensures: End‑to‑end transparency Automated, objective signals Fast executive decision‑making while keeping oversight lightweight, reliable, and scalable..

[Audio] This slide shows the Lite Delivery Artefact Usage Flow. The purpose of this slide is to make one thing absolutely clear: Lite Delivery is not a collection of optional templates. It is a disciplined sequence of decision artefacts, used in a specific order. The artefacts are numbered intentionally to reflect the mandatory order of creation and use. Everything starts with 01 – Project Charter OnePager. This is the formal entry point into Lite Delivery. No other artefact should be created until the Charter is completed and agreed. If the Charter is weak or unclear, everything that follows will be unstable. Once the Charter is in place, we move into planning artefacts: 02 – Lite Backlog, which defines what we are delivering 03 – Lite Delivery Plan, which shows how the work flows through the lifecycle 04 – Lite Test Strategy, which defines how quality and risk will be handled Together, these establish clarity across scope, flow, and quality, without heavyweight planning. During delivery, we actively use 05 – Value Pulse Lite. This allows us to track emerging value signals while work is still in progress, not after, when it is too late to act. After release, we complete 06 – Lite Value Outcome. This is where we validate whether the intended value was actually achieved, using evidence rather than assumptions. Throughout the entire lifecycle, 07 – Lite Executive Dashboard runs continuously. It aggregates signals from all other artefacts and provides a single, objective view for decision-making. A critical principle here is single‑workbook execution. All artefacts exist as sheets within one Excel workbook so the dashboard can aggregate automatically. If artefacts are split across files, the model breaks. This flow is deliberately simple, linear, and disciplined. It ensures that: Decisions are made in the right order Value is defined before work starts Progress and readiness are visible during delivery Outcomes are validated after release If teams start skipping steps, reordering artefacts, or creating documents out of sequence, that is a warning sign. It usually indicates either: Poor discipline, or That the initiative no longer fits Lite Delivery and should be escalated to Medium Delivery. In short, this artefact flow ensures that Lite Delivery remains: Predictable Value‑driven Transparent with the minimum governance required to stay in control..

[Audio] This slide summarizes the non‑negotiable implementation rules for Lite Delivery. These are not guidelines or best practices. They are hard rules that must be followed for the Lite model to work as intended. The first and most important rule is single‑workbook execution. All Lite artefacts must exist as sheets within one Excel workbook. This is essential because the Executive Dashboard relies on automated aggregation. If artefacts are separated across multiple files, the dashboard cannot function reliably and the model breaks. Closely related to this is the rule that artefacts are sheets, not documents. In Lite Delivery, we do not create isolated files for backlog, planning, testing, or value tracking. Each artefact is a structured sheet that feeds the overall system. Another critical rule is automatic dashboard updates. The Executive Dashboard must always reflect the current state of delivery, quality, and value—without manual intervention. This means: The dashboard is read‑only No data is entered directly into it All changes happen in the underlying artefacts If someone feels the need to manually adjust the dashboard, that is a warning sign that discipline is breaking down. Artefact numbering must also be strictly maintained. The numbers are not cosmetic. They reflect the required order of creation and use and ensure a shared understanding across teams. Skipping steps, renumbering artefacts, or using them out of sequence undermines the decision logic of Lite Delivery. This slide also highlights signals to watch for escalation. If you start seeing: Excessive backlog growth Pressure for detailed scheduling Disputed quality expectations Stakeholder conflicts that require heavy coordination those are not problems to solve by adding more detail to Lite artefacts. They are signals that the initiative should be escalated to Medium Delivery. Lite Delivery succeeds by staying lightweight, disciplined, and focused on decisions. The moment we start bending the rules, we lose predictability and trust in the signal. In short, these implementation rules ensure that: The system remains reliable Executive signals stay objective Governance remains proportional They protect Lite Delivery from slowly turning into a heavyweight process, and that protection is intentional..

References. [1] Lite_Delivery_Playbook_User_Manual_v2_Numbered.docx [2] Extreme_Lite_Delivery_Playbook_Training_DRAFT.pptx.