Explore

CODA Doc Administration

Database Overview

Content Page. CODA Docs are powered by a Database in the form of tables. Here you will find a description of those tables and a link to find them

Pedro Bernardo Juan Celis Caraballo

Instructions

Base Tables are by default, viewed as just simple tables, with no sorting, filtering or column hiding. It is easier to check them out like this and modify whatever is necessary.

Following, you will find an explanation, and connections created for each backoffice table that powers the document.

⁠
`Business Model Design Space Tables`⁠
⁠

1.1 Business Model Design Space

⁠

Business Model Design Space - Base Table⁠

- This a very simple table, and it only has one connection in

1.1 Business Model Design Space⁠

. Here it is viewed as a card, so that it is easy to fill and document. This table should not have more rows than the ones already has.

1.2 Baseline Business Model Canvas

⁠

Baseline Business Model Canvas - Base Table⁠

- This is also a very simple table, with nine different views connected in page

1.2 Baseline Business Model Canvas⁠

. Here, there is a view for each Canvas Block, in which an Interactive Baseline Business Model Canvas Event may be done.

⁠

Baseline Business Model Canvas - Block Name⁠

- This is a Look-Up table for the previous table, with the name of the Baseline Canvas Blocks, already with adequate color formatting and an image associated with each block. This Look-Up table is used in several other tables.

1.3 FOAR Analysis

⁠

FOAR Analysis - Base Table⁠

- This is a basic table for the FOAR Analysis event. It also uses the

Baseline Business Model Canvas - Block Name⁠

as the Look-Up Table for Canvas Block names. It has one connection with a Detailed view here,

FOAR Analysis - Display View⁠

. This is the view used in the

FOAR Event⁠

1.4 Blue Ocean

⁠

Blue Ocean Analysis - Base Table⁠

- This is a basic table for the Blue Ocean Analysis Event. It also uses the

Baseline Business Model Canvas - Block Name⁠

as the Look-Up Table for Canvas Block names. It has one connection with a Display view here,

Blue Ocean Analysis - Display View⁠

. This is the view used in the

Blue Ocean Event⁠

1.5 Portfolio Vision

⁠

Portfolio Vision - Base Table⁠

- This is a basic table for the Portfolio Vision Event. It has two connections. One is the Display view here,

Portfolio Vision - Display View⁠

. This view is used in the

Portfolio Vision Event⁠

. Another is the Output view here,

Portfolio Vision - Output⁠

, used as one of the main outputs of the Business Model Design Space.

1.6 Operational Value Streams (OVS)

⁠

Current OVS - Base Table⁠

- This is the table used for the Operational Value Stream Event. It has one connection to the Display view here,

Current OVS - Display View⁠

, used in the

Operational Value Stream Event⁠

1.7 Development Value Stream (DVS)

⁠

DVS - Base Table⁠

- This is the table used for the Development Value Stream Event. This will become the Look-Up table for the Development Value Stream in several other tables throughout this CODA Doc. There are fourteen connected views of this table. Thirteen are views for each one of the building blocks of the Value Stream, located in the

1.7 Development Value Stream (DVS)⁠

page. Another is the Output view here,

DVS - Output⁠

, used as one of the main outputs of the Business Model Design Space.

1.8 Portfolio Canvas

⁠

Portfolio Canvas - Base Table⁠

- This is the table used for the Portfolio Canvas Event. There are thirteen blocks in the Portfolio Canvas. Each one has a table view in the

1.8 Portfolio Canvas⁠

page and another table view in the

1.9 Key Outputs⁠

page. This table uses the Development Value Stream Table as a Look-Up table for the DVS names and ID.

⁠
`OKR's and Portfolio KanBan Tables`⁠
⁠

2.1 Objectives

⁠

Enterprise Wide Objectives - Base Table⁠

- This is the table used for establishing enterprise wide objectives. It uses

DVS - Base Table⁠

as a Look-Up table for the name and ID of the Development Value Stream. This is one of the few base tables with conditional formatting. The idea is to document all brainstormed objectives and leave them be even if they are not selected for the OKR period, so that they will serve as future reference. There are three connected views of this table, two that are used in the

2.1 Objectives⁠

Event. One is for the purpose of brainstorming several objectives and choose those that are a priority:

Objectives - Event Table⁠

. The other is for qualifying the objectives chosen previously:

Objectives - Evaluation Table⁠

. This Objectives table will be used as a Look-Up column in the Key Result tables. The third connected view is located in the

3.6 Key Information Radiators⁠

page. This is for the purpose of showing Objectives progress.

2.2 Key Results

⁠

Key Results - Base Table⁠

- This is the table used for establishing key results for each enterprise wide objective. It uses

Enterprise Wide Objectives - Base Table⁠

as a Look-Up table for the Objectives. There are six connected views of this table. Four of them are used in the

2.2 Key Results⁠

Event. One is for the purpose of brainstorming several key results per objective and choose those that are a priority:

Key Results - Event Table⁠

