4.1 KiB
title, type, source-type, category, tags, date-added, video-source, audio-source, status
| title | type | source-type | category | tags | date-added | video-source | audio-source | status | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CTP Topic 57 Product backlog managing demand | cloud-learning | video | DevOps & SRE/10_OpenText-Series |
|
2026-04-14 | nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 57_ Product backlog_ managing demand.mp4 | summarized (Gemini 摘要) |
CTP Topic 57 Product backlog managing demand
Source: NAS /volume2/work/Public Cloud Learning Sessions/CTP _ Topic 57_ Product backlog_ managing demand.mp4
Type: VIDEO | Category: 10_OpenText-Series
Status: 🟡 Awaiting Whisper transcription → Summary
摘要
Product Backlog: Managing Demand
This session covers managing the product backlog, including why it's needed, how it's managed, and its effects. The backlog is a holding area for upcoming features, highlighting needs, benefits, and priorities. Managing it involves understanding the value, importance, effort, and complexity of each piece of work.
New requests should be submitted through SMACs to start the timer and ensure tracking. While email or chat are acceptable for initial contact, SMACs is the most reliable method. Demand is reviewed in twice-weekly meetings with Matthew Chapman, David Grant, Brendan, and others to assess understanding, value, and priority. A calculator with about 20 questions helps determine the simplicity, cost, and ambition of each request. 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.
Once assessed, opportunities move into Octane as features with task lists. New teams undergo a prerequisite phase to align expectations and understand product needs. Planning involves mapping out upcoming work and important dates, typically six sprints ahead. Sprints allocate around 50% for new demand and 50% for support tickets and tech debt. Larger product groups like ADM and ITOM have fortnightly sessions to align plans and priorities. 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.
The prerequisite phase is crucial for product teams entering the transformation journey to the enterprise landing zone. It addresses questions about checklists, end goals, and stakeholder involvement. This phase gathers business and technical requirements, translating them into workable designs. Key components include introductory sessions, AWS account creation (reviewed with the PCG team), solution design and refinement, GitHub repository creation, and firewall tag definition. The effort estimate for the product team is about two hours, spread over one or two weeks.
After the prerequisite phase, SRE engineers build the account and hand it over, providing access details for the console and GitHub. A short demo of EC2 instances and other resources is given, along with CTP training videos. Two weeks of hyper care support is provided post-handover.
Existing product groups can request support via SMACs, email, or Teams. The support team assesses risk, complexity, and urgency. Defects are addressed in the current sprint, assigned to the original squad. A Teams channel is created for communication between the product group, SRE engineer, solution architect, and delivery manager. Change requests or enhancements are discussed with the solution architect to integrate them into the existing account.
Different support request types include adding VPCs, creating subnets, and managing roles/tags. Public subnets are generally restricted to production environments. The team provides guidance on using Atlantis or grant forms for self-service tasks. For urgent requests, the team assesses capacity and dependencies, potentially requiring additional approval from networking. Communication involves agreeing on timelines and providing updates through the Teams channel. Standard videos and wiki pages are shared for common requests.
关键概念
行动项
相关视频
配对视频笔记链接（生成后填入）
最后更新: 2026-04-14