What Scope Management Lessons a Telecom Smart‑Terminal Project Taught Me

Abstract – In January 2023 the author’s company won a multi‑million‑yuan smart‑terminal customization contract for a provincial telecom operator. The 8‑month project required delivering a senior‑friendly companion device that integrated AI, a proprietary OS (XXOS), an audio app (XXAPP), and big‑data services. Acting as project manager of an 18‑person team, the author applied a formal scope‑management plan—collecting requirements, defining scope, building a Work Breakdown Structure (WBS), and controlling changes—to finish on schedule (September 12) and meet all hardware delivery and acceptance criteria.

Project Background and Challenges – The contract (¥8.94 million) demanded hardware manufacturing, software development for Android/iOS, voice‑wake‑up, custom content, a mini‑program, and an XXOS backend. Key constraints included a fixed 8‑month timeline, long hardware‑certification cycles (75 days for CCC, RoHS, CTA, SRRC), a 30‑35 day mold‑making critical path, limited internal development resources, and frequent scope changes during product definition and ID design.

Scope‑Management Process –

Define Scope : Clarified the goal of creating a senior‑focused companion device by consulting market, technical, and user representatives.

Document Scope : Produced a detailed scope statement and obtained stakeholder sign‑off in review meetings.

Control Scope : Established a change‑management workflow, conducted regular stakeholder communications, monitored progress, and corrected deviations promptly.

The author emphasizes that strict WBS and change‑control practices kept the project aligned with its objectives.

Key Scope‑Management Practices

Clearly define project scope and objectives at initiation.

Prepare a detailed scope statement to align expectations.

Control scope changes through formal review and approval.

Prevent scope creep by maintaining constant communication with stakeholders.

Manage and trace requirements throughout the lifecycle.

Establish robust communication mechanisms across all involved parties.

Work Breakdown Structure (WBS) Development – The author followed five steps:

Identify the overall project goal (senior‑market companion device).

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

Further break down each task into sub‑tasks (e.g., concept design, preliminary方案, review, refinement for ID design).

Determine logical dependencies and sequencing among tasks to create a realistic schedule.

Assign timeframes and budgets to each (sub)task, enabling precise progress and cost control.

Summary and Reflection – The author distilled three decisive strategies:

Re‑anchor goals and priorities, shifting from a “perfect first‑release” mindset to a “core‑experience, fast‑to‑market” version.

Establish a “wartime” cross‑functional collaboration mechanism, holding daily stand‑ups and onsite alignment with suppliers to eliminate communication loss.

Parallelize long‑cycle activities (e.g., pre‑review certification documents and prototype testing) to compress schedule.

These actions led to successful delivery and the creation of a hardware‑front‑decision checklist that now mandates supply‑chain feasibility reviews at project initiation. The experience reinforced that embedding manufacturing thinking early in product definition and actively managing risks are the highest‑value contributions of hardware supply‑chain management.

Overall Conclusion – Effective scope management and a well‑crafted WBS ensure clear objectives, feasibility, and controllability, thereby boosting execution efficiency and project success. The author also notes remaining improvement areas: deeper user‑need analysis during scope definition, tighter task‑relationship planning, and more balanced resource allocation.