. The other three are for qualifying key results chosen previously. There are three tables so that teams can work in parallel if need be. The fifth tableview is for documenting OKR's as one of the main outputs of the OKR's at Portfolio Level:

Key Results - Output Table⁠

, in the

2.4 Key Outputs⁠

Page. Finally, the sixth connected view is located in the

3.6 Key Information Radiators⁠

page. This is for the purpose of updating and showing OKR progress.

2.3 Epics and Enablers

⁠

Epics and Enablers - Base Table⁠

- This is the table used for establishing initiatives in the form of Epics and Enablers. This is actually the heart of this CODA Doc because it is the base of the Portfolio KanBan Board. This table is used for the remaining events and tasks that are needed in the process. This table uses the

Key Results - Base Table⁠

as a Look-Up table for the Objectives and Key Results that created each initiative (Epic and Enabler). There are several connected views used in different stages of the process:

⁠

Epics and Enablers - Brainstorming Event Table⁠

view is used for the brainstorming of new Epics and Enablers, based on the Enterprise Wide OKR's. For this to work, Scrum Master/Product Owner must create at least one row for each key result in the

Epics and Enablers - Base Table⁠

⁠

Epics and Enablers - Output Table⁠

view is used to document all Epics and Enablers added to the Funnel at the Portfolio KanBan Board. It is an easy view to check all the epics and enablers and compare them.

⁠

Epics and Enablers - Reviewing Stage⁠

view is used exclusively for the Epic/Enabler Owner to work and deepen the knowledge on the subject of the Epic or Enabler. It is a Task view, and not an Event view.

⁠

Epics and Enablers - Lean Business Case⁠

view is used exclusively for the Epic/Enabler Owner to work on the Lean Business Case of the Epic or Enabler. It is a Task view, and not an Event view. However, the Epic/Enabler Owner will send this view to other team members to receive feedback when necessary.

⁠

Epics and Enablers - Go / No-Go Decision⁠

view is used for the Go / No-Go decision making event. In this event, several Epics and Enablers are presented by their Owners to the Committee, for a decision.

⁠

MVP Implementation⁠

display view is used as an information radiator table, to evaluate results from the Minimum Viable Product ongoing experiments. Epic/Enabler Owners may request frequent feedback using this view.

⁠

Persevere Implementation⁠

display view is used also as an information radiator table, to evaluate pivot or persevere decisions from the ongoing implementation experiments. Epic/Enabler Owners may request frequent feedback using this view.

⁠

Portfolio KanBan View⁠

card view is used as an information radiator to see the status of all the Epics and Enablers and how they progress along the KanBan Board.

⁠

Portfolio KanBan Stage⁠

is a Look-Up table for the

Epics and Enablers - Base Table⁠

to be used in its

Portfolio KanBan View⁠

. It includes the names of the stages and the Work in Process limits for each stage.

⁠

Portfolio KanBan WIP Status⁠

is a table to make visible the Work in Process limits of the Portfolio KanBan Board. It uses the

Portfolio KanBan Stage⁠

as a Look-Up table. It has conditional formatting to detect if the Work in Process limit has been violated. It has a connected view here,

View of Portfolio KanBan WIP Status⁠

, so that WIP violation is visible at the

3.1 KanBan Board⁠

page.

3.3 Lean Business Case

⁠

Canvas Initial Values Table⁠

is a Table used for initializing values in CODA Doc tables with Canvas Columns. It is specially used for the Lean Business Case documented in the

Epics and Enablers - Base Table⁠

. If Epic/Enabler Owners wish to change initial values in those columns, they should do so here.

Other Stuff

⁠

Roles and responsibilities⁠

is a table for planning purposes of the whole process of Modern Strategic Planning.

⁠

Roles⁠

is a Look-Up table for roles.

⁠

Committees⁠

is a Look-Up Table for Committees.

⁠

Responsibilities⁠

is a Look-Up Table for all responsibilities during the process.

⁠

Images⁠

is a Table for including images throughout the document.

⁠

Navigation Bar

⁠

Header Page...

⁠

CODA Doc Administration Header Page. This area is directed to Strategic Planning Team Members; especially those wearing the Scrum Master or the Product Owner hat. You may also use me, as a Consultant in your Modern Strategic Planning process.⁠

⁠

Home...

⁠

Lean-Agile Portfolio Management for a Modern Strategic Planning Content Page. The main purpose of this CODA Doc is to create visibility and document the whole process of Modern Strategic Planning. Find here a Happy Path - A simple RoadMap to go down to Business immediately, or take the Learning Path towards Lean-Agile.⁠

⁠

Next...

⁠

Business Model Design Space Tables Administration Page. Here you will find all the Backend tables associated to Business Model Design Space.⁠

⁠

Business Model Design Space Tables

1.1 Business Model Design Space

1.2 Baseline Business Model Canvas

1.3 FOAR Analysis

1.4 Blue Ocean

1.5 Portfolio Vision

1.6 Operational Value Streams (OVS)