GTG ARCHITECTURE & DELIVERY EXAMPLE / PUBLIC SAMPLE PLAYGROUND
A Roadmap That Respects the Dependencies.
Plan a fictional reporting initiative. Change team capacity, delivery approach, and sequencing priority, then inspect the resulting schedule, decisions, and acceptance criteria.
Explore This Workflow
Select a step, change its settings, then run the example to see what changes. The workflow follows a fixed sequence. No login is needed. Changes reset when you reload or leave this page.
This public playground uses fictional data. Your changes affect this fictional example only.
Showing the result for the current connections and settings.
THE STARTING POINT
GTG Sequences a Fictional Reporting Modernization
Northstar wants a trusted management report. Source access, agreed measures, a validated pipeline, and operating handoff all have dependencies.
- Capacity
- Two concurrent workstreams
- Delivery approach
- Early prototype review, then validated delivery
- Sequencing priority
- Business definitions and early report feedback
- Source ownership
- Operations source owner assigned in the sample
Illustrative GTG workflow with fictional data. Nothing is sent to GTG, a CRM, an email service, or a calendar.
Select a step to explore its role and settings. This walkthrough follows a fixed sequence.
CAPACITY CONSTRAINT / SELECTED CONTEXT
Allocate Teams
Schedule one or two workstreams; each task uses one stream for its full sample duration.
Each task uses one workstream for its full duration. Increasing capacity allows overlap only where dependencies permit it.
Configure Allocate Teams
These settings apply to fictional sample data. Run the configured sample after a change.
6 tasks, 8 workstream-weeks of effort, 2 concurrent workstream(s): the sample finishes in week 6. Dependencies and acceptance criteria remain visible.
- Tasks in scope
- 6
- Workstream-weeks of effort
- 8
- Concurrent workstreams
- 2
- Scheduled weeks
- 6
THE BUSINESS OUTPUT
Architecture Decisions & Delivery Roadmap — Example
- Schedule
- Relative weeks 1–6; 2 concurrent workstream(s)
- Decision and tradeoff
- An early prototype adds one workstream-week of effort and provides feedback before final acceptance.
- Dependency that cannot be skipped
- Source access → validated pipeline → model and report → acceptance and handoff
- Estimate assumptions
- Fixed fictional task durations, full workstream availability, no holidays or dates. Deterministic sequencing demonstrates dependencies; it is not an optimized or committed client schedule.
Fictional planning exercise. Assigning a role here records a sample assumption; it does not appoint a real person, create a task, or approve a project.
Delivery Roadmap
Each task uses one workstream. Bars show relative weeks; prerequisites are listed in the acceptance register.
- Confirm source accessWeek 1
- Agree KPI definitionsWeek 1
- Build validated pipelineWeek 2–3
- Review report prototypeWeek 2
- Build model and reportWeek 4–5
- Accept and hand overWeek 6
Delivery Decisions, Dependencies & Acceptance
Scroll horizontally to see all columns. Keyboard: focus the table, then use the arrow keys.
| Work item | Schedule | Prerequisites | Accountable role / acceptance |
|---|---|---|---|
| Agree KPI definitions | Week 1 | None | Business sponsor. Business sponsor signs off on metric definitions and scope. |
| Confirm source access | Week 1 | None | Operations source owner. Source owner approves access and names the operating contact. |
| Build validated pipeline | Week 2–3 | Confirm source access | Data engineering lead. Source-to-target counts and values reconcile; recovery is demonstrated. |
| Review report prototype | Week 2 | Agree KPI definitions | Analytics lead. Users review the report layout with fictional data before live-data acceptance. |
| Build model and report | Week 4–5 | Agree KPI definitions; Build validated pipeline | Analytics lead. Agreed measures reconcile and report-access requirements are verified. |
| Accept and hand over | Week 6 | Build model and report; Review report prototype | Delivery lead. Sponsor accepts results; operating owner receives runbook and recovery evidence. |
Bring your own business problem, systems, and constraints into a GTG discovery conversation.
Build Your Discovery Brief