This article presents a detailed glossary of core project management terminology, covering basic concepts, overall management, scope, schedule, resource, cost, procurement, quality, risk, and communication aspects, each paired with its standard English translation.
This article presents a comprehensive mind map that outlines the core concepts, tools, techniques, improvement methods, and organizational approaches of project quality management, with visual diagrams and a link to the full mind map for deeper reference.
This article provides a detailed overview of Maven, covering its purpose, project structure, build lifecycle phases, dependency coordinates and scopes, repository types, plugin mechanisms, aggregation and inheritance, as well as flexible configuration using properties and profiles, all illustrated with practical code examples.
A senior IT leader’s frustration with a middle‑platform project reveals how vague goals, insufficient budgeting, lack of real business scenarios, and misaligned expectations between management and consultants can doom enterprise transformation initiatives, offering hard‑earned lessons for future R&D managers.
In this reflective article, a former front‑end expert at Alibaba shares half a year of personal growth, detailing how he learned to challenge authority, improve mature technical systems, manage project risks, communicate effectively with product designers, and build professional credibility as a project manager.
This article shares practical strategies for interaction designers to identify and avoid common pitfalls across project initiation, execution, and closing phases, enabling faster, more reliable launches of time‑sensitive activity projects through early involvement, visual workflow mapping, modular components, and coordinated communication.
This article demonstrates how agile principles can be applied to wedding planning by defining clear goals, brainstorming ideas, creating a user‑story map to manage complex tasks, and conducting a post‑event review to assess outcomes and capture lessons for future improvement.
Linus Torvalds explains that developers often overestimate delegation and code importance, emphasizing that user needs trump code quality, that appropriate workflows matter more than tools, and that trust, proper use of SCM, and open communication via mailing lists are key to successful large‑scale projects.
The article follows architect Da Liu’s frustration over being passed over for promotion, revealing seven practical strategies—from reading diverse code and accurately judging project direction to mastering meeting management and version control—that can help engineers transform technical expertise into career advancement.
A project manager recounts how poor quality focus, insufficient team oversight, lack of design, uncontrolled requirement changes, and missing code reviews led to a disastrous rollout, and shares the corrective actions and key lessons to avoid similar failures in future software projects.
The article describes how a software team introduced a 15‑minute daily Scrum standup, defined its participants, duration, and agenda through brainstorming, and observed improved visibility of progress, reduced delays, and enhanced communication, with plans to add a Kanban board for further optimization.
This article explains how the 58APP platform identified design‑consistency problems across its many business lines, defined efficiency, quality, and verification goals, built shared interaction and UI component libraries, established data‑driven metrics, and achieved measurable improvements in publishing rates and overall user experience.
This article compares the traditional Waterfall model with Agile approaches like Scrum, outlining their origins, advantages, disadvantages, key roles, processes, and how teams can balance both methods to improve project delivery and avoid common pitfalls.
The article outlines dubbogo's five‑year evolution, its milestone‑driven roadmap, the launch of dubbo-go-proxy, community recruitment, management practices, tooling, code‑quality measures, and future challenges, providing a comprehensive view of this Go‑based backend framework.
This article concludes a four‑part time‑management series by exploring effective task delegation through the “monkey” metaphor, outlining seven practical steps—from explaining task importance to regular follow‑up—and emphasizing how clear communication and responsibility assignment improve team productivity.
In this candid post, a former technical director shares a three‑month case study of team mismanagement, detailing four critical mistakes—over‑estimating talent, under‑estimating project difficulty, spreading resources too thin, and neglecting proper management—along with reflective insights and actionable lessons for future leaders.
The article outlines three progressive stages for technical staff—from merely following PRD specifications, to understanding business needs and selecting appropriate solutions, and finally to proactively shaping business strategy—while sharing practical methods for demand exploration, project initiation, management, and data‑driven iteration.
This article explains the importance of quality management in projects, outlines its two main dimensions—process quality and product quality—details the multiple benefits of systematic quality control, and provides an eight‑step framework for creating an effective quality management plan.
This reflective article shares 23 practical lessons learned at Alibaba, covering mindset, structured thinking, communication, execution, personal growth, and promotion strategies to help professionals accelerate their careers and lead projects more effectively.
The article recounts Redis creator Salvatore Sanfilippo’s decision to step back from core development, explains his fatigue with open‑source maintenance, outlines the pressures he faced, and discusses how mature projects like Redis can continue thriving after a founder’s departure.
Youzan’s Efficiency Improvement team introduced project‑based management to bring transparency, empower part‑time PMs, and foster self‑organization, then layered Large‑Scale Scrum across component teams, enabling dynamic equilibrium between order and chaos and evolving the R&D organization toward agile, scalable efficiency.
The article compares large‑scale, highly regimented development teams with small, autonomous squads, explaining how the latter achieve faster delivery, higher innovation, and better resource efficiency while still handling complex projects, and discusses Conway's Law and practical implications for modern software organizations.
This article shares practical principles, mindset tips, and concrete planning methods for engineers who want to continuously improve their technical skills, overcome common career dilemmas, and become effective architects and leaders despite a busy workload.
This article details how JD.com’s retail teams collaboratively designed, built, and launched the lightweight Jingdong Fast Version mobile app in early 2020, outlining the project’s tight timeline, cross‑team coordination, technical architecture, design simplifications, and the successful on‑time release despite pandemic constraints.
This article explains agile testing principles, contrasts them with traditional waterfall testing, and details how the P1 project applied Scrum testing practices—short delivery cycles, daily stand‑ups, bug triage, continuous collaboration, technical excellence, and streamlined processes—to achieve rapid, high‑quality software releases.
This article identifies frequent agile‑method traps—acting like a project manager, making unilateral decisions, over‑monitoring, slow change handling, and indirect communication—and offers practical remedies to help agile leaders foster trust, autonomy, and faster delivery.
This guide outlines a complete post‑mortem (retrospective) framework—from defining types and preparing meetings to conducting effective sessions and tracking outcomes—helping teams continuously improve project execution and embed a learning‑focused culture across the organization.
This article examines how stable, non‑startup companies can develop their technical teams by addressing recruitment, personnel development, team culture, technology stack decisions, project management practices, and promotion pathways, offering practical insights for effective R&D management.
This article shares Ant Design’s multi‑year open‑source project operation experience, covering project documentation, website setup, code style, unit testing, CI services, release workflow, issue/PR templates, Git tips and community‑driven growth strategies for a frontend UI library.
The article examines how project management and agile methodologies were applied to China’s nationwide COVID‑19 response, illustrating initiation, planning, execution, risk and stakeholder management, iterative delivery, transparency, and continuous improvement through concrete examples and a structured framework.
The article shares a senior software architect’s multi‑year experience outsourcing projects to India, China and the Philippines, analysing cost differentials, cultural challenges, code quality issues and when offshore development can actually succeed.
At iQIYI, Elva leads a versatile PMO that acts like a conductor—standardizing processes, tailoring Scrum, Kanban or waterfall methods, and providing varying levels of support—to coordinate over 100 concurrent infrastructure, product and live‑streaming projects, boost delivery efficiency, and raise organizational maturity without adding headcount.
This article outlines how QA engineers can maximize their impact throughout the pre‑testing, testing, and post‑testing phases of cross‑department projects by understanding system interactions, coordinating with stakeholders, designing comprehensive test cases, monitoring progress, and conducting thorough retrospectives to continuously improve delivery quality.
This article shares practical project‑management secrets from Alibaba Entertainment's PMO, outlining how to structure, coordinate, and execute massive online campaigns remotely by focusing on clear goals, right people, solid plans, effective mechanisms, and thorough retrospectives.
This article analyzes common source‑code management patterns for numerous small projects, identifies their drawbacks, and proposes a hybrid solution that combines a single‑git repository with git‑submodule based sub‑projects, automated shell scripts, and Umi‑based tooling to achieve unified yet isolated development and deployment.
This article explains how the MaFengWo PMO team built a self‑developed PMO system that centralizes requirement data, automates group creation, synchronizes messages and emails, provides risk alerts and weekly reports, ultimately improving execution speed, reducing manual effort, and supporting multi‑business‑line project management.
This guide compiles key product manager interview questions about demand sourcing, priority assessment, requirement validation, translating user needs into solutions, version planning, handling project delays, managing requirement changes, and cross‑department communication, offering concise answers and practical frameworks to help candidates succeed.
The article explains what technical debt is, how it creates a vicious cycle that slows development, outlines common causes such as rushed releases and copy‑paste coding, and offers practical strategies—including measurement tools, incremental migration and full rewrites—to manage and avoid it.
Since 2017 Youzan has built its own Efficiency Platform, evolving from a basic data‑unification tool into a comprehensive collaboration and workflow system that integrates demand management, agile practices, merchant SLA, prioritization, value‑loop analytics, and internal services, embodying efficiency, collaboration, and continuous improvement.
Designers often waste time repeatedly sharing design‑link URLs, but by creating a centralized project‑progress table in Shimo and using link insertion, data validation, and conditional formatting, teams can instantly access design resources, streamline communication, and dramatically improve workflow efficiency.
This article explains the concept of risk, outlines the five key elements of risk management, provides practical templates and examples for identifying and responding to common project risks, and shares a case study with actionable lessons for improving risk handling in agile development teams.
This article explains why measurement is essential for management, outlines a step‑by‑step process for collecting and analyzing efficiency metrics, and shows how to turn data‑driven insights into concrete conclusions and actionable improvement plans for software projects.
JD Central’s 2019 merchant‑center overhaul transformed a fragmented, hard‑to‑use backend into a unified, efficient platform through intensive cross‑team collaboration, rapid component‑based development, and focused user‑experience research, delivering two versions on schedule and earning strong merchant praise.
JD Retail’s technology and data platform adopted agile methods, launched training and coaching, created an Agile Project Management Guide, and achieved a 25% reduction in delivery cycles while 80% of projects now follow agile practices, showcasing measurable efficiency gains.
The author, a former technical director, recounts a three‑month period managing a 20‑person R&D team across four legacy projects, analyzes four critical management mistakes—including over‑estimating team skill, under‑estimating project difficulty, spreading resources too thin, and neglecting dedicated management—and shares concrete reflections and actionable lessons for future leaders.
This article recounts a twelve‑year‑old French government software project that ballooned to over six million lines of C++ code, suffered from obsolete technology, chaotic version control, and absurd management practices, ultimately ending in failure and the arrest of its leaders.
The 2019 China Project Management Development 20‑Year Achievement Forum highlighted Alibaba Infrastructure's award for Best Enterprise Practice, where its PMO shared a layered strategic project management framework that translates departmental strategy into executable projects, offering insights for organizations facing rapid market changes.
This article summarizes Google’s core software‑engineering practices—including a unified source repository, the Blaze build system, rigorous code‑review processes, extensive testing, error tracking, language policies, debugging tools, release engineering, project‑management methods, and personnel development—showing how they contribute to the company’s sustained technical success.
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.
Effective meetings, essential for solving complex organizational problems, are best managed by applying project‑management principles through three phases—pre‑meeting preparation with clear agendas and materials, disciplined during‑meeting control and consensus building, and diligent post‑meeting follow‑up on action items—tailored to four distinct meeting types.
A technical director recounts a month‑long, troubled e‑commerce project—detailing its background, the cascade of quality and management mistakes, the intensive code‑review rescue, and the hard‑earned lessons on design, delegation, and balancing speed with quality.
This article outlines the nine critical competencies—ranging from analytical thinking and effective communication to automation, DevOps, and project management—that empower software testers to deliver high‑quality applications and thrive in modern development environments.
This article explores the core purpose of system architecture, identifies technical, business, and project-management challenges, and presents a systematic approach—systemic thinking, decomposition, abstraction, and patterns—to effectively design and implement robust architectures.
This article explains how to use GitLab Open API for project creation, code initialization, and team code statistics through Node.js backend services, enabling unified project management and data-driven team productivity analysis.
This guide outlines project naming conventions and step‑by‑step instructions for creating a new Jenkins project, configuring build history, parameterized builds, triggers, Jenkinsfile, and how to build, view logs, and debug the pipeline, illustrated with screenshots.
During a three‑month Flutter internship at Xianyu, a Guangdong University of Technology software‑engineering student migrated from Android to Flutter, rebuilt the publishing page with Fish‑Redux, optimized a pull‑to‑refresh widget saving over 100 MB of memory, mastered the full FDD workflow, and distilled a comprehensive learning roadmap and teamwork advice for future developers.
Drawing on over two decades of experience, this article examines whether project managers should code, outlines the PMP framework, discusses the pitfalls of early promotion to management, and offers practical advice on timing the transition from engineering to leadership roles.
A former programmer shares a candid 13‑year journey from entry‑level coding to tech director, revealing how hard work, evolving leadership styles, reward‑punishment balance, and reflective management practices shaped his success and the pitfalls he learned to avoid.
The article argues that Scrum falls short of true agility, critiques its rigid framework, labels it as fragile when mis‑implemented, and shares personal insights on why simple priority queues often outperform Scrum in software development.
This guide outlines how engineers can succeed as technical project managers by setting clear goals, aligning people and processes, and mastering each phase of the project lifecycle—from initiation and requirement review to scheduling, design, testing, release, and retrospective analysis—while mitigating common risks.
Facing a thousand‑person, multi‑team, multi‑topic mobile platform, Baidu’s App engineering team built a layered, closed‑loop agile framework—covering organization, business architecture, scope, timeline, risk, and stakeholder management—to streamline delivery, reduce handover costs, and accelerate value.
This article explains how to evaluate the necessity of reverse‑scheduled projects, assess timeline feasibility across requirement, development, and testing phases, and presents three practical approaches—adding manpower, adjusting requirements, and improving efficiency—along with key precautions to ensure successful on‑time delivery.
This guide explains the complete project kickoff process—from value research and preparation to the kickoff meeting—highlighting how clear goals, defined scope, key milestones, stakeholder organization, and effective communication can dramatically increase a project's chance of success.
The article introduces Deadline‑Driven Development (DDD), humorously dubbed “hanging‑rope development,” explains its reverse‑schedule methodology, outlines three key implementation steps, highlights its benefits for task clarity and focus, and concludes with a light‑hearted invitation to discuss other quirky development‑driven approaches.
This article examines the debate over writing documentation in agile projects, explains how to create effective agile documentation using user stories, compares it with traditional project documentation, and offers concrete guidance and examples to help teams adopt a more efficient, value‑driven documentation approach.
This article explains why agile projects treat documentation differently from traditional projects, outlines the logical and structural differences, shows how to write user stories that pair Why and What, and provides practical guidance for creating concise, value‑driven agile documentation.
This guide explains the essential components of a project kickoff—including value research, preparation, milestone setting, stakeholder organization, and information sync—offering practical steps and best practices to ensure a solid project start and reduce early‑stage risks.
The article explains how thorough requirement analysis, disciplined daily planning, proactive risk communication, and a strong team project culture enable testers to actively contribute to project success, improve delivery quality, and align product outcomes with business value in fast‑changing mobile‑internet environments.
This guide explains Jenkins project management, covering naming conventions, creating new projects, configuring build history, parameterized builds, triggers, Jenkinsfile setup, as well as building, viewing logs, and debugging pipelines with illustrative screenshots.
This article explores the most famous software development laws—from Murphy's Law to Moore's Law—explaining their meanings, origins, and practical implications for coding, project management, and system design.
The article examines agile transformation as a systematic, multi‑dimensional improvement effort, using YouZan’s evolution to illustrate how project‑manager roles expand from informal coordination in tiny workshops through functional, business‑unit, matrix, and strategic‑business‑unit structures, emphasizing the need to look beyond R&D formalities and consider systemic, time‑delay effects.
This comprehensive guide outlines 40 essential project management terms—from basic concepts like project plans and WBS to advanced topics such as risk mitigation, Kanban flow limits, and quality assurance—helping professionals enhance their terminology and improve project communication.
This article discusses common problems in fast‑paced project iterations—such as volatile requirements, low‑quality demand, delayed testing, and cross‑team dependencies—and presents practical methods like user stories, demand checklists, early annotations, developer‑led requirement reviews, and testing best practices to improve delivery speed and quality.
The article examines why testers and developers often clash, illustrates the conflict with the classic Prisoner's Dilemma, lists common friction points such as unclear processes, standards, resources, and attitudes, and offers practical recommendations to establish shared workflows, improve communication, and foster a cooperative team environment.
This guide explains why daily stand‑up meetings are vital for project communication, outlines a step‑by‑step method for introducing them in weak‑matrix organizations, and provides practical tips on preparation, commitment, timing, three‑question format, and continuous feedback to improve team efficiency.
This article argues that proactive planning is more constructive than passive year‑end summaries, explains how setting clear goals, breaking them into tasks, estimating time, and using simple tools like spreadsheets and Gantt charts can improve personal and professional productivity, even amid rapid change.
The article clarifies common misconceptions about waterfall and agile, explaining that both approaches require thoughtful planning, adaptability, and value‑driven delivery rather than merely executing a fixed plan or abandoning planning altogether.
In the VUCA era, project managers operating in matrix environments must adopt clear responsibilities, emotional intelligence, and strategic questioning to turn awkward interactions with technical experts into productive collaboration, using influence, empathy, and professional insight across all project phases.
This article shares practical insights on project management, covering how to understand project goals, assess resources, communicate with stakeholders, handle risks and changes, create effective plans, and ensure successful delivery through disciplined documentation and verification.
This article presents a detailed case study of a mid‑size development team’s front‑end and back‑end technology stack, server environment, project workflow, and management practices, aiming to share practical solutions and lessons learned for building and maintaining enterprise‑grade Java applications.
The article recounts how a major bank's R&D center used a card‑playing exercise to demonstrate agile story‑point estimation, detailing the step‑by‑step process, its purpose, and answering common questions about the technique’s applicability, units, and relative‑estimation logic.
This guide outlines the key features to consider when selecting a task management tool, compares seven popular solutions for developers, and highlights each tool's strengths, pricing, and missing functionalities to help teams pick the most suitable option for improved productivity.
A project manager reflects on a four‑month development effort that collapsed after launch, analyzing mistakes in quality control, trust, ownership, requirement handling, and code review, and shares concrete steps taken to fix the issues and key lessons learned for future projects.
Over the past two years AMP has grown from a tiny project to a large open‑source effort with over 700 contributors, prompting a shift from a single‑maintainer governance model to a consensus‑based Technical Steering Committee and working groups to give all community members a voice.
A senior project manager reflects on a four‑month, 100‑person‑day software project that collapsed after launch, analyzing five critical mistakes—from neglecting quality and over‑trusting the team to lacking ownership, design, and code review—and shares the concrete steps taken to rescue the product and the key takeaways for future projects.
This article walks you through creating, customizing, and linking Jira workflows—including building a workflow, defining a workflow scheme, associating it with a project, and configuring statuses, transitions, and conditions—so you can tailor issue processing to your team's needs.
This comprehensive guide walks new Jira administrators through creating projects, configuring issue type schemes, screens, and fields, and linking schemes to projects, providing clear instructions and visual examples to help avoid common pitfalls and streamline project management.
The article uses bridge‑building anecdotes and real‑world software stories to argue that blindly following best practices can create unnecessary complexity, hinder problem‑solving, and waste resources, urging developers to balance standards with actual project needs and timing.
In this interview, senior JD.com project manager Tian Yanyun discusses his most memorable projects, coordination techniques without formal authority, demand decomposition, feasibility assessment, risk control, portfolio benefits, and how to thrive in a volatile, uncertain, complex, and ambiguous environment.
This article shares practical, experience‑based advice on introducing agile methods in software projects, emphasizing tailoring practices to specific contexts, problem‑driven adoption, and essential rules such as physical Kanban boards, daily stand‑ups, and clear Scrum roles, illustrated with multiple real‑world case studies.
The article outlines the essential professional knowledge, multifaceted responsibilities, and flexible approaches a competent e‑commerce project manager must possess, emphasizing the integration of PMBOK fundamentals, technical and business expertise, and agile practices across diverse development projects.
The article examines why developers feel compelled to refactor messy code, illustrates common pitfalls such as mixing refactoring with new feature development, and proposes practical strategies—including separating refactoring from feature work, adopting small‑step incremental changes, and integrating test‑driven development—to manage refactoring projects successfully.
The author recounts how discovering Agile and Extreme Programming in 2008 transformed his software development mindset, improved project delivery, and reshaped organizational and product design practices, illustrating both the benefits and challenges of adopting Agile in a traditionally waterfall‑focused environment.
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.
The article recounts a recent Java web project for a municipal client, detailing the lack of documentation, the decision to redevelop, the choice of front‑end and back‑end frameworks, the layered architecture design, agile team management, and practical lessons for rapid development of small‑to‑medium systems.
The article argues that testers should abandon a passive, isolated role and become proactive quality guardians who understand business, design logic, and user scenarios, using testing as a project‑management lubricant to drive continuous improvement and build a strong capability barrier.
This article explains why architects need both specialized and general management skills and summarizes the ten PMP knowledge areas—Integration, Scope, Schedule, Cost, Quality, Resource, Communication, Risk, Procurement, and Stakeholder—providing visual references for each.
The article recounts the Hujiang PMO salon held on May 27, 2018, detailing the schedule, keynote presentations on PMO operations, organizational project management, a complex cross‑departmental learning system case study, and concluding remarks on continuous improvement and transformation in project management.
The article shares practical QA techniques and project‑progress strategies for a mobile DSP advertising team, emphasizing paper‑based documentation, rapid test case execution, clear test design using XMind, and the potential of AI‑driven bug analysis, while also highlighting the importance of versatile testing roles.
This article recounts how a small, multi‑disciplinary channel development team applied a customized Kanban‑based agile process to overcome tight schedules, heavy workloads, and a critical three‑day emergency feature request, demonstrating both the strengths and limits of agile in fast‑changing environments.
