導入敏捷開發 - 讓團隊運作更流暢

Open in ChatGPT Open in Claude

歡迎收聽 Mark 的技術雜談，我是主持人璦廷。當團隊不斷擴大，你是否也覺得每天的會議越來越多，甚至壓縮了實際開發的時間呢？讓我們來看看今天的文章，作者分享了為了解決頻繁同步工作的痛點，決定導入敏捷開發的實戰經驗。這個重點值得注意，導入敏捷的目的不僅是減少重複會議，更是為了讓團隊專注於每兩週的交付，透過持續產出讓客戶安心，同時提升整體的資訊透明度。在實際運作上，團隊重新調整了會議結構。每天的站立會議嚴格控制在十五分鐘內，只聚焦昨日進度、今日目標與遇到的困難。而每兩週一次的規劃與審查會議，則確保了衝刺目標的確立與成果展示。特別的是，團隊採用輪流展示的制度，讓每位成員都有機會學習程式整合，藉此揪出開發盲點。總結來說，敏捷開發並非死板的框架，而是能依據現況彈性調整的工具。聽完今天的分享，不妨思考看看，你的團隊目前最需要簡化的溝通環節又是哪一個呢？

Podcast ConversationAI dialogue version of this article · Mandarin audio

Introduction

As the team grew, so did the number of meetings and repetitive tasks. We used to have two sync meetings a day, one in the morning and one in the afternoon, which felt like a waste of time because we'd have to sync up again before we had even finished our work. After a discussion with my boss, we decided to adopt Scrum.

Purpose of Adopting Scrum

To reduce repetitive meetings.
To have the team focus on bi-weekly deliverables. When users see updates every two weeks, they won't feel the need to constantly chase us for progress.
Continuously receiving feedback from customers or stakeholders helps the team understand requirements and make corresponding adjustments.
To identify problems sooner. Issues can be raised and resolved during daily meetings (e.g., progress, incorrect work item estimates).
To help everyone understand the purpose and value of their work, not just focus on the task at hand.
To make team operations smoother.
To increase transparency.

Adjustments to Meetings

1. Morning Sync with US Colleagues

This meeting is optional. We don't discuss the specifics of our work, only matters that require coordination or assistance with our US colleagues.

2. Planning Meeting (Bi-weekly): To decide which items to complete in the upcoming sprint (led by the PM).

(Held on the first day of every two-week cycle. Considering that the current members are all new, we will temporarily skip story point estimation to avoid spending too much time on it.)

3. Daily Stand-up Meeting: Daily Scrum

A 10–15 minute meeting each day that must not run over time. The goal is to keep the team in sync. (Please update your Jira ticket statuses beforehand.)

What did I complete yesterday?
What will I do today?
Are there any impediments in my way? What are they?

4. Bi-weekly Review Meeting: To demonstrate the results of the current sprint and gather feedback and new requirements.

(Held on the first day of every two-week cycle. We use a rotating system for demos. Everyone is expected to learn how to integrate the work, as this is when we often discover blind spots in our code design.)

P.S. Agile methodologies are often adapted to fit a company's specific situation; they are rarely applied directly out of the box. Due to the current high number of meetings, we are temporarily skipping the retrospective meeting.

#management #agile #scrum #team #meeting