The author reflects on transitioning from hardware to pure software project management, outlines a B2B e‑commerce order‑platform reconstruction case, details goals, budget, team composition, core challenges, agile‑milestone execution, risk mitigation, outcomes, and personal growth insights.
This guide explains why projects often fail, defines project management, and walks through the five essential phases—initiation, planning, execution, monitoring, and closure—providing practical steps, key metrics, and visual tools to help teams deliver results on time, within budget, and with quality.
Technical project managers drive complex initiatives by translating business needs into feasible solutions, planning milestones, allocating resources, managing risks, and coordinating cross‑functional teams through design, testing, deployment, and closure, while using tight schedules, daily checkpoints, and transparent reporting to balance quality, speed, and reusable outcomes.
This article outlines a comprehensive, step‑by‑step approach for SRE incident commanders, covering fault perception, grading, team organization, remediation tactics, transparent communication, and post‑mortem practices to efficiently resolve service disruptions.
The article teaches developers essential project‑management skills—schedule, quality, and risk management—by explaining why coordination matters, outlining common pain points, and detailing practical techniques such as two‑day task decomposition, code‑review standards, and systematic risk identification and mitigation to become reliable, results‑driven partners.
This article outlines the most common mistakes new CTOs make—from mismatched skills and resources to neglecting monitoring and responsibility—and offers practical guidance on how to align engineering teams, balance vertical and horizontal tasks, and lead startups effectively.
This article explains the differences between remote and distributed software teams, outlines the advantages of a distributed model, and provides practical strategies, tools, and communication techniques for effectively coordinating and leading large, multi‑location development projects.
This guide explains the purpose of weekly reports, outlines how to tailor them for supervisors, teams, and personal reflection, and provides structured templates, the STAR principle, and efficiency tips to help technical managers write clear, data‑driven, and actionable reports.
This article explains the importance of standardization in multi‑party research projects, outlines the roles and responsibilities of each team member, and details a comprehensive 12‑step workflow—from demand communication to project settlement—to improve quality, coordination, and efficiency.
During the early COVID‑19 outbreak, Suning’s self‑developed remote‑office tool Douya was rapidly reconfigured, opened to external users, and continuously upgraded within days, showcasing an intense emergency development process that mobilized over 80 engineers to support millions of remote workers.
This comprehensive guide explains how technical professionals can excel as project managers in internet companies by defining clear goals, aligning people and processes, and navigating each phase—from project initiation and requirement review to scheduling, testing, release, and post‑mortem—ensuring timely, high‑quality delivery.
This article explores the core competencies that distinguish a truly professional project manager, emphasizing the importance of goal‑oriented thinking, effective communication, risk identification, and strong negotiation skills while highlighting common pitfalls and the need for clear appointment and exit criteria.
Using the popular game 'Honor of Kings' as a metaphor, this talk explores core project management concepts—including integration, human resource, communication, stakeholder, and post‑mortem practices—illustrating how game strategies can inform effective team coordination, task allocation, and project success within a tech organization.
This article recounts LEGO’s Digital Solutions department’s journey of scaling agile across 15‑20 teams through a two‑day, large‑room PI planning event, detailing the challenges, the introduced practices, outcomes, and ongoing refinements to improve cross‑team alignment and delivery.
As smartphones become full‑featured computers, traditional PC/M functionalities are migrating to mobile apps, causing teams to face pre‑, mid‑, and post‑development challenges such as coordination friction, technical debt, and high coupling, and the article proposes concrete improvement measures including clearer collaboration, reduced coupling, parallel versioning, and iterative release cycles.
