---
title: CTP Topic 4 Using Agile to run the Cloud Transformation Program
type: cloud-learning
source-type: video
category: DevOps & SRE/10_OpenText-Series
tags:
  - Agile
  - Cloud-Transformation
  - CTP
date-added: 2026-04-14
video-source: nas:///volume2/work/Public Cloud Learning Sessions/CTP _ Topic 4_ Using Agile to run the Cloud Transformation Program.mp4
audio-source: ""
status: summarized (Gemini 摘要)
---

# CTP Topic 4 Using Agile to run the Cloud Transformation Program

**Source:** NAS `/volume2/work/Public Cloud Learning Sessions/CTP _ Topic 4_ Using Agile to run the Cloud Transformation Program.mp4`

**Type:** VIDEO | **Category:** 10_OpenText-Series

**Status:** 🟡 Awaiting Whisper transcription → Summary

---

## 摘要

> ## Agile Framework and Cloud Transformation Program

Heather Norris, project manager on the cloud transformation program, discussed the agile principles and methodologies used, covering the journey from its start to current practices, and offering tips for future improvements. Key aspects of agile include team collaboration and communication. The presentation covered agile frameworks, ceremonies (meetings), plan and board activities, and key takeaways.

The program initially used the Scrum framework with two-week sprints, which included product backlogs, sprint planning, retrospectives, reviews, and daily scrums. *The big problem with Scrum, in my opinion, is that you can't make changes throughout the sprints, we are not advised to.* Due to the inevitable changes in the program, a transition to a Kanban structure with continuous flow was necessary. Kanban allows changes at any time and focuses on continuous delivery rather than releases at the end of each sprint. The current framework is a hybrid, primarily using Kanban but retaining fixed ceremonies from Scrum, specifically daily stand-ups and retrospectives.

Daily stand-ups are designed to quickly inform everyone of what's going on in the team. These sessions should be brief (15-30 minutes) and focus on updates reflected in the planner board, answering what was completed yesterday, what's being done today, and any blockers. Retrospectives are important for rapid feedback and improving the development culture, helping to understand what's working well and what's not. *Agile is all about getting that rapid feedback to make the product and make the, you know, the development culture better.* Action items with owners should be detailed to drive improvements.

The Microsoft Planner board is used to manage projects, add user requirements, and centralize information. The board follows a Kanban structure with columns for backlog, to do, in progress, program key decisions, and icebox. Key practices include assigning a single owner to each task, even with multiple contributors, and clearly defining roles such as oversight. Linking dependent cards and using priorities and due dates are also crucial. Changes to prioritization, dates, owners, or progress should always be communicated with comments on the cards.


---

## 关键概念

-

---

## 行动项

-

---

## 相关视频

> 配对视频笔记链接（生成后填入）

---

*最后更新: 2026-04-14*
