0 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 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.
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 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.
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.
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 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 explains how a small SaaS product team can adopt agile management by visualizing work with four Kanban boards, categorizing product and technical demands, and leveraging Atlassian Confluence and Jira to improve transparency, communication, and delivery efficiency.
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 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 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.
Youzan scales demand backlog management from a single product to multiple lines by aligning OKR‑driven strategic goals with stakeholder inputs, centralizing ownership in a product‑owner‑led backlog that integrates information, uses user‑story, impact‑mapping and MoSCoW prioritization, employs fixed Scrum/Kanban cycles, splits large backlogs by domain, and leverages electronic kanban tools while continuously refining granularity and value‑loop closure.
This article explains how buffer zones in a Kanban board help identify bottlenecks, illustrates the problem with limited WIP using a case study, and provides practical steps to set up transition states as buffers to improve overall workflow efficiency.
The article draws parallels between emergency rooms and IT operations, describing how Kanban's WIP limits, one‑to‑one liaison models, transparent dashboards, and Scrum time‑boxing (daily stand‑ups and weekly reviews) help a globally distributed team prioritize urgent incidents while still advancing important non‑urgent work.
This article provides an in‑depth tutorial on leveraging Atlassian's JIRA and Confluence to support agile principles such as decentralization, collaboration, transparency, and visualisation, covering issue types, workflows, boards, release management, knowledge sharing, and seamless integration between the two tools.
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.
The article introduces the Kanban method as a lean approach to managing professional services, outlines ten essential principles such as focusing on flow, incremental change, risk management, and scalability, and concludes with a recruitment announcement seeking DevOps engineers in Beijing.
This article examines common misconceptions and mistakes in implementing Agile and DevOps—such as misusing Scrum, overly long daily stand‑ups, indiscriminate automation testing, superficial CI pipelines, and ineffective Kanban—while offering concrete, principle‑driven practices to achieve efficient, high‑quality software delivery.
The article explains why Kanban, with its three simple practices of visualizing workflow, limiting work‑in‑progress, and continuously improving flow, is a lighter, less intrusive alternative to Scrum for agile and lean project management, even in traditional waterfall environments.
This article recounts a real‑world Kanban board improvement performed by a software development team, describing the initial problems, a 15‑minute, four‑step redesign process, and the resulting clearer task visibility, better WIP control, and stronger team alignment.