Mastering Internet Project Workflow: Roles, Timelines, and Postmortems

Introduction

互联网公司常见工种有哪些？

In an internet project, multiple roles collaborate: product, development, testing, operations, UI design, and more. Coordination occurs both linearly and across departments to ensure smooth project initiation, development, testing, and launch.

Cross‑department collaboration examples:

Product stage: Services in product A require another department to develop supporting services, requiring coordination of timelines.

Development stage: Teams define interfaces, schedule, and joint integration for cross‑department features.

Testing stage: Tests are performed according to product functional nodes, development processes, and interface specifications.

Timeline Definition

Level: ⭐⭐⭐⭐

Item: Define project development milestones

Participants: Business, product, development lead, testing lead, architect, core project members

Description: A clear timeline, often driven by product or project manager, aligns business, product, PRD hand‑over, development, testing, and release dates to avoid bottlenecks and reduce risk.

Resource Allocation

Level: ⭐⭐⭐

Item: Development resource allocation

Participants: Architects, developers, testers

Description: Development involves the full lifecycle from engineering to testing and release. Resource effort varies by phase and should be proportioned (e.g., 1 = 100%, 0.8 = 80%). Improper allocation can cause delayed testing or insufficient bug fixing, increasing project risk.

Development, Testing, and Release Phase

Level: ⭐⭐⭐⭐

Item: Development, testing, release

Participants: Developers, testers, architects/tech leads

Description: Developers receive product requirements, design, and lead design reviews involving multiple roles. Proper design ensures efficient resource use and future scalability. Development must produce unit‑tested code, test reports, and interface documentation. After testing, a release report is issued, and product/operations prepare configurations and permissions for launch.

Project Retrospective

Level: ⭐⭐⭐⭐

Item: Project retrospective

Participants: Development and testing teams

Description: Retrospectives summarize technical and business lessons to prevent recurrence. Topics include:

Database Review

Adjust connection pool size according to business load.

Avoid complex nested queries and functions in business queries.

Strengthen duplicate‑prevention fields.

Initialize index fields and optimize slow queries.

Business Review

Standardize marketing scenario designs and cache consistency.

Enhance duplicate‑prevention in financial settlement flows and simulate diverse test scenarios.

Scale external system dependencies with traffic‑based stress‑test reports.

Increase code‑review rigor for core functionalities and continuously optimize as load grows.

Regularly review and improve code quality on the development side.

Maintain proper branch management during development, testing, and release to avoid merge chaos.

Monitor and log all business process configurations for quick anomaly tracing.

Conduct full‑link stress tests for core scenarios to ensure quality and reduce traffic risk.

Feature Review

Optimize logic encapsulation, caching, threading, and validation.

Ensure complete logging of inputs, outputs, and exceptions.

Set timeout and retry policies for external API calls.

Address urgent exception displays and reproduce issues in test environments.

Deployment Review

Deploy services according to stress‑test standards.

Use dual‑ or triple‑data‑center setups for core services.

Isolate RPC interfaces for non‑core services.

Adjust JVM, connection limits, and logging parameters as needed.

Interface Review

Validate functional completeness.

Retest exception flows.

Define monitoring scope for data metrics.

Perform regular post‑release checks.

Conclusion

Medium‑to‑large internet projects involve many processes that must be carefully controlled; otherwise, risks arise and timelines slip. While small feature iterations can be streamlined, thorough analysis, retrospectives, and knowledge sharing create valuable technical assets that help newcomers and foster continuous improvement.