1 views collected around this technical thread.
Behavior‑Driven Development (BDD) is an agile methodology that uses natural‑language Gherkin scenarios to describe system behavior, fostering collaboration among developers, testers, and product owners, with detailed examples, best practices, and tool recommendations for implementing BDD across various software projects.
The article explores the challenges of product design, explains how misaligned communication hampers requirement understanding, introduces user journey maps as a visual tool to align teams, outlines their components and a step‑by‑step process for creating effective maps, and highlights their value for product management.
The article traces the progression of software development methodologies—from the linear waterfall model to flexible Agile practices, the collaborative DevOps culture, and emerging AI‑driven and low‑code approaches—highlighting their benefits, challenges, and the impact on modern engineering workflows.
The Release Train Engineer (RTE) is a pivotal role in the Scaled Agile Framework (SAFe) responsible for coordinating multiple agile teams, facilitating PI planning, removing impediments, enhancing transparency, and driving continuous improvement, with growing demand across large enterprises and promising career prospects.
The article draws parallels between Buddhist mindfulness and software engineering, urging developers to focus on the current code snapshot, accept change as the only constant, avoid premature work for an uncertain future, and always choose the simplest solution that meets today’s needs.
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.
Test‑Driven Development (TDD) and Behavior‑Driven Development (BDD) are software development approaches that start with writing tests or user stories, outlining core steps, advantages, disadvantages, and offering guidance on selecting the appropriate method based on project requirements, team expertise, and business communication needs.
The article explains the principles of agile methodology and agile testing, highlighting the benefits of early involvement, continuous feedback, customer‑centricity, test‑driven development, regression testing, lightweight documentation, and collaboration, and introduces the concept of pure agile as a strict adherence to the Agile Manifesto.
These reading notes dissect Brooks’s *The Mythical Man‑Month* anniversary edition, tracing its historical context, explaining the person‑month fallacy, Brooks’s law, and communication overhead, then mapping those lessons onto today’s agile, CI, modular testing practices while noting documentation trade‑offs and including community‑engagement promotions.
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.
The article analyzes why software engineering management has made little progress in the last ten years, highlighting the lag between rapid technological advances and outdated management practices, cultural and human challenges, and insufficient education and training, and it presents a list of questions collected from various companies.
This article provides a detailed guide on user stories in agile project management, covering definitions, characteristics, benefits, differences from traditional requirements, writing techniques like the INVEST principle and BDD format, common pitfalls, and best practices such as workshops, continuous feedback, and collaboration with development teams.
This article examines how DevOps reshapes the product manager’s responsibilities, highlighting traditional limitations, the drivers for role transformation, required capabilities such as agile mindset and DevOps tool proficiency, and effective collaboration mechanisms to achieve faster, higher‑quality product delivery.
This article explains Domain-Driven Design (DDD), its key concepts such as bounded contexts, ubiquitous language, domain models and layered architecture, traces its evolution, highlights recent trends like Event Storming and CQRS, and draws parallels to technical team management practices for handling complexity, communication, iteration, and strategic focus.
The 2024 XOps Industry Innovation Forum in Beijing unveiled the China DevOps & BizDevOps State Survey, revealing that over 6,300 enterprises participated, with more than 60% adopting agile practices, 83% using containers or VMs, and a growing focus on automation, testing, and BizDevOps transformation across diverse sectors.
The article reviews the history of China's IT industry over the past eighteen years, exposing how government policies, CMM certifications, and superficial agile practices have led to chronic software quality and delivery problems, and argues that only solid fundamentals such as extreme programming, TDD, and deliberate practice can truly improve software development.
The article explains software architecture concepts, the architect’s duties of extracting requirements, designing and implementing solutions, and presents methodologies such as the C4 model, 4+1 view and domain‑driven design, while outlining how to develop architectural thinking through study, practice, reflection and ongoing learning.
Over the past two decades, software engineering has shifted from waterfall to agile, embraced DevOps, cloud and micro‑services, containerization, CI/CD, open‑source, AI, heightened security, diverse languages, remote collaboration, user‑centered design, dependency management, and continuous learning, while core concepts such as requirements analysis, design principles, testing, version control, and architecture remain unchanged.
This case study describes how a large manufacturing company's IT department, led by Michael, overcame strong internal resistance from senior staff to transition from a traditional waterfall development model to an agile and DevOps approach through personalized communication, stakeholder engagement, and transparent implementation planning.
The article reviews China’s DevOps capability maturity model, its adoption across more than 20 industries, and showcases how leading securities firms such as China Merchants, Guoxin, and Dongguan have achieved advanced agile development, continuous delivery, technical operations, security, and tool standards, highlighting measurable improvements in delivery speed, quality, and automation.