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 case study details how a distributor business unit R&D team applied the APD agile methodology to transform weekly iterations into daily releases, reduce demand cycle time, double throughput, halve bugs, and adopt lean‑Kanban and Scrum‑inspired practices for sustained improvement.
The 7FRESH mobile app team at JD transformed its organization into product‑oriented cross‑functional squads, refined task splitting and estimation, expanded automated testing, enforced strict test‑in criteria, and allocated time for technical debt reduction, resulting in markedly higher delivery quantity, frequency, and quality while improving stakeholder satisfaction.
The article explores how unpredictable black‑swan events, the butterfly effect, Murphy's law, rapid business growth, technical debt, tool choices, complex domains, documentation, and leadership all combine to threaten software stability, and proposes agile, systematic, and quality‑centric approaches to mitigate these risks.
The article introduces Autohome's Product Development (APD) methodology, detailing its framework, core principles, three development models—flow, iteration, and train—and how it integrates lean‑agile practices to double team capacity and halve delivery cycles.
This article explains how software teams can select, combine, and interpret nine essential metrics—including lead time, cycle time, team velocity, defect rates, MTBF, MTTR, and security incident counts—to drive continuous improvement, align with business goals, and ultimately achieve successful outcomes.
To keep product development sustainable, prioritize user‑reported bugs first, then self‑discovered bugs, followed by user‑requested features and finally internal ideas, using continuous ranking based on impact, difficulty, and supporter count while actively listening to users and fixing problems before adding new functionality.
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.
This article recounts how an agile coach helped Alibaba Health's B2B development team overcome chronic release failures, burnout, and low productivity by establishing stable feature teams, aligning goals, tightening quality gates, clarifying requirements, visualizing flow with Kanban, implementing continuous integration, and driving continuous improvement through clear metrics.
This article explains the purpose, prerequisites, organization, preparation, focus points, execution, and follow‑up of daily stand‑up meetings, emphasizing value‑flow, Kanban visualization, and practical checklists to help teams collaborate effectively and deliver value smoothly.
This article recounts a real‑world agile transformation where a vendor‑centric, zero‑to‑one business system was delivered by iteratively applying agile, lean, and DevOps practices such as JIRA tracking, WIP limits, weekly planning, daily stand‑ups, and shortened feedback loops, highlighting the coach’s role in the trenches.
The article discusses the challenges of allocating delivery team resources based on project budgets, the need for a monthly stakeholder "parliament" to prioritize demands, and the difficulty of creating a manageable, value‑driven backlog that balances large projects, regulatory work, and small initiatives.
The article presents seven tactical principles for agile coaching, explains their system‑dynamic foundations, and offers practical guidance on building leadership groups, clarifying roles, aligning management, measuring improvement, strengthening execution, optimizing communication, and fostering deliberate practice to drive sustainable agile transformation.
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.
This article explains the Agile Fluency Model, describing its four progressive layers—Focusing, Delivering, Optimizing, and Strengthening—detailing the benefits, required investments, typical timeframes, and practical guidance for organizations to assess, improve, and sustain agile team performance.
The article explains how mixing old and new work methods creates distinct team dynamics, identifies four participant types, outlines two major transformation challenges, and shows how a sand‑box simulation can safely guide teams toward a stable, flow‑based agile/DevOps paradigm.
This article recounts the one‑year agile pilot of the Agricultural Bank’s Spring mobile‑marketing platform, detailing its origins, challenges, cultural and efficiency gains, a live DevOps+LIVE Q&A session, and practical insights from ScrumMasters on managing uncertainty in large‑scale banking software projects.
This article explains how Fangduoduo’s R&D team creates an empowering platform by gathering creative talent, fostering a self‑driven culture, integrating product thinking into engineering, and applying DevOps, OKR, and Scrum practices learned from leading Silicon Valley companies.
This article explains why retrospective meetings are crucial for team growth, outlines five maturity levels of retrospectives, and provides a detailed, five‑stage process—including preparation, data collection, insight generation, action planning, and closure—to help teams continuously improve their workflow.
This article explains how senior engineers must go beyond continuous delivery to ensure that what they ship delivers real value, describing the relationship between continuous delivery and business innovation, the growth‑flywheel model, the gate‑keeping framework, impact mapping, and the Biz‑Dev‑Ops practice for data‑driven, iterative product development.
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 article explains Alibaba’s “2‑1‑1” vision for accelerating continuous delivery—delivering 85% of requests within two weeks, developing them within one week, and releasing within an hour—by visualizing end‑to‑end value streams, limiting parallel work, and applying lean, agile practices to improve flow efficiency.
This article explains agile development’s core business goals of faster value delivery and effective learning, defines agile as early value delivery and adaptive response, and presents a comprehensive five‑group metric system—including release capability, demand response cycle, throughput, built‑in quality, and external delivery quality—to assess and improve continuous delivery performance.
The article compares internet‑focused teams with traditional ones, highlighting differences in work mindset, leadership focus, user‑centric goals, rapid feedback loops, and the qualities needed for managers to thrive in fast‑changing, user‑driven environments.
The article explains how Spotify’s agile practices succeed because they align with Swedish cultural values and organizational principles, warns against naïvely copying the model, and offers guidance on adapting agile transformations to different cultural contexts using Hofstede’s dimensions.
This article outlines the key characteristics of large‑scale websites and presents a comprehensive set of architectural goals, patterns, and techniques—including performance tuning, high availability, scalability, extensibility, security, and agile operations—to guide the design of robust, user‑centric online platforms.
The article analyzes common product development practices that lead to failure, outlines ten root causes such as idea sourcing, flawed business plans, misaligned roles, late agile adoption, and project‑centric management, and concludes with a call for companies to adopt outcome‑focused, continuous discovery approaches, while also featuring a DevOps recruitment notice.
The article outlines eight key principles that enterprises should follow to harness big data responsibly, covering goal definition, strategic partnership, source identification, continuous communication, agile iteration, technology evaluation, cloud alignment, and talent development with security considerations.
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.
This talk explains how visualizing end‑to‑end value flow, focusing on demand bottlenecks, defining proper metrics, and aligning features with key business goals can dramatically speed up product innovation cycles and deliver higher‑value software.
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.
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.
This article explores the concept of engineer culture versus KPI‑driven culture, outlines essential prerequisites such as trust and technical leadership, and shares concrete practices—including small‑team dynamics, automated testing, continuous integration, pair programming, and effective meetings—to help teams cultivate a sustainable, high‑impact engineering environment.
This article shares ZhaiZhai's data‑driven approach to process improvement, detailing how development self‑testing and code‑review practices were introduced, measured, and refined using PDCA cycles to boost quality, efficiency, and team morale across multiple teams.
This report details a joint initiative by the Application Development Department and the PMO to improve software delivery efficiency through a full‑process continuous delivery methodology, a Git‑based configuration‑management model, and end‑to‑end pipelines applied to the multi‑scenario C3 project group, including results, advantages, training, and future plans.
This article compiles a series of Chinese-language resources on user story mapping, explaining how the technique helps agile teams create clearer backlog, prioritize features, and plan releases, offering both theoretical background and practical steps for effective implementation.
The DevOps International Summit 2024 in Beijing, the sole China‑based global DevOps conference, brings together over 80 leading experts to showcase end‑to‑end practices—from Lean‑Agile, Continuous Delivery, SRE, and microservices to DevSecOps, AI‑driven tooling, and the new Research and Operations Integration Capability Maturity Model—through industry‑focused tracks, hands‑on training, and real‑world case studies across finance, telecom, retail and more.
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 article describes how the Agricultural Bank's software development center introduced daily builds, automated testing, Kanban boards, and Scrum stand‑ups across three phases to boost development efficiency, product quality, and team collaboration, sharing lessons learned and outcomes from the pilot projects.
This article explores the concept of software architecture for mobile apps, sharing personal reflections, industry case studies, design principles, modularization strategies, development practices, testing, risk management, and agile processes to help developers build maintainable, scalable, and high‑quality applications.
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 author shares personal insights from a recent discussion with Microsoft Seattle on DevOps transformation, highlighting the lack of a standard definition, various performance metrics, the role of story points, and considerations for UI automation testing within agile teams.
This article explains how agile development—especially Scrum—and agile testing practices like continuous testing, TDD, automation, and continuous integration enable rapid iteration, higher product quality, and faster delivery in fast‑changing market environments.
The article reviews the rise of Agile since the 2001 Manifesto, examines enterprise adoption challenges, outlines major frameworks like SAFe, LeSS, DAD, and Nexus, highlights the role of Agile coaches, and predicts broader integration with DevOps and other business functions in the coming decade.
This article analyzes Nationwide Insurance's multi‑year DevOps transformation, detailing its organizational scale, strategic goals, experiment timeline, team interaction model, developer‑experience improvements, lead‑time metric, support structure, and a rapid response case that together illustrate how a large financial services firm accelerated delivery while reducing risk.
The 2017 PractiTest software testing industry survey reveals worldwide respondent demographics, preferred testing skills, increasing multitasking and automation, widespread agile and CI/CD adoption, future technology priorities, and hiring expectations, offering a comprehensive snapshot of current practices and emerging trends for testers.
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.
This article offers product managers practical negotiation techniques—including securing a home base, identifying true stakeholders, using vision as a tool, maintaining consistency, proving rationale, committing to agile practices, asking open‑ended questions, focusing, listening, and standing firm on decisions—to effectively influence and align stakeholder expectations.
This article compiles seasoned developers' advice on choosing a language, embracing agile delivery, rigorous testing, avoiding premature optimization, and writing maintainable code to help programmers grow their careers and produce high‑quality software.
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.
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.
The article uses the hammer metaphor to critique treating agile methods as a one‑size‑fits‑all tool, illustrating common misunderstandings through dialogues about user stories, estimation, TDD, pair programming, Kanban, Scrum, SAFe, and continuous delivery, and urging thoughtful adoption.
The article shares a year‑long experience of applying agile and lean principles—especially splitting and decoupling—to improve delivery efficiency, team structure, and value flow across large waterfall projects, small process‑optimisation tasks, and product‑centric squads, highlighting concrete practices, outcomes, and future plans.
The article explains how traditional user research methods struggle to keep pace with fast‑moving internet product cycles and proposes an agile, business‑oriented research framework that shortens study time, improves cross‑functional communication, and ensures research outcomes are actionable and aligned with product goals.
This article explores how operations teams can adopt agile principles—especially Kanban—to address common challenges such as delayed feedback, task overload, and hidden risks, demonstrating a step‑by‑step transformation within the DevOps lifecycle.
To distinguish yourself among Java developers, focus on mastering core OOP principles, essential APIs, continuous coding, community engagement, blog interaction, studying open‑source frameworks, tracking tech trends, maintaining reusable code snippets, understanding various development methodologies, and documenting your insights for sharing.
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.
This article explores the evolution of continuous delivery, explains its core principles, and presents two detailed case studies from Baidu and Tencent that illustrate how organizational, architectural, and automation improvements can dramatically accelerate software release cycles while maintaining quality.
This article recounts how the Taobao Live team applied agile practices over three months, tracking capacity, lead time, quality, and predictability, and demonstrates measurable improvements in delivery speed, defect reduction, and business metric alignment through focused goals, rapid hypothesis testing, and continuous delivery.
The article illustrates five typical ways requirements are expressed in software projects—from leader‑driven oral requests and vague “half‑cooked” specifications to detailed document‑heavy, prototype‑driven, and client‑participation models—highlighting the challenges and impacts each pattern has on development and delivery.
This article details Ctrip's four‑year journey of using the OK system and OKR framework to create agile OK teams, drive high‑efficiency operations, implement entrepreneurial incentive mechanisms, and cultivate talent through the Huangpu training camp, ultimately reshaping corporate culture and sustaining rapid growth.
This article shares several agile process‑improvement case studies—from enhancing team responsiveness and communication to building strong engineering culture—offering practical guidance on establishing visibility, efficient decision‑making, minimizing re‑planning costs, and fostering high‑quality, cross‑functional delivery teams within software development.
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.
To achieve sustainable, low‑cost, high‑quality continuous delivery, teams—especially those under 30 members or working on loosely coupled services—should master core practices such as two‑week iteration cycles, CI pipelines, estimation, planning, and iterative activity management, as illustrated by the Baidu case series.
The article discusses how a software team selects an appropriate iteration cycle, establishes clear work agreements for each sprint, adopts single‑piece development with immediate testing, and introduces continuous integration to improve quality and efficiency in an agile environment.
This article details how a Youku team, together with Alibaba's PMO, redesigned their demand analysis workflow in 2016‑2017 by introducing data‑driven standards, product planning, decentralized reviews, and unified tooling, resulting in clearer timelines, higher efficiency, and measurable quality improvements.
Through agile coaching, this case study details how the demand analysis workflow for Youku’s mobile app was redesigned, standardized in Alibaba’s RDC platform, and evaluated, resulting in clearer product planning, decentralized reviews, data‑driven management, and measurable improvements in efficiency, quality, and cross‑team collaboration.
This article presents a curated list of essential Java books ranging from beginner fundamentals and agile testing to advanced architecture, software development processes, and project management, offering download links and concise commentary to help Java developers systematically improve their skills.
This case study examines Baidu's large‑scale Z service architecture refactoring project, detailing its organizational background, stakeholder pain points, current waterfall delivery issues, a CMMI‑based maturity assessment, and a two‑phase improvement plan aimed at adopting continuous integration and agile practices to achieve more predictable and faster software delivery.
The article argues that software development is a continuous design activity rather than a repeatable manufacturing process, using car production and cooking analogies to illustrate why traditional waterfall management fails and why developers should be seen as designers, not assembly line workers.
This article explains the core concepts of Agile software development, Continuous Integration, DevOps, and Continuous Delivery, compares their definitions from Wikipedia, offers personal interpretations, discusses their relationships, and provides practical advice for teams to solve real-world problems effectively.
This article examines how Agile, DevOps, microservices, and Docker have risen together in recent years, analyzing Google Trends data to illustrate their intertwined growth and explaining why Docker is seen as essential for rapid software delivery within modern DevOps and microservice ecosystems.
The author recounts a three‑year career path from a fresh Android developer in Shanghai to a CTO, sharing interview struggles, project experiences, hiring strategies, agile management insights, and personal growth reflections that can guide aspiring software engineers and tech leaders.
Agile teams can maintain rapid iteration cycles by applying the ‘555’ rule—five focused tasks, five representative participants, and five hours of testing—to deliver concise, high‑impact usability feedback without slowing development and ensure design decisions are data‑driven.
This article traces the evolution of software engineering tools leading to DevOps, highlights common transformation pitfalls, outlines core DevOps practices such as autonomous small teams, traceable toolchains, real‑time metrics, and describes the surrounding ecosystem, offering practical guidance for organizations adopting DevOps.
This article explains the core concepts of Agile development, its main methodologies such as Scrum and XP, the essential Scrum workflow terms, and how Agile integrates with DevOps practices like continuous integration and Docker containers.
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 article explains the origins of DevOps, presents the CALMS and Three Ways frameworks, and organizes practical DevOps principles into four dimensions—people, product, process, and tools—illustrating how they collectively enable continuous, on‑demand delivery of business value.
This article explains how to run a Kanban stand‑up meeting—its objectives of inspecting value‑flow, the daily right‑to‑left board walk, the six key issue categories plus an extra "6+1" check, and practical tips for keeping the meeting short, focused, and effective.
The article recounts how a team of mostly iOS developers built the LightOxygen Android v1.0 app using React Native, detailing their version planning, feature set, React Native’s strengths and shortcomings, and future roadmap while sharing practical development insights.
This article traces the history of DevOps from Patrick Debois' early frustrations in 2007 through the Velocity conferences, the birth of DevOpsDays, and the rise of continuous delivery, showing how agile principles reshaped IT operations into a collaborative movement.
This article examines how a startup’s Kanban board was redesigned to visualize end‑to‑end value flow, improve cross‑team collaboration, expose bottlenecks, and enable product managers to track and accept work more effectively.
This article explains the origins of the Kanban method, clarifies common misconceptions, and outlines its five core practices—visualizing value flow, making policies explicit, limiting work‑in‑progress, managing workflow, and establishing feedback for continuous improvement—highlighting how these practices enhance lean product development.
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.
The article explains why flat user‑story backlogs are ineffective, illustrates the problems with prioritizing and planning using such lists, and shows how constructing a user‑story map provides context, improves backlog management, and enables better release planning for product development.
This article explains DevOps as a cultural and technical shift that unites development and operations, outlines its relationship with agile, describes the required team and mindset changes, and provides a comprehensive glossary of key practices, tools, and cloud concepts.
Learn how to ensure high‑quality Java code throughout agile development by standardizing coding conventions, applying static analysis, writing unit tests, implementing continuous integration, and conducting thorough code reviews and refactoring, with practical tool recommendations and best‑practice guidelines for each step.
This guide explains how to structure product development cycles using Scrum, detailing iteration lengths, backlog prioritization, planning game preparation, roadmap definition, requirement tracking, and effective collaboration between development and testing teams to deliver publishable versions consistently.
At SpringOne, Credera engineers Jason Goth, Micah Blalock, and Patricia Anderson explained how they leveraged Conway’s Law to redesign a client’s technical architecture and processes, overcoming productivity decline by restructuring teams, applying the open/closed principle, and introducing new communication roles, ultimately accelerating high‑quality code delivery.
This article shares a first‑hand account of how Vipshop’s infrastructure group introduced Scrum, detailing the motivations, role adjustments, optimal team composition, practical challenges, and take‑aways for other technical teams considering agile adoption.
This article outlines the challenges of modern software delivery in a VUCA environment and presents a practical, step‑by‑step approach to designing a visual continuous‑delivery pipeline that balances speed, quality, and reliability through agile, lean, and DevOps practices.
This article examines how increasing software productivity drives the evolution of development models—from traditional waterfall through agile to microservices—and how full‑feature teams adapt production relations to maximize efficiency and creativity.
The article explains how to use the User Story Mapping technique on the TFS platform, describing both a direct one‑to‑one mapping approach and a conversion method that transforms business‑level story maps into technical TFS work items for efficient DevOps team collaboration.
Alibaba architects attended the SpringOne conference in Las Vegas, sharing insights on emerging technologies such as ReactiveX, Ratpack, Java 9 modules, Spring 5 and 1.4, Zipkin, XRebel, PaaS platforms, serverless computing, cloud‑native principles, Agile, DevOps, and microservices, highlighting both global trends and challenges for Chinese cloud providers.
This article clarifies common misunderstandings about agile development, explains why it can be faster than traditional methods by reducing pre‑development waste, early releases, and continuous testing, and offers practical illustrations through games, diagrams, and user‑story techniques.
The article examines how concise, efficient, and simple development practices—ranging from agile iteration and tool selection to testing automation and team management—can boost developer productivity, reduce waste, and enhance software quality across the entire software development lifecycle.
This article explains how to configure and use a TFS Kanban board to plan, execute, and review a Scrum sprint, covering team roles, sprint cadence, backlog grooming, sprint planning, daily stand‑ups, and sprint review and retrospective activities.
