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.
This guide shares practical GitHub usage habits, from crafting consistent READMEs and issue/PR templates to leveraging labels, CI integration, release workflows, and post‑release support, helping open‑source maintainers improve project visibility, collaboration, and quality.
This article shares practical advice on ensuring software projects are maintainable, well‑designed, effectively implemented, and smoothly deployed with proper monitoring and statistics, helping teams avoid common pitfalls and achieve long‑term success.
The article examines why traditional waterfall planning remains essential for banking software projects while selectively adopting agile practices, highlighting the differences between consumer‑focused (To C) products and business‑focused (To B) initiatives, the limits of MVP, and a hybrid delivery model that satisfies both speed and contractual certainty.
The story follows Pilot Fish, a diligent developer tasked with building a customer‑service system despite receiving only vague, “just do something” feedback from department heads, leading to a demo that merely opens and closes a CD‑ROM, highlighting the pitfalls of unclear requirements and misguided iterative development.
This article outlines nine recurring problems—from mismatched teams and unrealistic requirements to relentless overtime and ignored personal lives—that drain developers' energy and sabotage software projects, offering insight into how these issues arise and why they persist.
The article explains that there is no universal silver‑bullet methodology for software projects; instead, teams must analyze each project's unique variables, blend existing frameworks, and continuously refine a simple, tailored process to achieve effective results.
The article shares practical reflections on project management in e‑commerce development, emphasizing the importance of clear requirements, effective communication, realistic scheduling, resource allocation, and proactive risk management to help practitioners improve their project outcomes.
This guide explores why open‑source matters, shares PingCAP’s practical experience running TiDB, TiKV, and PD, and provides step‑by‑step advice on choosing licenses, managing repositories, fostering community contributions, and effectively participating in open‑source projects.
This article recounts how Ctrip’s Service Butler project achieved a one‑month launch by establishing clear division of labor, intensive cross‑team communication, Scrum‑of‑Scrums, War‑Room sessions, and a strong team‑spirit culture, illustrating practical agile management for large‑scale development.
This article outlines the core professional skills, project experience, development processes, tools, interview questions, and negotiation tips that Java developers need to master to succeed in job interviews and advance from junior to senior positions.
The article chronicles JD.com’s middle‑platform R&D PMO from its 2012 founding through phases of following, driving, and leading, detailing team growth, agile scaling challenges, PMI China collaboration, performance models, award wins, and strategic goals for 2018.
This article shares a detailed, experience‑based framework for project managers to successfully lead cross‑company, multi‑team software collaborations by dividing work into planning, implementation, and delivery phases, emphasizing risk identification, schedule coordination, change handling, and continuous external communication.
The article compares the classic waterfall software development model with iterative development, outlines the drawbacks of the former, highlights the six advantages of iteration, and details a multi‑iteration parallel approach with QA and release‑cycle practices for improved project control and product quality.
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.
The article examines why software projects often suffer from the paradox of many team members, few deliverables, and heavy workloads, identifying issues such as misaligned roles, poor code quality, communication overhead, mistrust, unclear requirements, and outdated architecture that collectively drain efficiency.
The iQIYI Literature vertical uses a streamlined four‑stage agile workflow—review, scheduling, development, release—combined with dynamic process tweaks, tight baseline coupling, branch‑isolated CI/CD, and layered quarterly, monthly, and weekly planning, enabling rapid product iterations and sustained growth into a recognized brand.
A senior Alibaba engineer reflects on three years of building a large‑scale data platform, tackling distributed rate‑limiting challenges, leading cross‑regional projects, and pursuing AI research, while sharing personal insights on career growth, technical problem‑solving, and the value of continuous learning.
This guide explains Scrum fundamentals, team roles, the five development steps from brainstorming to evaluation, and shows how to configure and run a Scrum project in JIRA with detailed board setup, sprint planning, and reporting features.
This article breaks down the realistic role of product managers, highlighting core competencies such as communication, independent thinking, and project management, and offers practical guidance on handling diverse requirements and ensuring product plans smoothly transition into development.
This article presents a structured recommendation of Java books covering introductory syntax, intermediate refactoring and TDD, advanced architecture, software development processes, and project management, helping Java developers progressively deepen their knowledge and improve coding practices.
This article explains why designers need product thinking and breaks down the five key mindsets—user‑centered, logical, data‑driven, marketing, and project thinking—providing practical examples and actionable steps to boost influence, career growth, and design impact.
The article shares JD.com Mall R&D Management expert Qian Zhilin’s three‑year experience, detailing four stages of project management—from early follow‑up and coordination to guidance, planning, and the evolution toward project‑set management—offering practical lessons for R&D and product teams.
The article explains why many hiring posts that claim they only need one programmer are misguided, highlighting disrespect, underestimation of effort, misunderstanding of project scope, and premature recruitment, and offers practical advice for both employers and developers.
This interview chronicles Xiao Li’s unconventional path from a petroleum chemistry graduate to a senior operations director, highlighting his hands‑on experience with system administration, virtualization, cloud computing, and team management across major Chinese tech firms.
The article explains how a software lifecycle tool integration platform serves as a data bus to unify disparate development, testing, project management, and outsourcing tools, enabling accurate enterprise reporting, seamless agile and requirement synchronization, and end‑to‑end traceability across the software development process.
This article shares a veteran front‑end engineer’s step‑by‑step methodology—covering the 3W framework, requirement clarification, timeline estimation, risk exposure, and post‑release monitoring—to help developers consistently deliver high‑quality features.
This article details how a design team tackled a one‑month launch deadline for the “Hi Travel Medal Cloud Diamond” product, outlining project initiation, rapid parallel design, goal decomposition, interaction and visual design, usability testing, data‑driven adjustments, and post‑launch insights.
This article explains the purpose and interpretation of cumulative flow diagrams in lean software development, illustrates how WIP and lead time affect delivery, and discusses common pitfalls such as code coupling, optimistic estimates, and non‑project activities that hinder iteration progress.
This article introduces seven high-quality open‑source bug tracking tools—Bugzilla, Redmine, Trac, Mantis, Fossil, Phabricator, and WebIssues—detailing their origins, main features, and why they can boost project development and issue management for software teams.
The article explains why rapid response is essential in modern software projects, critiques the drawbacks of waterfall development, and introduces agile practices such as short iterations, user stories, continuous integration, automated testing, and close collaboration to deliver value more efficiently.
This guide outlines practical strategies for tech team leadership, covering people, project, technology, and culture management, recruitment, mentorship, code review, pair programming, documentation standards, automation, and workflow optimization to boost productivity and morale.
In this interview, Linus Torvalds shares hard‑earned lessons on software project management, emphasizing personal responsibility, the primacy of users over code quality, the limited role of tools, and how the Linux kernel mailing list keeps contributors aligned, offering timeless advice for developers and teams.
This case study describes how Qunar's R&D support team built an integrated project management platform that unified workflow, data, and toolchains across development, testing, and release stages, dramatically lowering communication overhead, eliminating information inconsistencies, and improving overall engineering productivity.
This article explains how a product‑focused, fast‑response team can efficiently select and use software for environment setup, project management, and technical knowledge accumulation, ensuring minimal distraction and streamlined development.
The article shares practical insights from a JD Cloud redesign project, highlighting how proactive information gathering, early cross‑team communication, and a unified iconfont workflow can reduce hidden variables, improve efficiency, and prevent costly rework in fast‑paced frontend development.
This comprehensive guide outlines the core Java programming competencies, web development frameworks, project experience, management tools, system architecture components, interview questions, and personal evaluation tips that aspiring Java engineers should master before a job interview.
This article shares six practical stories—from a broken Mac repair dilemma to project reporting, vendor selection, and daily work habits—illustrating how leaders prioritize speed and efficiency, the importance of clear communication, and the standards for doing work well while fostering teamwork and personal growth.
This article explains the core concepts of Agile development, compares it with traditional waterfall methods, outlines its benefits such as faster response and higher quality, and introduces practical frameworks like Scrum and XP along with key practices like TDD and continuous integration.
After nearly a decade of work in embedded, web, mobile, consulting, and integration projects, the author outlines four major knowledge areas—engineering methods, system integration, project management, and development—detailing essential practices, design principles, and technology stacks such as C, Android, cloud services, and big data.
This article explains how to create and customize Kanban boards in TFS, covering board creation, column naming, WIP limits, status mapping, swimlane usage, card field configuration, and visual styling to improve team visibility and workflow management.
This article outlines the essential mindset, problem‑solving approach, solid PHP fundamentals, and comprehensive internet application and project‑management knowledge required for developers aspiring to senior PHP engineer roles.
A corporate dragon‑boat race on the Duanwu Festival turned into a vivid lesson on project management, highlighting how unclear roles, poor communication, lack of team harmony, and member inactivity can derail a project and offering practical tips to strengthen leadership and teamwork.
The article explains how software architects combine technical architecture responsibilities with people‑focused management duties, emphasizing the importance of nurturing talent, sharing a clear product vision, encouraging collaboration, and balancing technical excellence with team motivation to achieve successful, high‑impact projects.
This guide outlines eight practical steps—from simplifying your vision to a minimal viable version, crafting clear requirements, mapping user interactions, breaking down milestones, recruiting freelancers, and building lasting collaborations—to help you hire a programmer and successfully launch your product idea.
This article examines some of the most expensive IT project failures worldwide—from the 2012 RBS software upgrade outage to the UK’s £12 billion CFH medical records system—highlighting how budget overruns, unrealistic expectations, and poor coordination repeatedly burn billions without delivering results.
This guide outlines sixteen practical project‑management insights—from defining clear goals and stakeholder roles to handling cost‑cutting pressures and risk mitigation—helping teams streamline planning, improve execution, and prevent unnecessary overtime.
From a tiny squad using SVN to a full‑stack agile team, we detail how migrating to GitHub, adopting ZenHub for project management, integrating TravisCI for continuous testing and deployment, using Reviewable for pull‑request reviews, Coveralls for coverage metrics, and Slack for real‑time communication transformed our development workflow and boosted code quality.
This article shares practical advice from a former development director on how technical managers can excel by connecting with their teams, managing tasks effectively, mastering time and resources, respecting individuals, and representing their team’s interests to drive success.
This article presents 22 fundamental Scrum questions covering roles, artifacts, events, benefits, limitations, and practical guidance, offering a comprehensive overview for anyone preparing to become an effective Scrum Master and deepen their understanding of agile project management.
The article reflects on an engineer's experience updating a signature system, highlighting the pitfalls of quick patches, the importance of requirement analysis, resource testing, realistic time estimation, and proactive communication, and advocates for a refactor to improve maintainability and role perception.
This article recounts a recent cross‑border shopping user research project, detailing preparation, requirement gathering, timeline planning, execution, data analysis, report writing, and final sharing, while highlighting practical insights and best practices for effective research and project management.
This case study outlines JD Smart Cloud’s unified app project, covering its background, early interaction and visual mockups, design adjustments driven by stakeholder feedback, the final UI layout, and key takeaways on communication, prioritization, and iterative design in tight‑deadline product development.
Exploring how various project management tools—from Rally and JIRA to Trello, physical whiteboards, and Confluence—can be selected and applied based on team size, structure, and geographic distribution, this guide helps teams boost efficiency while avoiding tool misuse.
This article offers actionable guidance for project managers on understanding technical roles, providing clear information, fostering open communication, handling requirement changes wisely, and motivating teams to create a collaborative environment that accelerates project delivery.
