Story
Atlassian
John DeereJohn Deere Brings Cross-team Delivery onto Atlassian
John Deere, an industrials organization in the United States, uses Jira Service Management from Atlassian to support program management for project and operations leads.
John Deere folded Jira Service Management into program management so project and operations leads share one view of cross-team delivery.
“Inside John Deere, program management used to depend on whoever still had the latest file.”
“Project and operations leads needed a system that would still make sense after the original project team moved on.”
Independent write-up. Figures come from public sources or are illustrative.
Value results
| Category | Value result |
|---|---|
| Capability | Cross-team delivery can be reviewed without waiting on a personal export |
| Capability | Named workflow replaces ad hoc routing for cross-team delivery |
| Capability | Program management stays visible to adjacent teams through Jira Service Management |
Story
Inside John Deere, program management used to depend on whoever still had the latest file. That pattern is common in industrials groups working out of the United States. Project and operations leads needed a system that would still make sense after the original project team moved on.
John Deere uses Jira Service Management from Atlassian as the working layer for cross-team delivery. Atlassian provides work management and DevOps software, including Jira and Confluence, used by software and business teams. The practical change is simple: program management has a home, and reviews happen there instead of in a forwarded thread.
Nothing in this writeup invents a savings number. What John Deere gets from Atlassian is a durable place to run program management and a way for project and operations leads to see the same cross-team delivery at the same time.
