How a Custom PMO System Boosts Development Efficiency and Cuts Management Costs

Background

MaFengWo's transportation and hotel development teams use a bi‑weekly PK and iteration model. To achieve efficient and transparent development, they adopted TAPD for full‑cycle project management because of its easy configuration, mobile support, and strong project isolation.

Requirement Classification

Requirements are divided into three categories: daily, project, and online issues. Daily and project requirements follow a two‑week and four‑week iteration cycle respectively, with nine common status states managed in TAPD.

PMO Daily Operations

For each requirement, five roles (PM, product manager, developer, tester, PMO) have specific tasks at each status stage, such as creating enterprise WeChat groups during the "Ready for Implementation" stage, holding daily stand‑ups during development, sending daily test reports, and issuing release notifications after deployment. These repetitive tasks are often scattered across emails and chat groups, making later retrieval difficult.

PMO System Design Goals

Unify all requirement‑related information in TAPD, including stand‑up minutes, test reports, and release notices.

Support multiple business lines with configurable iteration schedules, email groups, and WeChat groups.

Automate processes such as group creation and message/email synchronization.

Enable parallel requirement management and risk control.

Facilitate knowledge accumulation and sharing.

Automatically generate weekly summary reports for business leaders.

Main Functions and Implementation

Overall Design

The PMO system integrates TAPD and Enterprise WeChat APIs to collect and process data across multiple business lines.

Key Features

Iterative Management : Before PK meetings, the system gathers pending PK requirements from TAPD and sends a consolidated list to the "Pending PK" group; after meetings, it posts "Ready for Implementation" summaries to the bi‑weekly PK group.

Weekly Progress Summaries : Every Friday at 6 pm, the system emails and messages the current iteration progress and delay status for each business line.

Automatic Group Creation : When a requirement enters "Ready for Implementation", a dedicated WeChat group is created; the group name updates as the status changes.

Automated Messaging and Emailing : The system scans requirement comments for keywords (stand‑up minutes, test reports, delay risks, release notices, online effect follow‑up) and sends corresponding messages or emails.

Progress Alerts : Based on status changes, the system automatically sends Kick‑Off, test, and delay notifications.

Data Statistics : Provides statistics on effort, iteration, and quarterly metrics to support KPI planning.

Knowledge Management : Stores process documentation and PM knowledge for onboarding new team members.

Implementation Effects

All requirement information is centralized in TAPD, simplifying lookup.

Risk extraction and group notifications help PMO focus on high‑risk items.

Automated Kick‑Off, test, and stand‑up notifications save significant PM time.

Weekly release summaries reduce product managers' reporting workload.

Developers and testers receive automatic test and release emails.

Knowledge base accelerates newcomer onboarding.

Future Plans

The PMO system will be integrated with a newly developed DevOps platform, enabling automatic status synchronization between TAPD and DevOps, further reducing manual updates and improving the precision of delay risk alerts.