Pulling it all together: Planned Value to Delivery

Pulling it all together - Planned Value to Predictable Delivery

Understand the Core Distinction: Value delivery planning and team execution

DevStride solves what can otherwise be a significant project and portfolio management challenge: the idea of value delivery (what’s being accomplished or delivered) vs. team execution (who’s working on what and when), which may represent several moving parts in the overall portfolio of work.

Mistaking one for the other leads to misaligned boards, poor reporting, and eventually rework.

Real-World Use Cases:

Here are a couple of real-world examples:

DevOps(s) resources has a board that tracks all their web development efforts, but they may be creating features from 10 different workstreams on the portfolio (Map Value) map.

A Sales Enablement Team might have a board of tasks and deliverables (playbooks, campaigns, onboarding docs) that belong to different strategic initiatives in Map Value.

A Best Practice Approach

Here's a quick summary that shows how DevStride creates predictable success by linking value mapping to execution through 4 key modules:

1. Map Value
2. Plan Delivery
3. Track progress
4. Measure performance

1. Define Your Value Delivery (Workstreams) in Map Value.

When creating a workstream, name it based on the business value you plan to deliver (e.g., “Customer Portal”, “Q3 Product Launch”, “Sales Acceleration”).

Within the workstream, create items (e,g., Intiative, Objectives, Tasks or Epics, Features, Stories) that represent outcomes you plan to deliver.

Structure these hierarchically using DevStride’s item types.

Break down work items from bigger units of work to smaller.

For example, a development group's item hierarchy might look like this:

Solution ->
Capability ->
Epic ->
Task
Defect

Goal: This is your delivery view, like a product owner or business leader would view it - a delivery of value.

2. Organize Folders and Define Team Execution in Plan Delivery

Organize Folders

In Plan Delivery:

Create folders (1) named for how teams operate as working groups performing work (e.g., “QA Team”, “Web Product x Engineering Team”, “Customer Ops”).

Inside each folder, create:

• Perpetual Boards (for ongoing work)
• Cycle Boards (for sprints or deadlines) with an assigned cadence/timebox

as needed (2):

Create Boards and and Assign Workstream Items

1. Open a board and assign items from the board.

OR

2. Navigate to items in your porfolio under Map Value (e.g., “Feature: Customer Login”).

Assign those items into the appropriate board where execution happens.

Goal: The boards in the Plan Delivery will be your execution view. This view is one that a project manager, delivery manager, or scrum master might operate in, one that executes the work to support the value delivery.

:::

3. Use Track Progress as a delivery timing guardrail

The interactive gantt charts in Track Progress provide a visual overview of:

• the status of the project
• the items that make it up
• dependencies
• the critical path

In addition to providing teams and leadership with status information, Track Progress creates the opportunity for updates and conversations with clients and stakeholders through:

• scenario planning for delivery timeframes and change requests
• sharing capabilities

4. Measure Performance with interactive reports

The Measure Performance module provides robust and meaningful reporting of progress, throughput, velocity, churn and more, creating the opportunity to track, refine, and improve processes and predictability project over project.

Pull it all together

• Use the Workstreams view in Map Value to see the hierarchy of deliverables as it relates to your objectives and the value your organization is delivering.

• Use the Boards View in Plan Delivery to see what teams are actively executing.

• Use Gantts in Track Progress to see details of delivery timing.

• Use Reports to pull metrics across multiple dimensions.