1 views collected around this technical thread.
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 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.
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 that agile transformation focuses on people and continuous improvement, not merely applying a standard Scrum framework, and argues that coaching is essential to guide teams from merely following processes to truly embodying agile values.
The article explains why agile transformations often fail when teams focus only on isolated Scrum practices, and proposes that true improvement requires synchronizing the process chain, organizational structure chain, and tool chain to achieve smoother end‑to‑end business delivery.
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.
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 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.
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.
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.
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.