--- title: "Adopting Agile Development - Making Your Team's Workflow Smoother" description: "Sharing how to introduce Scrum agile development to your team, reducing redundant meetings and improving delivery efficiency and transparency by adjusting the meeting structure (planning, stand-up, review meetings)." canonical_url: "https://blog.markkulab.net/en/post/introduce-agile-development-to-reduce-redundant-meetings" author: "Mark Ku" author_url: "https://blog.markkulab.net/en/author/mark-ku" site: "Mark Ku's Tech Notes" date_published: "2023-03-12 01:01:35 +0800" category: "Management" tags: ["management", "agile", "scrum", "team", "meeting"] language: "en" license: "CC BY 4.0" license_url: "https://creativecommons.org/licenses/by/4.0/" attribution: "when reusing or quoting, credit the author and link back to the original" --- # Adopting Agile Development - Making Your Team's Workflow Smoother > **TL;DR** — 歡迎收聽 Mark 的技術雜談，我是主持人璦廷。當團隊不斷擴大，你是否也覺得每天的會議越來越多，甚至壓縮了實際開發的時間呢？ 讓我們來看看今天的文章，作者分享了為了解決頻繁同步工作的痛點，決定導入敏捷開發的實戰經驗。這個重點值得注意，導入敏捷的目的不僅是減少重複會議，更是為了讓團隊專注於每兩週的交付，透過持續產出讓客戶安心，同時提升整體的資訊透明度。 在實際運作上，團隊重新調整了會議結構。每天的站立會議嚴格控制在十五分鐘內，只聚焦昨日進度、今日目標與遇到的困難。而每兩週一次的規劃與審查會議，則確保了衝刺目標的確立與成果展示。特別的是，團隊採用輪流展示的制度，讓每位成員都有機會學習程式整合，藉此揪出開發盲點。 總結來說，敏捷開發並非死板的框架，而是能依據現況彈性調整的工具。聽完今天的分享，不妨思考看看，你的團隊目前最需要簡化的溝通環節又是哪一個呢？ ## 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.) 1. What did I complete yesterday? 2. What will I do today? 3. 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. --- ## About this article and its author Originally published on [Mark Ku's Tech Notes](https://blog.markkulab.net/en/post/introduce-agile-development-to-reduce-redundant-meetings) License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/) — when reusing or quoting, credit the author and link back to the original ### About the author **[Mark Ku](https://blog.markkulab.net/en/author/mark-ku)** — Software Solution Provider - 10+ years senior software engineer, now an AI Builder - Focused on large-platform architecture — North-American e-commerce, AI SaaS subscription billing - Combining AI Agents and automation to build evolvable product foundations ### Free tools built by the author All of these are free to use: - [Free PDF Sign Tool](https://blog.markkulab.net/en/tools/pdf-sign): Online PDF sign tool — draw, type, or upload a signature, then drag, resize, and download. Everything runs in your browser; nothing is uploaded. - [VS Code Refactory](https://blog.markkulab.net/en/tools/refactory): Refactory is a VS Code refactoring extension: 34 actions plus a 37-rule code-smell inspection layer with a Code Health dashboard, across 18 languages, backed by 534 tests. It learns your repo's conventions: where interfaces live, where DI is registered, whether 'use client' belongs. It ranks files by git churn × complexity so you know what to fix first, and hands any smell to the Claude Code already on your machine. Free to use, and your source never leaves your computer. - [DB-Kit Database Manager](https://blog.markkulab.net/en/tools/db-kit): DB-Kit is a lightweight, cross-platform database manager built with Tauri + Rust + React. Manage MySQL, MariaDB, PostgreSQL, SQL Server, Oracle, SQLite, MongoDB, Redis, Kafka, Elasticsearch and RabbitMQ from one consistent interface: passwords encrypted in the OS keychain, SSH tunnels, full CRUD, a visual query builder, stacked multi-statement result sets, cross-connection data transfer and compare/sync, Excel / CSV import & export, visualized execution plans, ER diagrams, scheduled backups, SQL stress testing with p50–p99 latency percentiles, a 15-rule SQL review engine, Kafka message browsing with monitoring & alerts, a bilingual UI (Traditional Chinese / English), a built-in AI assistant (natural-language SQL, AI review and tuning advice) and the dbk CLI. Free and open source (MIT), with installers for Windows, macOS and Linux. - [VS Code Super Mermaid](https://blog.markkulab.net/en/tools/super-mermaid): Super Mermaid is a VS Code extension for beautiful Mermaid diagrams out of the box: auto-colored live preview, mouse pan & zoom, high-res PNG / SVG export, 21 templates and multiple themes. Free and open source (MIT). - [React Super Mermaid](https://blog.markkulab.net/en/tools/react-super-mermaid): react-super-mermaid is an open-source React component library: render beautiful Mermaid diagrams with a single , with built-in colorful / sketch themes, pan & zoom, in-diagram search, and high-res SVG / PNG export. Lightweight, SSR-safe, fully typed. Free and open source (MIT). - [Jira / Confluence Super Mermaid](https://blog.markkulab.net/en/tools/jira-super-mermaid): An Atlassian Forge app: write Mermaid syntax directly inside a Jira issue or a Confluence page and get flowcharts, sequence diagrams, state machines and Gantt charts. 11 diagram types, SVG / PNG export, light and dark themes, full CJK support. Runs on Atlassian: your diagrams live in your own site and the app calls no third-party service. Free, coming soon to the Atlassian Marketplace. - [Mermaid Live Preview](https://blog.markkulab.net/en/tools/mermaid-preview): Write Mermaid in your browser, see it render instantly, and share the whole diagram as a single link. No sign-up, nothing uploaded to a server, and mermaid.live share links work as-is. - [React Intl Phone Number](https://blog.markkulab.net/en/tools/react-intl-phone-number): react-intl-phone-number is an open-source React component: framework-agnostic and antd-free, with E.164 in/out, a searchable flag / country-code dropdown, configurable validation levels (strict / mobile-strict / loose), themeable CSS, and i18n — phone logic powered by google-libphonenumber. Lightweight and fully typed. Free and open source (MIT). - [Uptime Kuma Cluster](https://blog.markkulab.net/en/tools/uptime-kuma-cluster): Turn single-node Uptime Kuma into a highly available cluster: OpenResty + Lua smart load balancing, shared MariaDB state, health checks and automatic failover, plus cluster-management REST APIs. One Docker Compose command to start. Free and open source (MIT). - [Special Education](https://blog.markkulab.net/en/education): Learning materials crafted for special education students ### Daily podcasts - [Mark's Tech Insights — Daily AI News](https://blog.markkulab.net/en/category/tech-news): Daily curated AI and tech trends. Catch the latest developments via audio summaries — covering AI applications, software architecture, DevOps, and engineering practice. — RSS: https://blog.markkulab.net/feed.xml - [AI股市蝦聊](https://blog.markkulab.net/en/category/ai-stock-chat): Every trading day, an AI-analyzed take on the Taiwan stock market, delivered as a two-host conversation covering the session and the next-day outlook. — RSS: https://blog.markkulab.net/ai-stock-chat/feed.xml - [開源好物週報](https://blog.markkulab.net/en/category/open-source-weekly): A weekly two-host pick of free open-source tools surfaced from real Hacker News, GitHub, and Reddit buzz — what pain they solve and the fastest way to get started. — RSS: https://blog.markkulab.net/open-source-weekly/feed.xml ### Newsletter [Subscribe to the newsletter](https://blog.markkulab.net/en/subscribe) — Be the first to know about new posts. No spam, unsubscribe anytime.