This article explains how architecture remains a vital part of agile software development, covering agile‑first approaches, lifecycle‑wide modeling, ownership roles, scaling strategies, demand‑driven design, multi‑view modeling, and practical tips for communicating and evolving architecture without over‑building.
The article explains how agile development reshapes testing responsibilities—emphasizing customer mindset, continuous testing, strategy formulation, and exploratory testing—while also announcing the IDCF DevOps Hackathon, an end‑to‑end DevOps experience event in Hangzhou as this event.
This article provides a comprehensive overview of Agile methodology, detailing how testing adapts to Agile practices, comparing Scrum and Kanban, and exploring testing techniques such as BDD, ATDD, exploratory testing, and session‑based testing, while offering guidance for aligning testing with Agile delivery.
The article examines why many agile transformations fall short due to non‑agile business practices, explains the overlapping responsibilities of PO and BA, highlights two common pitfalls for new product owners, and outlines a comprehensive, market‑driven approach to product planning and lifecycle management.
This article outlines the most common software testing metrics, explains how they differ from broader software quality measures, and shows how teams at project, department, and executive levels can select and track the right indicators in both waterfall and agile environments.
The article details CICC Wealth’s E‑Space investment advisory platform’s journey to passing the China Information Communication Research Institute’s DevOps continuous delivery Level‑3 assessment, highlighting the role of standardized DevOps practices, agile transformation, tool integration, performance improvements, and the broader impact on the financial sector’s digital modernization.
This article explains the purpose and various formats of agile retrospectives, provides step‑by‑step guidance for face‑to‑face and online sessions, introduces useful tools, and offers practical tips to ensure retrospectives lead to continuous improvement and actionable outcomes.
The article explains how Test‑Driven Development is fundamentally a mindset that emphasizes predefined standards and expectations, explores related practices such as contract testing, acceptance criteria, and standard‑driven development, and discusses the challenges of defining, maintaining, and motivating adherence to these standards within agile teams.
During agile transformation, both newly appointed agile coaches and team leaders often feel uncertain, so this article outlines the three phases—introduction, adaptation, and innovation—and recommends specific leadership styles and techniques for each role at each stage to effectively guide teams toward true agility.
This article presents seven practical recommendations for conducting effective remote daily stand‑up meetings, covering optimal timing, personal conversation, video usage, data visualization, creative communication tools, online meeting enhancements, and informal team bonding to maintain agility in a remote‑first work environment.
The article narrates a software team's shift from a traditional waterfall model to an iterative, value‑driven agile approach, detailing the coach’s demand‑analysis meetings, three‑week sprints, lightweight documentation, continuous feedback, and the eventual successful delivery while highlighting common agile practices.
This article outlines Ctrip's hotel R&D team's systematic approach to boosting development efficiency through OKR alignment, MVP-driven value delivery, agile practice upgrades, and DevOps automation, detailing challenges, solutions, measurement metrics, and continuous improvement strategies.
The article outlines Microsoft’s experience and practical guidance for implementing large‑scale Agile and Scrum across a 4,000‑person development organization, emphasizing coordination, autonomy, continuous integration, DevOps, and leadership support to achieve sustainable, customer‑focused delivery.
The article argues that many organizations are exhausted by the over‑hyped Agile movement, labeling it an "Agile industrial complex," and calls for a return to the Agile Manifesto’s core values and principles, enriched by insights from social sciences and interdisciplinary thinking.
This article details Vivo's internet platform product R&D team's experience introducing OKR, outlining cultural prerequisites, positive and negative impacts, practical steps, pilot execution, common challenges, and guidance for other organizations seeking to adopt the framework.
This article explains how ScrumXP, a lightweight process created by SAFe that blends Scrum and Extreme Programming, differs from the Scrum defined in the official Scrum Guide in terms of purpose, team structure, roles, events, values, and empirical foundations.
The article examines the gap between the ideal of agile demand management—clear value‑driven goals, fast iterative releases, and unified backlogs—and the reality many teams face, then offers concrete principles, role guidelines, and decision‑making models to help product managers overcome common obstacles and achieve true demand agility.
This article presents a curated collection of 54 reference books covering DevOps, Agile, continuous delivery, lean, microservices, and related management topics, explaining a two‑step reading approach—first extracting key concepts, then deepening understanding—to help readers build a comprehensive knowledge framework.
The article details Liaoning Mobile's award-winning DevOps transformation, describing the team's background, agile implementation, toolchain construction, challenges faced, system highlights, and measurable results that earned them the prestigious Communication Industry DevOps Team Award at the 2022 GOITI ceremony.
This article presents a comprehensive framework for enhancing engineering efficiency and governance in agile delivery, outlining purpose‑driven goals, a golden‑triangle of best practices, metrics, and capabilities, and practical steps for implementation and continuous improvement.
The article explains why Scrum may not be appropriate in many situations, outlines the essential conditions for its successful use, and provides concrete examples of environments where Scrum works well and where it tends to fail, helping teams assess its applicability.
This article reviews popular project management tools—including Airtable, Asana, Basecamp, Jira, OpenReplay, Monday.com, Trello, and Wrike—detailing their key features, advantages, and drawbacks to help development teams choose the most suitable solution for efficient software project tracking.
Liaoning Mobile’s Channel Management System project passed the CAICT DevOps Capability Maturity Model Level‑3 continuous delivery assessment, showcasing how standardized DevOps practices, toolchains, and agile transformation boosted delivery speed, team capability, and operational efficiency, positioning the carrier at the forefront of China’s digital transformation.
This article explains five key dimensions—individual empowerment, team empowerment, clear goals, growth support, and culture shaping—that leaders should balance to foster effective self‑organization in agile teams, and also announces the upcoming IDCF DevOps Hackathon.
This article explains the ten advantages of using fixed‑length agile iterations—such as better forecasting, risk control, reduced waste, and improved alignment—while highlighting common pitfalls like extending iterations, treating them as mere timelines, and unstable team composition, emphasizing the prerequisites needed to reap these benefits.
In the era of large‑scale software, organizations must appoint value‑stream architects to visualize, influence, design, and train around integrated delivery pipelines, ensuring continuous business value, faster feedback loops, and alignment between product and engineering across the entire software value stream.
The article explains why a progressive, incremental approach to business architecture—balancing clear primary requirements with flexible handling of secondary and emergent features—helps large‑scale website projects avoid the pitfalls of rigid waterfall planning and enables smoother versioned development.
Liaoning Mobile’s DevOps R&D system was selected as a flagship case at the recent Service Trade Fair, showcasing how the company accelerated its digital transformation through agile delivery, cloud‑native architecture, intelligent operations, and comprehensive talent development to boost development efficiency and business agility.
In this interview, Sunrise Integration’s senior project manager John Rabal shares how his team leverages Jira Software automation—such as daily incomplete‑issue reminders, end‑of‑day status reports, and comment syncing—to streamline workflows, enhance collaboration across teams and clients, and provide practical advice for new Jira administrators.
The article explains how strong, open‑ended questions can help Scrum teams identify and fix common retrospective anti‑patterns—such as management attendance, lack of follow‑up, off‑topic discussions, trying to solve everything at once, and unclear action items—by fostering deeper reflection and collaborative problem‑solving.
The article outlines six strategic actions that visionary CIOs employ—abandoning legacy systems, creating innovation‑focused processes, reimagining work, leveraging their strategic position, cultivating talent and culture, and building credibility—to drive digital transformation and business growth.
This article details how the used‑car technology team at Autohome optimized R&D efficiency through standardized workflows, task decomposition, unified time‑based measurement, rigorous demand review, flexible branching, CI/CD pipelines, and data‑driven metrics, resulting in higher throughput and reduced bug rates.
This article explains the concept of reframing, illustrates it with classic stories and practical examples, and then uses reframing questions to challenge common Scrum myths, helping teams rethink agile roles, meetings, and backlog management for better product outcomes.
This article compares the traditional Waterfall development model with the Agile Scrum approach, outlining each method's strengths and weaknesses, describing Scrum roles and workflow, and offering practical insights on when and how to apply either model in software projects.
The article examines Mike Cohn's 2019 perspective that the Product Owner role in Scrum can be shared among team members, discussing the unique nature of Scrum expert roles, the feasibility conditions, and the potential future where product ownership becomes a collective team responsibility.
This article compares the traditional Waterfall model with Agile and Scrum practices, outlining each approach's strengths, weaknesses, roles, and workflow steps, and offers practical guidance on when to apply one method over the other in software projects.
This article compares the traditional Waterfall development model with Agile methodologies, outlines Scrum roles and workflow, highlights each approach's strengths and weaknesses, and emphasizes the importance of team consensus for effective software project management.
This article recounts a company's shift from traditional project management to agile practices, detailing demand grooming, sprint planning, daily stand‑ups, iteration reviews, retrospectives, and the integration of a simple three‑state Kanban board within TAPD to handle uncertain work and improve continuous delivery.
This article explores the origins of DevOps, defines its core principles, explains why organizations adopt it to accelerate delivery, reduce technical debt, and eliminate system fragility, and debunks three common misconceptions about its relationship with agile, tooling, and role expectations.
The article examines how modern development teams often overlook critical aspects of the Agile manifesto—particularly code quality and system flexibility—by reviewing the evolution from waterfall to Agile, highlighting common pitfalls, and suggesting practices such as CI/CD, DevOps, and modular design to sustain rapid, reliable delivery.
The article outlines five essential principles—goal alignment, transparent planning, consistent rhythm, cross‑team mechanisms, and a shared Definition of Done—to help multiple agile teams collaborate efficiently and deliver products successfully, while also mentioning a related DevOps hackathon event.
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.
Luc Julia, co‑founder of Siri and Samsung’s chief technology officer, shares how his early fascination with personal computers and human‑computer interaction led to pioneering voice assistants, the challenges of building Siri’s massive backend, the push for agile methods at HP, and his vision for AI’s ecological impact and future across industries.
This article traces the evolution of software development practices from the linear Waterfall model through Agile iterations to the integrated DevOps culture, highlighting each approach's principles, advantages, and key differences for modern engineering teams.
The article shares a personal journey through agile testing practices, Scrum adoption, quality measurement, and the challenges of fostering true agile testing within software teams, highlighting the evolution of roles, metrics, and cultural shifts needed for effective quality engineering.
This article compares Agile and DevOps, outlining their core values, processes, team structures, planning approaches, and how they can be combined to improve software development productivity and delivery speed.
The article examines Elon Musk’s five‑step work method—originating from the Model 3 production crisis—as a practical agile framework that combines demand validation, minimal processes, continuous simplification, rapid iteration, and automation to drive innovation in high‑tech manufacturing and R&D organizations.
This article explains how to keep software architecture simple and appropriate by applying KISS principles, balancing completeness, flexibility, and lightness, outlines when pre‑design is sufficient or excessive, presents core design principles such as SOLID, N+1, statelessness, and details a six‑step C4‑based design and review process.
This guide defines technical debt, outlines its classification into vulnerabilities, bugs, and code smells, and presents clear objectives, principles, standards, evaluation rules, recommended practices, and metrics to visualize, assess, and systematically reduce debt, thereby improving project delivery efficiency.
The essence of agile lies in embracing trial‑and‑error and taking small, rapid steps, which together keep projects out of high‑risk gambles and steer them toward steady, predictable progress by continuously learning and adapting to change.
This article provides a comprehensive overview of agile development and Scrum, explaining core concepts, roles, artifacts, workflow stages, and practical implementation tips through a real-world case study, while also offering advice on maintaining iteration rhythm and ensuring successful adoption.
This article explains why writing user stories at the wrong time is a common agile pitfall, outlines three typical anti‑patterns—converting requirement documents, only drafting stories before an iteration, and overly detailed stories—and presents a recommended, lightweight backlog‑driven approach for effective story creation and continuous refinement.
Lean Software Development (LSD) is an agile framework that emphasizes delivering value and eliminating waste, offering principles and practices that streamline workflows, boost quality, enhance learning, and foster continuous improvement across software projects.
This article presents a comprehensive framework called the "Golden Triangle" for improving software development efficiency, detailing three interrelated components—efficiency practices, an integrated platform, and data‑driven metrics—along with their goals, value propositions, classification, and practical implementation recommendations.
This article explains Bruce Tuckman's five-stage team development model, its later addition of a fifth stage, and offers practical guidance for agile project managers on how to lead teams through forming, storming, norming, performing, and adjourning phases to ensure project success.
This guide explains how to conduct a Scrum iteration retrospective by clarifying its purpose, preparing the right participants and materials, leveraging Projex data such as efficiency metrics, burn‑down charts and defect trends, and turning feedback into concrete improvement actions for continuous team improvement.
The article explains ITIL 4’s Service Value System, detailing its seven interrelated guiding principles—Focus on Value, Start Where You Are, Progress Iteratively with Feedback, Collaborate and Promote Visibility, Think and Work Holistically, Keep it Simple and Practical, and Optimize and Automate—and shows how they jointly create stakeholder value, illustrated with real‑world examples from the Youzan e‑commerce platform.
This comprehensive guide walks team leaders through transforming waterfall projects into agile Scrum workflows, explains the bi‑weekly iteration cycle, and details how to prepare, conduct, and document a high‑efficiency iteration planning meeting using the 云效项目协作·Projex tool.
The article explains the concept, purpose, common criteria, necessity, potential risks, side effects, and best‑practice recommendations for using Definition of Ready (DoR) in agile teams, emphasizing that DoR should guide development without becoming an inflexible waterfall‑like gate.
This article explores various innovative metric visualizations and practices for agile teams, distinguishing process and value metrics, emphasizing accurate data collection, and offering numerous chart examples to deepen insight and drive continuous improvement.
The article explains how a Scrum master uses the ORID (Objective‑Reflective‑Interpretive‑Decisional) framework to structure a sprint retrospective, detailing preparation, four discussion rounds, voting on improvement actions, and post‑meeting follow‑up to enhance team collaboration and process quality.
This article explains the Scrum framework—its core concepts, roles, ceremonies, and iterative process—and discusses how game development teams can adopt Scrum and Scrum of Scrums to improve efficiency, manage change, and deliver valuable products.
The article explains continuous deployment, using IMVU as a case study to illustrate how rapid release cycles affect software quality, team incentives, and culture, and argues that frequent, small deployments improve learning, reduce waste, and boost morale while challenging traditional batch‑oriented development practices.
The article examines the evolution of project management standards, highlights China’s recent national guidelines, and presents JD.com’s intelligent shopping guide AI project as a case study illustrating how business‑driven value streams, advanced technologies and rigorous target‑benefit management can shape modern project management practices.
This article explains the concept of time boxes in Scrum, lists the common Scrum events and their recommended durations, discusses the advantages of fixed‑length meetings, offers guidance on handling overruns, and provides advice on selecting appropriate time‑box lengths while noting a related DevOps hackathon.
This article outlines a standardized test case review workflow, analyzes current challenges in agile environments, and presents a detailed design for an integrated online test case review platform, including framework, functional features, implementation steps, and best practices to improve test quality and risk management.
This article shares four practical techniques—a dot‑timing method, magnetic‑fixing method, user‑story card stacking, and goal‑confidence index—to help Scrum Masters design clearer, more motivating task boards that improve visibility, reduce waste, and strengthen team focus on sprint objectives.
This article shares practical experience of applying the Agile Team Maturity Model (ATMM) to evaluate and improve agile team processes, detailing the model’s evolution, assessment steps, team dialogues, feedback, and lessons learned for effective R&D management.
This article explains the purpose of an agile team maturity model, highlights the unique mindset‑driven nature of agile, and proposes a preliminary PMTV (People, Mechanism, Tool, Value) framework with detailed assessment criteria for evaluating team capabilities and improvement opportunities.
This article examines how defining and progressively moving the Definition of Done (DoD) within agile feature teams can clarify goals, reduce unfinished work, improve iteration completion and delivery rates, and ultimately increase development throughput through concrete metrics and practical steps.
The 2021 Kanban State Report, translated by Agilean, reveals that Kanban is widely adopted across industries, with most teams using digital tools, lane‑based boards, and emphasizing incremental evolution, visualization, and tool selection, while highlighting the benefits of training and the popularity of Jira despite mixed recommendations.
The article analyses why many team‑level agile transformations encounter strong resistance, loss of momentum after the coach leaves, and systemic mismatches, and proposes practical, collaborative approaches such as workshops, incremental change, aligned incentives, leadership mindset shifts, and focused problem‑solving to achieve sustainable agile adoption.
The article examines why Daily Scrum meetings often feel painful, explains the three guiding questions from the Scrum Guide, clarifies that Sprint scope can be renegotiated while the Sprint Goal remains fixed, and offers practical steps and examples for defining powerful Sprint Goals that keep teams focused on value and incremental delivery.
This article explores how Project Management Offices function within agile organizations, examining the risks they mitigate, the governance they provide, the tension with agile teams, and practical approaches for integrating PMOs as supportive leaders in large‑scale agile transformations.
This article traces the evolution of DevOps from its roots in Toyota’s Production System and early manufacturing practices through the emergence of Kanban, Waterfall, Scrum, Agile, Lean, and modern extensions like ChatOps, GitOps, FinOps and AiOps, highlighting key milestones and concepts.
This article examines how a software team transformed its daily stand‑ups by introducing physical Scrum and Lean Kanban boards, detailing the observed problems, step‑by‑step improvements, measurable outcomes, and future refinements to enhance transparency, focus, and value‑flow.
This article examines the challenges Chinese banks face in moving from team‑level to product‑level agile, and presents Thoughtworks’ systematic “Four‑Stage Eight‑Step” framework—including goal definition, mechanism building, operation promotion, and result verification—to achieve rapid, end‑to‑end agile transformation.
This article explains the concept of transformation, distinguishes Agile transformation from Digital transformation, outlines their respective benefits, presents ten advantages of applying Agile to digital initiatives, and provides a six‑step roadmap with metrics and leadership guidance for successful organizational change.
This article argues that Agile has become a buzzword while failing to deliver real value, highlighting ten fundamental flaws such as limiting agility to development teams, lacking automated testing, ignoring code and requirement quality, misusing staffing practices, treating Agile as a mere tool, and enforcing rigid functional divisions that together undermine true agility.
This article explores why tech managers face questions about staffing, delivery speed, and 996 culture, then proposes a scientific approach to measuring team performance using four core DevOps metrics—lead time, deployment frequency, MTTR, and change‑fail rate—along with supporting indicators such as WIP, code size, and bug count.
Bank of Communications shares its award‑winning DevOps journey, detailing how a Level 3 maturity assessment, agile practices, AI integration, and cross‑department collaboration have driven its digital transformation, improved delivery speed, and positioned it as a leader among state‑owned banks in China.
This article details a localized Scrum framework for the Materials Center project, covering core workflow, role responsibilities, backlog management, adapted Scrum events, definition of "Done", story‑point re‑evaluation, and a summary of successes and areas for improvement, providing practical guidance for agile teams.
This guide outlines practical facilitation methods for agile retrospectives—including preparation steps, divergent and convergent techniques, opening and closing rituals, handling ad‑hoc teams, using retrospectives as training, and fostering self‑management—to continuously improve team effectiveness.
This article shares a step‑by‑step case study of how an agile coach transformed a team anniversary celebration into a focused workshop that sparked open dialogue, strengthened collaboration, and delivered measurable improvements in team spirit and performance.
The article outlines how R&D organizations evolve from functional to cross‑functional Scrum teams using a 3‑3‑5‑5 framework, physical and electronic Kanban (Jira with plugins), defined domain, project and story owners, and data‑driven metrics to monitor effectiveness, align product and research, and continuously improve value delivery across design, implementation and operation.
The article explores how daily stand‑up meetings, a staple of agile software development, can become truly effective by addressing subtle details, common pitfalls, participant roles, timing, structure, and facilitation techniques that keep meetings short, focused, and valuable for the whole team.
The Baidu Tech Salon #95 brought together senior engineers and experts to discuss the importance of engineering capability, China Mobile's DevOps transformation under its "cloud shift" strategy, and innovative approaches to undergraduate software engineering education, offering actionable insights for developers and organizations.
Digital transformation demands a shift from traditional hierarchical structures to networked, platform-based, self‑driven, data‑driven, and learning‑oriented organizations, and requires cultivating digital management, professional, and application talent—learning‑oriented, innovative, and agile individuals—to enable collaboration, empowerment, and sustained competitive advantage.
This article traces the evolution of DevOps from its roots in Toyota Production System and Kanban through Waterfall, Scrum, Agile, Lean, and modern extensions like ChatOps, GitOps, FinOps and AiOps, highlighting key milestones and their impact on software delivery practices.
This article chronicles the history of DevOps and its related practices—from the Toyota Production System and Kanban to Waterfall, Scrum, Agile, Lean, and modern concepts like ChatOps, GitOps, FinOps and AiOps—highlighting how each milestone shaped today’s software delivery culture.
The article explains five distinct agile coaching postures—coach, lecturer, mentor, consultant, and role model—detailing when to adopt each, how to transition between them, and the importance of maintaining neutrality while guiding teams toward self‑directed improvement.
This article details Bank of Communications' successful DevOps standard assessment, showcasing how its Smart HR and Cross‑border Finance projects reached Level 3 maturity, the interview insights from the project manager, and the broader impact of DevOps practices on banking digital transformation.
This article outlines SAFe 5.0’s core concepts—organizational agility, a culture of continuous learning, and a measurement‑driven growth process—explaining how lean thinking, strategic agility, and iterative improvement enable enterprises to respond faster to market changes and sustain competitive advantage.
This article outlines six practical metrics—unified backlog, user‑centric requirement description, consistent requirement flow, short lead time, high iteration completion rate, and stable iteration velocity—to help teams distinguish superficial agile ceremonies from truly effective agile execution.
The author shares a decade‑long progression from junior developer to technical director, offering practical advice on mentorship, continuous learning, agile practices, and leadership that can help developers at any stage navigate their own career growth.
This article shares a practical three‑step method for turning KPI from a hindrance into a catalyst during agile and DevOps transformation, covering urgency creation, pilot projects, and performance‑assessment redesign, while illustrating how integrated tools and feedback loops boost delivery efficiency and business value.
This article outlines frequent software development errors—such as misunderstanding the product, ignoring assumptions, poor communication, and siloed teams—and offers practical advice on product context, collaborative practices, and agile processes to help teams deliver successful projects.
The article analyses why agile methods often fail in large enterprises, highlighting cultural, managerial, and skill‑related obstacles, critiquing frameworks such as SAFe and Scrum, and offering concrete suggestions for improving team composition, processes, and leadership to achieve real software value.
This reflective essay examines the evolution of agile coaching in China, distinguishes technical and non‑technical coaching streams, highlights the recurring dilemmas faced by coaches—including misaligned expectations, lack of true leadership, and the pitfalls of self‑organization—and argues that continuous identification of team needs and strategic thinking are essential for a sustainable coaching practice.
This article explains the distinction between well‑defined and high‑uncertainty project work, compares traditional waterfall planning with modern Agile practices, and presents data showing Agile’s higher success rates while also providing practical guidance for teams transitioning to more exploratory development approaches.
