Skip to content

Commit e060ff3

Browse files
authored
Fix headline level, and Status section (#255)
1 parent 194838e commit e060ff3

File tree

1 file changed

+11
-10
lines changed

1 file changed

+11
-10
lines changed

patterns/2-structured/crossteam-project-valuation.md

Lines changed: 11 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -7,23 +7,23 @@ Cross-Team Project Valuation
77
It's hard to sell the value of cross-team, inner sourced projects that don't provide a direct impact on company revenue.
88
Here's a data-driven way to represent your project that both articulates its value and amplifies it.
99

10-
# Context
10+
## Context
1111

1212
* You are responsible for a cross-team that serves as a platform for others in the company.
1313
* The cross-team project does not deliver any direct value for company revenue.
1414

15-
# Problem
15+
## Problem
1616

1717
Cross-team projects can potentially have a very large impact on the company yet are difficult to represent in a data-driven fashion.
1818
As a result, it is easy and common to either pursue projects that does not provide real value or to underfund what would otherwise produce great value.
1919

20-
# Forces
20+
## Forces
2121

2222
* Projects need to show value (objective or subjective) to company leadership in order to be funded.
2323
* Cross-team project value is dispersed across multiple end business units.
2424
* Due to this dispersal, cross-team project value is difficult to measure directly.
2525

26-
# Solution
26+
## Solution
2727

2828
Set in place a pattern and model of how to value cross-team projects.
2929
Such models give us the tool that we need to focus and amplify high-value collaboration for the company.
@@ -81,25 +81,26 @@ Some may be concerned about the lack of accuracy in this valuation approach. It
8181
In-practice, as long as these valuations are within an order-of-magnitude of reality and one-another, they are sufficiently accurate to fill these purposes.
8282
They will provide a head-and-shoulders improvement in on-the-ground results over the ad-hoc valuations (and resultant effects) described in the **Problem** section at the beginning of this document.
8383

84-
# Resulting Context
84+
## Resulting Context
8585

8686
* Data-driven means to discuss the value and funding of the cross-team project with leadership.
8787
* Key metrics around the cross-team project instrumented in raw form.
8888
* Defining how the cross-team project provides value tends to lead to it actually producing greater value for the company.
8989
* Generally-successful project and "buzz" around it.
9090

91-
# Known Instances
91+
## Known Instances
9292

9393
* Nike
9494

95-
# Authors
95+
## Authors
9696

9797
* Russ Rutledge
9898

99-
# Acknowledgement
99+
## Acknowledgement
100100

101101
* Jeremiah Wright for teaching me to think about cross-team projects as an internal business dealing in the currency of developer time.
102102

103-
# State
103+
## Status
104104

105-
Proven in multiple domains.
105+
* Structured
106+
* Old status: Proven in multiple domains.

0 commit comments

Comments
 (0)