This article explains the evolution from monolithic applications to microservices, outlines the advantages and disadvantages of both architectures, and provides practical guidance on when and how teams should adopt microservices to improve agility, scalability, and organizational efficiency.
This article introduces the agile 7Ps framework for designing and running effective meetings, explaining each of the seven key elements—Purpose, Product, People, Process, Pitfall, Preparation, and Practical concerns—and offers practical tips and a canvas to help organizers plan, execute, and evaluate meetings efficiently.
This article explains how traditional, lengthy test‑strategy documents can be replaced by a concise, one‑page visual diagram that clearly presents what to test, how to test, guiding principles, and the roles of test left‑shift, test quadrants, test layers, and test right‑shift, using a real‑world example to illustrate the approach.
The article outlines a comprehensive CDO action guide, presenting ten practical steps—including executive sponsorship, appointing a chief digital officer, setting clear strategic goals, adopting agile development, measuring economic impact, and fostering an innovative culture—to help enterprises navigate and succeed in digital transformation.
This article explains the end‑to‑end software project lifecycle—from research, design, development, testing, and operation—detailing each role’s responsibilities, agile scrum practices, DevOps automation, CI/CD pipelines, and the user access flow that together ensure efficient, reliable delivery of web applications.
The article explains how adopting Just‑In‑Time (JIT) thinking and lean‑startup validation can help product teams filter out 80% of low‑value requests, accelerate delivery, reduce overtime, and align development effort with the most valuable business outcomes.
The Shanghai DevOps Best‑Practice Salon gathered experts from banks and tech firms to share real‑world experiences on DevOps adoption, lean R&D efficiency, agile pipeline construction, and DevSecOps integration, offering actionable lessons for modern IT operations.
This article examines daily stand‑up meetings in agile software development, outlining essential practices, common pitfalls, and detailed patterns—including participant roles, question formats, speaking order, timing, energy‑keeping techniques, and autonomy‑building strategies—to help teams run concise, valuable syncs.
This article explains how GrowingIO's R&D department structures project classification, work, personnel, and time management using Jira, detailing requirement handling, iteration processes, and practical Scrum/Kanban practices to balance OKR goals with customer demands.
The article examines the controversy around low‑code platforms, argues they are not a harmful industry toxin, and explains how technological progress—from steam power to AI—has driven the evolution from ERP to middle platforms and finally to low‑code as a key enabler of agile enterprise transformation.
This comprehensive guide explains why breaking down user stories is crucial for agile teams, defines proper story formats, introduces the INVEST criteria, describes vertical versus horizontal slicing, outlines a step‑by‑step splitting flowchart, explores Cynefin domains, offers nine concrete splitting patterns, and provides practical advice for scaling and team organization.
This article shares how a large SaaS company tackled the difficulty of defining and adopting R&D efficiency metrics in agile squads by strengthening awareness, boosting participation, establishing clear standards, and using data‑driven feedback to achieve measurable improvements in delivery speed and quality.
This article examines how Qunar’s technology director applied Domain‑Driven Design to reshape business processes, the challenges faced, tools used, and practical steps for teams to adopt DDD effectively in a large micro‑service environment.
A seasoned tech manager shares a tongue‑in‑cheek 13‑point manifesto on how misguided agile practices, ego‑driven coaching, disrespect for team members, reckless experimentation, and neglect of proper planning can quickly cripple a software development team.
This article outlines the core concepts of project management, including its definition, goal types, unique characteristics, the triple constraint, comparison with routine operations, typical information‑system project traits, PRINCE2 basics, lifecycle phases, and major development models such as waterfall, spiral, iterative, V‑model, prototype, and agile.
The 2020 China DevOps Status Survey reveals that while over 60% of companies have adopted DevOps, many still struggle to assess its success, highlighting key performance criteria, maturity levels, and ongoing challenges such as expertise gaps and metric definition.
The author, a former programmer turned tech manager, humorously lists thirteen counter‑productive practices—ranging from fake agile enthusiasm and lack of coaching to cultural neglect and tool misuse—that can sabotage a development team when agile is applied without genuine understanding or respect.
This article examines why traditional testing must evolve for agile development, outlines the challenges of frequent builds, limited sprint time, performance and API testing, and provides practical guidance on planning, scope selection, parallel execution, DevOps integration, and choosing the right automation tools to boost collaboration and quality.
This article explains DevOps as the integration of development and operations, defines continuous integration (CI) and continuous delivery/deployment (CD), contrasts them with agile development, and illustrates how these practices streamline software delivery, testing, and production deployment.
The article outlines how agile development improves software quality, enhances team collaboration, increases project transparency, reduces risk, accelerates growth, and enables more accurate project assessment, making it a comprehensive methodology for modern, user‑centric software projects.
This article introduces four major software development models—Waterfall, Iterative (RUP), Spiral, and Agile—detailing their origins, core concepts, advantages, and disadvantages, helping readers understand how each approach structures project phases, manages risk, and adapts to changing requirements.
The article outlines a comprehensive framework for evaluating enterprise digital maturity across six dimensions, describes the four stages of digital transformation, presents the seven key characteristics of digital enterprises, and offers practical solutions to common obstacles such as talent gaps, unclear goals, and fragmented initiatives.
This article shares a software team’s experience of shortening release cycles from two‑week to one‑week sprints, the quality challenges encountered, the root causes of instability, and the practical process improvements—including stable release branches, extended testing windows, and holiday moratoriums—that restored service reliability.
This article traces the historical shift in software development practices, comparing the linear Waterfall model with Agile, Kanban, Scrum, and Lean approaches, highlighting how each methodology improves flexibility, transparency, and efficiency by borrowing principles from automotive production systems.
This article examines the concepts of design thinking, lean, agile, and DevOps, explains their shared focus on delivering customer value, and proposes a combined, value‑oriented workflow that integrates these methodologies through value definition, value‑stream mapping, quadrant analysis, and automation within an end‑to‑end platform.
This article compiles a wide-ranging discussion on how development teams can guarantee that developers allocate sufficient time for writing test cases despite tight schedules, covering division of testing duties, organizational processes, requirement handling, performance metrics, and skill development.
The article humorously outlines seven destructive tactics—such as poaching talent from big firms, misapplying agile, enforcing unrealistic role ratios, neglecting proper technical management, promoting false startup culture, using line‑count performance metrics, and building unnecessary middle‑platforms—to illustrate how to deliberately cripple a small‑to‑mid‑size tech team.
This guide offers practical advice for agile developers, covering stand‑up meetings, sprint planning, tracking progress, story points, and teamwork to help teams thrive in fast‑paced, remote‑first environments by emphasizing efficient communication, realistic planning, and continuous improvement.
This guide offers practical advice for agile developers, covering effective stand‑up meetings, sprint planning, time tracking, collaborative awareness, task‑tracking tools, meaningful story points, and key habits to ensure smooth, productive remote software development.
In a 2020 interview, the China Agricultural Bank DevOps Construction Engineering Team explains how they built a comprehensive DevOps capability—covering toolchains, workflow management, metrics, and standards—overcame pandemic‑related obstacles, and earned the prestigious Banking DevOps Team of the Year award while outlining their 2021 roadmap.
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.
This article explains the DevOps methodology, the roles of Continuous Integration and Continuous Delivery/Deployment, and how Agile development fits into modern software workflows, highlighting their goals, processes, and the relationships among these concepts for faster and more reliable software releases.
This article challenges the common belief that software teams are terrible at estimating by presenting real‑world examples, research findings that most estimates fall within 20‑30% of actuals, and evidence that collaborative feedback can dramatically improve estimation accuracy.
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 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 argues that many agile implementations are misapplied, creating pressure and defects for developers, and proposes that developers focus on proven software development practices such as extreme programming, continuous delivery, and test‑driven development rather than blindly following flawed agile frameworks.
DataOps, an Agile‑derived methodology that extends DevOps principles to data analytics, emphasizes automation, collaboration, and continuous delivery to accelerate and improve data processing, quality, and business insight, while outlining its benefits, relationship to Agile/DevOps, and practical steps for adoption.
This article outlines why digital transformation is essential for modern retail, defines its scope, presents a five‑stage maturity model, and offers a six‑step practical roadmap—including breaking conventions, shaping new tracks, integrating decisions, leveraging strengths, agile iteration, and ecosystem collaboration—to guide retailers through successful change.
The author reflects on personal experiences with agile adoption, emphasizing the importance of documentation, distinguishing true teams from loosely organized groups, clarifying Scrum role requirements, and discussing the unique challenges and advantages small teams face when practicing agile methodologies.
The article explains why traditional GUI testing is fragile, outlines the benefits of shifting to API testing—including early verification, automation, and comprehensive coverage of positive, negative and edge cases—and offers practical guidance for integrating API tests into an agile CI workflow.
The article explains three agile demand‑management approaches—Scrum product backlog, disciplined agile work‑item list, and lean option pool—detailing their principles, stakeholder roles, risk‑value modeling, and how to choose the most suitable strategy for a project.
Impact Mapping is a visual, goal‑driven framework that brings business, product, and engineering together to identify, test, and iteratively deliver the most valuable features that directly contribute to measurable business outcomes.
This article explains what regression testing is, why it is critical in fast‑paced agile and DevOps workflows, and provides practical strategies, best‑practice recommendations, and checklist items for building and maintaining effective regression test suites.
This article analyzes why DevOps adoption often fails, explores the Agile Flow Model with its four fluency intervals, outlines the necessary organizational investments and challenges for each stage, and presents real‑world DevOps toolchain case studies to guide effective implementation.
Traditional enterprises face low R&D efficiency due to heavy, multi‑layered project management and over 70% cross‑project, cross‑department, and supplier involvement; this discussion identifies root causes, diagnostic methods, and practical short‑ and long‑term strategies to improve coordination, visibility, and organizational structure.
This article details Zhejiang Mobile's adaptation of Google‑originated Site Reliability Engineering to a telecom environment, outlining a three‑layer capability framework, standardized processes, integrated platforms, and measurable outcomes that demonstrate how agile SRE practices can boost reliability and scalability in traditional industries.
This article explains the purpose, types, and practical benefits of maturity models for scaling Agile and DevOps in enterprises, outlining stage‑based and continuous models, design principles, and how they help teams assess current capability, set improvement goals, and continuously enhance delivery efficiency.
This article presents 30 practical guidelines for technical leaders, covering team structuring, agile practices, communication, performance tracking, and cultural initiatives to enhance productivity and morale within engineering groups while also warning against common pitfalls and emphasizing the importance of empathy and continuous improvement.
This article examines how DevOps adoption transformed the Agricultural Bank’s enterprise‑level R&D management system, detailing its evolution, the operational and cultural shifts introduced, and practical recommendations for integrating DevOps, agile, and continuous delivery at scale.
Built‑in quality emphasizes integrating quality throughout the software development lifecycle, using agile principles, continuous integration, test‑driven development, code review, and shared code ownership to reduce technical debt, avoid rework, and ensure reliable, maintainable products.
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 explains the two‑pizza team principle, arguing that keeping development teams small enough to be fed by two pizzas reduces communication overhead, encourages self‑organization and cross‑functional collaboration, and ultimately leads to more sustainable and faster project delivery than expanding large, unwieldy groups.
This article explains how agile teams can run productive retrospective meetings to capture successes, identify problems, and implement actionable improvements, sharing real‑world experiences, common pitfalls, and concrete guidelines for moderating, prioritizing, and tracking outcomes across iterations.
The article details TaiKang Insurance's journey through the GNSEC 2020 DevOps summit, its successful Level‑3 continuous‑delivery assessment, the technical and organizational challenges overcome, measurable gains such as 300% demand parallelism, 50% faster response, and future plans to expand DevOps practices across the enterprise.
This article explains why Selenium test automation requires ongoing maintenance, outlines the two main maintenance scenarios—test failures and dependency changes—and provides practical guidance for developers and testers to efficiently support and sustain automated testing in agile environments.
This article explains why functional test automation is essential for modern agile and DevOps teams, outlines how to calculate its return on investment, and provides a detailed roadmap of testing strategies, team composition, and maintenance practices to reduce costs and improve software quality.
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.
The article analyses the 2020 Chinese DevOps survey, highlighting the current maturity of agile management, continuous delivery, technical operations, application design, and security, while sharing practical experiences, tool choices, and common challenges faced by enterprises during DevOps transformation.
This article explains the Design Sprint framework—originating from Google and blending Design Thinking with Agile—to help teams solve defined problems, build low‑fidelity prototypes, and validate ideas within five focused days, covering preparation, goal setting, and execution steps.
The article outlines a set of practices for creating a small, self‑managing engineering team that continuously ships code, emphasizing no middle management, outsourcing non‑core work, short weekly tasks, pair accountability, single‑owner projects, and letting underperformers go.
This article offers practical guidance for maintaining productivity while working from home during the pandemic, covering distraction‑reduction habits, cloud‑based Selenium testing, communication tools, stable network setup, mental‑health strategies, task planning, continuous learning, and physical well‑being.
The article explains how designing autonomous, end‑to‑end responsible teams—by minimizing inter‑team collaboration, adopting full‑process or cross‑functional squads, and leveraging automation tools—leads to better software architecture, aligns with Conway’s law, and improves efficiency in modern DevOps environments.
This comprehensive guide explains why and how to split user stories in agile development, covering the INVEST criteria, story hierarchy, vertical slicing, goal decomposition, and a variety of practical techniques to create small, valuable, and testable story increments.
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.
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.
The article argues that product management succeeds when teams are cross‑functional and autonomous, eliminating inter‑team friction, and explains how motivation, mastery, and purpose drive high‑performing squads, illustrated with examples from Transferwise, Spotify, and insights from Daniel Pink’s research.
This article presents a comprehensive analysis of Ant Financial’s financial‑grade R&D efficiency practices, covering industry challenges, the SOFAStack‑LinkE platform, agile and DevOps methodologies, continuous integration, testing, deployment, release strategies, cloud‑native transformation, and consulting solutions for improving development productivity and reliability.
The article explains, using a 1982 Lisa team story and agile practice observations, why lines of code, iteration velocity, and full staff utilization are unreliable productivity metrics and advocates using global outcome metrics and leading indicators for effective software development management.
This article shares Ant Financial's experience and structured approach to managing remote software development teams, covering planning, communication, toolchains, daily routines, and the benefits and challenges of distributed work to help technical leaders optimize remote collaboration.
This article recounts how adopting agile practices—including user‑experience mapping, sprint‑0 preparation, iterative planning, daily stand‑ups, demo sessions, and retrospectives—dramatically improved delivery speed, quality, and business involvement for a corporate HR system project.
This report details how the HR system team adopted agile methods—including user‑experience mapping, Sprint 0 preparation, backlog planning, Kanban boards, daily stand‑ups, burn‑down analysis, demo sessions, and retrospectives—to improve delivery speed, quality, and business collaboration.
The article clarifies the concept of self‑organization in Scrum, compares it with Hackman’s power‑matrix levels, describes the ideal self‑organizing team, examines its benefits and pitfalls, and analyzes how Scrum would function if self‑organization were removed.
This article explains how the internally built jCover tool helps a fast‑moving Java backend team measure and improve test coverage across full‑stack, incremental, and parallel testing scenarios, addressing common challenges of agile development, tool limitations, and quality assurance.
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.
CITIC Bank’s DevOps lead Li Hongtao explains how the bank’s new organizational‑level agile practice integrates development and data‑center operations, employs a DevOps capability maturity model, and cultivates agile coaches to overcome transformation challenges, offering a practical roadmap for peers in the banking sector.
This article explains design thinking as a customer‑centric, double‑diamond process that guides product teams through discovery, definition, development, and delivery, illustrating how tools such as personas, empathy maps, journey maps, story maps, and prototypes enable sustainable, desirable, feasible, and viable solutions within agile environments.
The article describes how Ctrip Ticket's front‑end team introduced Behavior‑Driven Development (BDD) using Cucumber and the Macaca‑based MEC framework to unify requirements, automate testing, reduce manual effort, and achieve over 90% UI test coverage while cutting integration costs by 75%.
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.
Exploratory testing, a flexible, unscripted approach integral to agile development, enables rapid discovery of defects, improves user experience, and complements automated regression testing, while its various types, benefits, challenges, and common myths are examined to guide teams in effective implementation.
Agile development, created to overcome waterfall's drawbacks, focuses on boosting efficiency and responsiveness, and studying its patterns deepens understanding of this modern software methodology.
The article critiques how many organizations have become weary of Agile, describing the "Agile industrial complex" and urging a return to the original Agile Manifesto values and principles while integrating insights from social science and interdisciplinary thinking.
In an in‑depth interview, Fang Wei, former assistant general manager of Zhejiang Mobile’s network department, shares his 15‑year journey from B‑domain maintenance to leading DevOps, cloud, and AIOps initiatives, detailing the shift from waterfall processes to agile, micro‑services, containerization, and AI‑driven operations that reshaped the company’s IT landscape.
This article explains what Test‑Driven Development (TDD) is, outlines its step‑by‑step workflow, reviews its historical origins, compares it with traditional testing, and discusses the key benefits and drawbacks to help teams decide whether to adopt TDD.
The article explains what code review is, its goals, why it’s essential alongside testing, how QA professionals can effectively participate, various review methods, a Selenium‑specific checklist, and a set of best‑practice guidelines to improve software quality and delivery speed.
This article outlines Alibaba’s approach to scaling R&D efficiency across its 50,000‑engineer workforce, detailing the challenges of large‑scale development, agile and DevOps practices, value‑focused delivery, and systematic tools that enable sustained high‑quality software production.
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 introduces seven practical retrospective meeting techniques—Thermometer, Emotion Meter, Emotion Journey, Practice Box, Problem‑Solution Board, and more—explaining their purpose, execution steps, and visual examples to help agile teams foster continuous improvement and stronger collaboration.
The article analyzes how unpredictable business volatility, digital transformation, and the convergence of Agile and DevOps will reshape software testing over the next ten years, emphasizing cross‑industry impact, automation growth, and the critical role of quality engineering.
This article provides a comprehensive overview of Test‑Driven Development, explaining its principles, workflow, relationship to acceptance testing and traditional testing, its impact on design and documentation, challenges in database development, integration with Agile Model‑Driven Development, common myths, adoption statistics, and a curated list of supporting tools.
This article examines common misconceptions about agile development, explains its original intent of collaborative, iterative delivery, and shows how a large software team uses the CORNERSTONE platform to define roles, manage user stories, run sprint planning, daily stand‑ups, and track progress effectively.
The article explains the responsibilities, strategic influence, and collaborative practices of Enterprise Architects within SAFe, highlighting how they drive adaptive design, portfolio governance, cross‑solution coordination, and continuous improvement to align technology decisions with business goals.
The article argues that the primary reason agile, DevOps, and practices like TDD struggle to take root is team laziness, emphasizing that solid methods alone are insufficient without disciplined, persistent execution and proper management rituals.
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.
This article presents a detailed case study of Savioke’s robot delivery prototype using Google’s five‑day design sprint, outlines the steps and challenges of rapid product development, and extracts broader lessons on Google’s agile culture, team structure, and performance practices while also announcing a related DevOps hackathon.
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.
The article describes Tubi's three‑month experiment to replace traditional waterfall and rigid sprint models with a flexible Release Train system, outlining the motivations, principles, team roles, tooling choices, successes, and areas needing improvement for a fast‑growing startup.
The author reflects on a recent emergency department visit, highlighting excessive queuing and fragmented steps, and draws parallels to agile and DevOps transformations, emphasizing the need for customer‑centric process redesign and value‑stream mapping to reduce waste and improve efficiency.
The article debunks the myth that agile eliminates planning by showing that even in complex, time‑boxed Scrum projects a flexible, continuously‑refined plan covering scope, cost, schedule, and quality is essential for managing risk and delivering business value.
This case study details how a user product center team applied the APD agile methodology and stream development practices—such as visual value streams, explicit process rules, WIP limits, bug‑board visualization, workflow management, and an evolved TDD approach—to double throughput, cut delivery cycles by 60%, and reduce monthly bugs from 50 to 2, demonstrating measurable R&D efficiency gains.
