This article explains how to create and customize Kanban boards in TFS, covering board creation, column naming, WIP limits, status mapping, swimlane usage, card field configuration, and visual styling to improve team visibility and workflow management.
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.
A corporate dragon‑boat race on the Duanwu Festival turned into a vivid lesson on project management, highlighting how unclear roles, poor communication, lack of team harmony, and member inactivity can derail a project and offering practical tips to strengthen leadership and teamwork.
This article examines why many enterprises view user research as ineffective, outlines the four biggest challenges—defining clear goals, cultivating insight, building capable teams, and adopting the right mindset—and offers practical strategies for making research results actionable, integrating them into product development, and evolving the role of user researchers.
Discover 26 practical agile development principles—from building test cases before code to avoiding premature optimization—that guide teams to deliver high-quality software efficiently, emphasizing incremental work, continuous testing, thoughtful design, and disciplined code management.
The article introduces User Story Driving Agile Development (UDAD), a comprehensive methodology that integrates impact mapping, user story mapping, visual guidance, Scrum, Kanban, continuous integration, exploratory testing, and automated deployment to provide a cohesive, end‑to‑end agile process supported by Microsoft Team Foundation Server.
The article introduces Kanban, User Story Mapping, and Impact Mapping as visual tools to clarify requirements, explains a stepwise thinking approach from abstraction to concrete code, and offers practical advice on prototyping, delayed decision‑making, and preparation before coding to improve product development.
This article traces the evolution of web technologies from CGI to MVC and service‑oriented architectures, examines how communication challenges drive the shift from waterfall to agile development, compares expert versus full‑stack learning models, and envisions a "no‑stack" future for versatile engineers.
This article explains how to transform user stories into a product backlog, demonstrates using electronic tools such as TFS and Excel for tracking, and provides a sample e‑commerce application to illustrate agile planning, backlog management, and DevOps integration.
This article provides a comprehensive overview of DevOps, explaining its purpose, cultural challenges, core principles such as automation, standardization, and configuration, its relationship with cloud, lean and agile, practical steps, metrics, and how it transforms IT delivery into an end‑to‑end business value pipeline.
Impact Mapping is a collaborative strategic planning technique that visualizes business goals, stakeholders, desired influences, and deliverables to align product development with measurable outcomes, prevent scope creep, and improve decision‑making across agile teams.
The article analyzes the root causes of Dev‑Ops conflicts, illustrates typical complaints at each release stage, and proposes concrete measures—shared goals, platform‑driven automation, and cultural alignment—to transform friction into collaborative efficiency.
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 explains how to organize a user story map in eight practical steps, detailing the benefits of visualizing the backlog, prioritizing features, fostering collaborative brainstorming, and planning incremental releases to ensure early validation of architecture and scope.
The article recounts a hands‑on Beijing Agile Community workshop on User Story Mapping, explains the technique’s role in solving common agile requirement‑analysis problems, describes its structure and how it connects to backlog and release planning, and shares personal reflections on its usefulness for product management.
The article examines how concise, efficient, and simple development practices, agile iteration, automated testing, and thoughtful tool selection can boost individual and team productivity while maintaining software quality, offering practical examples and strategic guidance for optimizing software development processes.
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.
This article presents 22 fundamental Scrum questions covering roles, artifacts, events, benefits, limitations, and practical guidance, offering a comprehensive overview for anyone preparing to become an effective Scrum Master and deepen their understanding of agile project management.
The article explains how Scrum Masters often turn Daily Scrum into a status‑report meeting, why this command‑and‑control approach hinders agile transformation, and how shifting to a coaching role that empowers teams to self‑manage leads to more effective collaboration and continuous improvement.
Through two real-world cases, this article shows how system thinking and causal loop diagrams expose why agile and automation testing initiatives repeatedly stumble, revealing reinforcing and balancing feedback loops that lead to short‑term fixes, long‑term stagnation, and the classic ‘missing the forest for the trees’ dilemma.
Compiled from the SEI blog series, this article presents concise summaries of the six most popular DevOps topics of the past six months—including Agile integration, ChatOps communication, Vagrant environment consistency, mitigating context‑switching overhead, and a foundational overview of DevOps—offering practical insights and links to the original sources.
The article explains how architects can adopt a risk‑ and cost‑driven, lightweight approach to keep architecture agile, offering five actionable recommendations—decision‑focused delivery, a backlog of architectural concerns, economic impact prioritization, minimal architecture, and delivering just enough expectations—applicable across agile and plan‑driven projects.
The article explains how treating early users as collaborators, adopting a hands‑off leadership style, releasing early and often, and focusing on simplicity can dramatically improve code quality, product design, and overall project success in software development.
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.
This comprehensive guide, originally a white‑paper by Gene Kim, explains what DevOps is, how it differs from Agile, ITIL and visible ops, outlines its core principles, application domains, business value, and practical patterns for integrating security, QA, and continuous delivery into modern IT workflows.
