The article argues that agile is a set of guiding principles—early delivery, rapid feedback, and adaptation—rather than a rigid set of practices like Scrum or Kanban, and advises teams to tailor processes to their context instead of blindly following a prescribed workflow.
The article presents a comprehensive overview of 17 project management methodologies, explains why multiple approaches exist, outlines five key factors for selecting the right one, compares Waterfall and Agile, and summarizes each method’s core characteristics and suitable scenarios.
A software team discovered that Scrum’s ceremonies and story‑point focus were masking weeks of unfinished work, so they switched to Kanban with WIP limits and flow metrics, ran a simple JavaScript simulation, and measured dramatic improvements in cycle time, delivery volume, and team morale.
The article examines how leading tech companies are abandoning Scrum and traditional agile ceremonies in favor of more flexible, outcome‑focused methods such as OKRs, a "no formal methodology" approach, and Shape Up, highlighting economic pressures, talent dynamics, and the evolving role of agile professionals.
This article explains Scrum@Scale, its core concepts, components, roles, events, and decision‑making teams, showing how organizations can scale Scrum effectively while maintaining agile principles and addressing common challenges such as prioritization, delivery quality, and organizational change.
The article explains the historical evolution of software testing, argues for the continued necessity of independent testing teams within DevOps, and details a customized Agile framework—including Scrum, Kanban, and XP—along with roles, artifacts, values, ceremonies, and practical steps for successful adoption.
This article presents a detailed Scrum Master checklist covering questions for the product owner, team dynamics, engineering practices, and organizational health, providing a practical guide for improving Scrum effectiveness while also noting a promotional announcement for a DevOps certification program.
This article explains the concept of story points as a relative estimation unit, why agile teams use them, how they are applied across Scrum ceremonies, and answers common questions about their relationship to effort, value, and managerial decision‑making.
The article explains how enterprises can transition from traditional waterfall development to scaled agile practices by introducing Scrum of Scrums (SOS) architectures and three scaling models—1+1+2N, 1+3N, and 1+4N—detailing their structures, meetings, advantages, and limitations for teams ranging from dozens to hundreds of members.
This article details a company’s year‑long evolution of a one‑day Scrum Master training program, covering its motivation, survey‑driven redesign, scenario creation, theory delivery techniques, domino‑based sandbox exercises, key agile practices like time‑boxing and retrospectives, and the resulting growth of a sizable certified Scrum Master talent pool.
This article explains how to build an effective agile team, conduct concise stand‑up meetings, run purposeful planning, acceptance, and retrospective sessions, and avoid unnecessary customizations by following core Scrum guidelines, offering practical tips for roles, meeting formats, and team dynamics.
This article reviews the most popular software project management methodologies—including Waterfall, Agile, Scrum, Kanban, and Lean—detailing their processes, advantages, and disadvantages, and offers guidance on selecting the approach that best fits a project's requirements, team size, and organizational culture.
This guide reviews three popular Scrum tools—VivifyScrum, Scrumwise, and ActiveCollab—detailing their features, advantages, drawbacks, pricing, and integration options to help developers and project managers choose the most suitable solution for agile software projects.
The article examines the circumstances under which a Scrum team might outgrow the framework, discussing the Stacey matrix, evolution of team maturity, key indicators of diminishing Scrum value, and concluding that teams should abandon Scrum when it no longer serves its risk‑reduction and product‑discovery purpose.
The 2022 China Enterprise Agile Practice Whitepaper, based on a survey of 644 companies across 43 cities and 16 industries, uncovers how agile adoption has surged, highlights dominant frameworks like Scrum of Scrums, identifies key engineering practices, and pinpoints organizational culture as the biggest hurdle for Chinese firms navigating digital transformation.
The article argues that every Scrum event—daily stand‑up, sprint planning, sprint review, and sprint retrospective—is essential for transparency, inspection, and adaptation, making it incorrect to label any single event as the most important.
The article explains how managerial interference and misguided expectations hinder Scrum teams, outlines common harmful practices such as dictating tasks, enforcing rigid plans, rewarding unsustainable pace, and ignoring organizational obstacles, and offers concrete guidance for leaders to support true Scrum adoption and sustainable team performance.
This article provides a detailed overview of user stories, their three essential elements, writing guidelines, role modeling, collection methods, acceptance testing, and practical application within Scrum, including estimation, prioritization, iteration planning, and the advantages and pitfalls of using user stories in software development.
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 five typical problems that hinder effective Scrum iteration retrospectives—monotonous formats, unimplemented improvement actions, lack of business participation, unsafe environments, and unrealistic "change‑the‑world" expectations—and offers practical guidance and tool resources for agile coaches to revitalize these meetings.
This article summarizes four years of agile transformation in the JD Cloud Platform R&D department, detailing cultural building, continuous agile practices, practical guidelines, effectiveness measurement, and insight analysis across five key areas to improve organizational, technical, and project 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.
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.
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.
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 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.
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.
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.
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 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.
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 explains why Scrum teams must be cross‑functional, describes the problems caused by missing skills or external dependencies, and offers practical ways to develop such teams through internal training, contracts, small stable groups, and a paper‑airplane game to illustrate agile principles.
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 article explains why a clear Sprint Goal is essential for delivering stakeholder value, how it guides team collaboration, planning, and re‑planning, and the additional benefits such as fostering swarming, improving velocity, and maintaining focus throughout the Sprint.
This article compares the traditional Waterfall development model with Agile methodologies, outlines Scrum roles and processes, and discusses how teams can balance documentation‑heavy and people‑centric approaches to improve software project efficiency and adaptability.
The article explains what documentation means in agile development, why completely abandoning docs is harmful, and how to create documentation that truly adds value by applying the 5W1H framework, timing, stakeholder focus, and lean practices within Scrum teams.
This article explains how Agile teams can use the MoSCoW prioritization technique to sort Sprint Backlog items, detailing the meaning of each MoSCoW category, the roles of Product Owners and Scrum Masters, and handling special cases such as skill mismatches and evolving user needs.
This article translates and expands on the whitepaper "The 8 Stances of a Scrum Master v2.0", detailing the servant‑leader, facilitator, coach, manager, mentor, teacher, impediment remover, and change‑agent roles, clarifying common misconceptions, and sharing personal experiences on adopting a 100% Scrum Master identity.
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.
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.
The author, despite not being an avid reader, curates a personal list of twenty essential Agile and DevOps books—ranging from novel‑style introductions to practical guides—offering brief insights on each title to help readers deepen their understanding of agile practices and DevOps culture.
This article explores three key agile‑requirements questions—how many layers are appropriate, whether an Epic is a User Story, and if User Stories belong to Scrum—by examining Scrum guides, historical origins, and practical hierarchy models such as Theme‑Initiative‑Epic‑Story.
This article describes how Worktile introduced Scrum, built an 8‑person self‑organizing Scrum team for the Lesschat product, iterated through two‑week Sprints, identified and solved scaling challenges, and eventually evolved into a multi‑team, hundred‑person agile R&D organization with continuous delivery practices.
This article compares four typical R&D models—including Waterfall and Agile—explains their suitable scenarios and trade‑offs, then delves into Scrum’s core concepts, roles, artifacts, events, and metrics, offering practical guidance for teams transitioning to agile development.
This article details how KuJiaLe's internal "Afu Workshop" used agile coaching steps—assessment, training, calibration, creative retrospectives, and continuous feedback—to dramatically improve sprint completion rates, velocity, and team satisfaction across two product squads.
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 article explains agile testing as a collaborative team activity, defines its broad and narrow meanings, describes the role of agile testers, outlines ten guiding principles, presents testing strategies, the test‑automation pyramid, agile testing quadrants, and the agile testing manifesto.
This article explains Scrum sprint planning, covering its definition, goals, participants, inputs and outputs, preparation steps, time‑boxing rules, focus on outcomes over tasks, estimation techniques, and practical best‑practice tips for running effective sprint planning meetings.
This article provides a comprehensive, section‑by‑section comparison of the 2020 Scrum Guide with the 2017 version, highlighting shifts in terminology, added emphasis on value creation, self‑management, lean thinking, and the removal of prescriptive language, accompanied by the author’s personal interpretations.
This article explains why Scrum retrospectives are essential for continuous improvement, outlines the preparation steps, agenda items, facilitation techniques, and key pitfalls to avoid, providing practical guidance for agile teams to run effective review meetings.
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 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 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.
This article explains agile testing principles, contrasts them with traditional waterfall testing, and details how the P1 project applied Scrum testing practices—short delivery cycles, daily stand‑ups, bug triage, continuous collaboration, technical excellence, and streamlined processes—to achieve rapid, high‑quality software releases.
This article explains why many agile retrospectives become lengthy and ineffective, analyzes the root causes, and provides a step‑by‑step PDCA‑based framework—including pre‑meeting preparation, meeting design, execution, and follow‑up—to ensure actionable improvement items are planned, executed, checked, and acted upon.
This article identifies frequent agile‑method traps—acting like a project manager, making unilateral decisions, over‑monitoring, slow change handling, and indirect communication—and offers practical remedies to help agile leaders foster trust, autonomy, and faster delivery.
This tutorial walks developers through installing ZenTao via Docker, explains core Scrum concepts, and demonstrates step‑by‑step how each role—admin, product owner, scrum master, developer, and tester—uses ZenTao to execute a complete agile project lifecycle.
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.
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 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 article adapts William J. Donovan’s sabotage manual to reveal how easy it is to undermine an agile team’s efficiency and how practical tactics—like over‑reliance on supervisors, ignoring feedback, and over‑building features—can silently destroy true agility.
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.
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 compares the traditional Waterfall model and the modern Agile approach, outlining their processes, advantages, disadvantages, and suitability for different projects, helping teams decide which methodology best aligns with their product goals and organizational constraints.
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.
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 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.
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.
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.
This reflective essay examines how agile development, flat management, and engineering culture intersect, contrasting traditional control‑heavy standards like ISO9000 and CMM with the open, collaborative approaches exemplified by Linux, Scrum, and modern tech giants, and explores how organizations can nurture both rigor and innovation.
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.
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 recounts a Nokia mobile‑software project where a newly appointed agile consultant analyses the company’s Scrum adoption, team structure, user‑story splitting, point‑based estimation, and the exclusion of testing and code‑review effort to improve planning and delivery for a ten‑month, 200‑person product development effort.
This article presents a series of agile process‑improvement case studies—including flexible response to change, effective communication, goal‑aligned teams, and robust engineering culture—offering practical guidance for software teams seeking to adopt and sustain agile transformations.
This article outlines how teams can transition to agile development by adopting Scrum or Kanban, emphasizing self‑organization, realistic planning, continuous integration, automated testing, regular retrospectives, and servant‑leadership to sustainably deliver business value while managing technical debt.
The article uses a bicycle analogy to explain why teams should first faithfully follow Scrum, then experiment with modifications only after sufficient practice, recommending a 100‑hour disciplined trial before deciding to trim the framework.
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.
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.
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 explains the core concepts of Agile development, compares it with traditional waterfall methods, outlines its benefits such as faster response and higher quality, and introduces practical frameworks like Scrum and XP along with key practices like TDD and continuous integration.
This guide explains the fundamentals of product backlog creation, outlines essential backlog attributes, demonstrates how to use Worktile for backlog and sprint planning, covers sprint backlog management and burn‑down chart generation, and concludes with practical tips for agile teams.
This article explains how to use user stories as a collaborative tool for agile product planning, detailing the key challenges, the roles involved, the three-step storytelling process (finding clues, drawing the main line, and specification), and how to run effective requirement workshops.
This article compares waterfall and agile approaches to software architecture, examining the architect's role, time span, deliverables, and documentation practices, and offers practical guidance for building sustainable, adaptable system designs in modern development environments.
This article shares NetEase Youdao Note’s practical Scrum experience, outlining when agile development fits, how to scale Scrum teams, the role of Scrum Masters, metrics for team performance, and tips for efficient sprint planning and cross‑team collaboration.
The article traces the ten‑year evolution of the Agile Manifesto, examines the perspectives of its signatories and industry experts, compares Scrum, XP, Kanban and RUP, and discusses the challenges and conditions required for successful Agile adoption in modern software projects.
