0 views collected around this technical thread.
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.
This article explains the concept of time boxes in Scrum, lists the common Scrum events and their recommended durations, discusses the advantages of fixed‑length meetings, offers guidance on handling overruns, and provides advice on selecting appropriate time‑box lengths while noting a related DevOps hackathon.
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.
This article shares a software team’s experience of shortening release cycles from two‑week to one‑week sprints, the quality challenges encountered, the root causes of instability, and the practical process improvements—including stable release branches, extended testing windows, and holiday moratoriums—that restored service reliability.
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 how agile teams can plan and track work using iterations or sprints, outlines the benefits of iteration planning, provides step-by-step guidance for creating iteration plans, and demonstrates how to configure iterations in TFS to manage tasks effectively.
The author recounts a four‑week, self‑organized DevOps research sprint on Google’s agile practices, describing the challenges of remote teamwork, sprint planning, iterative deliverables, and the final presentation, while highlighting lessons learned about autonomy, communication, and outcome‑focused management.
This article recounts how a small, multi‑disciplinary channel development team applied a customized Kanban‑based agile process to overcome tight schedules, heavy workloads, and a critical three‑day emergency feature request, demonstrating both the strengths and limits of agile in fast‑changing environments.