51 lines
2.3 KiB
Markdown
51 lines
2.3 KiB
Markdown
---
|
||
title: "CTP Topic 57 Product backlog managing demand"
|
||
type: source
|
||
tags:
|
||
- Product-Backlog
|
||
- Demand-Management
|
||
- Agile
|
||
- CTP
|
||
date: 2026-04-14
|
||
---
|
||
|
||
## Source File
|
||
- [[raw/Cloud & DevOps/Public-Cloud-Learning-Sessions/10_OpenText-Series/ctp-topic-57-product-backlog-managing-demand.md]]
|
||
|
||
## Summary
|
||
- 核心主题：Product Backlog（产品待办列表）管理需求
|
||
- 问题域：云转型计划（CTP）中的需求管理与优先级排序
|
||
- 方法/机制：通过 SMACs 提交需求、双周会议评审、20题计算器评估、Octane 入池、前置条件准备阶段
|
||
- 结论/价值：实现需求透明度和优先级评估标准化，确保所有需求在同一标准下被审视
|
||
|
||
## Key Claims
|
||
- 需求必须通过 SMACs 提交以启动计时器和确保追踪
|
||
- 每周双次会议评审需求的价值和优先级，计算器评估复杂度、成本和野心
|
||
- 新团队需经过前置条件准备阶段才能进入 Octane
|
||
- Sprint 规划通常提前 6 个迭代，50% 分配给新需求，50% 给支持工单和技术债务
|
||
|
||
## Key Quotes
|
||
> "We need a way to make sure it's transparent and we're holding everything up to the light and looking everything for the same lens as we are."
|
||
|
||
> "It means that for ADM they can effectively plan all of the work that's going into their sprints with the engineers that are working solidly on their work."
|
||
|
||
## Key Concepts
|
||
- [[Product-Backlog]]：存放待开发功能的区域，高亮需求、收益和优先级
|
||
- [[SMACs]]：Service Management Access，用于提交新需求的标准化入口
|
||
- [[Octane]]：数字化产品管理平台，需求评估后移入为特性
|
||
- [[前置条件阶段]]：产品团队进入企业级 Landing Zone 转型旅程的准备阶段
|
||
- [[Sprint-规划]]：提前约 6 个迭代规划工作，50% 新需求 + 50% 支持工单/技术债务
|
||
|
||
## Key Entities
|
||
- [[Matthew-Chapman]]：需求评审会议主持人
|
||
- [[David-Grant]]：需求评审会议参与人
|
||
- [[Brendan]]：需求评审会议参与人
|
||
|
||
## Connections
|
||
- [[CTP]] ← manages_demand ← [[Product-Backlog]]
|
||
- [[SMACs]] ← triggers ← [[Demand-Tracking]]
|
||
- [[前置条件阶段]] ← precedes ← [[Octane]]
|
||
- [[Sprint-规划]] ← includes ← [[Demand-Allocation]]
|
||
|
||
## Contradictions
|
||
- 邮件或聊天可作为初始联系方式，但 SMACs 是最可靠的追踪方式 |