Lessons in Scope Management for an Information System Project

The case study describes an eight‑month, 8.94 million‑yuan smart‑device project commissioned by a provincial operator to create a companion device for senior users, integrating AI, a proprietary OS, an audio app, and big‑data services.

Project background and challenges : limited hardware resources, a tight 8‑month timeline, lengthy product definition and ID design phases, and extensive certification (CCC, RoHS, CTA, SRRC) created high risk for scope, schedule, and cost.

Scope‑management process :

Define scope – clarified goals and functional requirements through market, technical, and user interviews.

Document scope – produced a detailed scope statement reviewed with stakeholders.

Control scope – established a change‑management workflow, held regular stakeholder meetings, monitored progress, and corrected deviations promptly.

Key scope‑management practices :

Clearly define project scope and objectives at initiation.

Create a comprehensive scope statement.

Control scope changes and avoid scope creep.

Manage and trace requirements.

Maintain strong communication with all parties.

Work Breakdown Structure (WBS) development :

Determine project goal – a senior‑friendly companion device.

Decompose the project into major tasks such as market research, product definition, ID design, structural design, hardware development, software development, and testing.

Detail each task into sub‑tasks or work packages (e.g., concept design, preliminary方案, review, refinement for ID design).

Identify task dependencies and sequence to schedule work logically.

Define schedule and budget for each (sub)task based on the WBS.

Three decisive strategies that ensured delivery :

Re‑anchor goals and priorities – shifted focus from “perfect first release” to a “core‑experience, fast‑to‑market” version, freezing non‑essential features.

Establish a “wartime” coordination mechanism – daily cross‑department stand‑ups, on‑site alignment with mold and PCBA factories, and immediate issue resolution.

Parallelize long‑cycle tasks – pre‑reviewed certification documents and test samples, converting serial activities into concurrent ones to compress time.

These actions led to successful system launch on September 12 and delivery of the hardware to the client’s warehouse, generating significant GMV. The author reflects that effective scope management and a well‑crafted WBS are essential for project clarity, feasibility, and control, while noting remaining improvement areas such as deeper user‑need analysis and tighter task sequencing.