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.
The article examines why traditional waterfall planning remains essential for banking software projects while selectively adopting agile practices, highlighting the differences between consumer‑focused (To C) products and business‑focused (To B) initiatives, the limits of MVP, and a hybrid delivery model that satisfies both speed and contractual certainty.
This article provides a detailed overview of JIRA and Confluence, explaining their core concepts, issue types, workflows, boards, release management, and integration features, and shows how they together enable decentralized, collaborative, transparent, and visual agile development practices.
The article explains how transitioning a waterfall‑style project to agile by breaking the work into user stories and using user‑story mapping can provide early feedback, improve continuous delivery, and resolve common pitfalls such as unclear requirements and integration challenges.
The article explains why rapid response is essential in modern software projects, critiques the drawbacks of waterfall development, and introduces agile practices such as short iterations, user stories, continuous integration, automated testing, and close collaboration to deliver value more efficiently.
This guide outlines project naming conventions and step‑by‑step instructions for creating a new Jenkins project, configuring build history, parameterized builds, triggers, Jenkinsfile, and how to build, view logs, and debug the pipeline, illustrated with screenshots.
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.
This article compares the traditional Waterfall development model with the Agile Scrum approach, outlining each method's strengths and weaknesses, describing Scrum roles and workflow, and offering practical insights on when and how to apply either model in software projects.
This translated article shares 42 practical lessons drawn from Mahesh Balakrishnan’s experience building a production database, covering customer focus, project management, design principles, observability, research, and strategic thinking to help engineers and managers create reliable, scalable infrastructure.
This article explains what bug tracking is, outlines a typical bug‑tracking workflow, describes the elements of a good bug report, lists criteria for choosing a bug‑tracking tool, and reviews twelve popular tools with their features, integrations, pricing, advantages and disadvantages, concluding with recommendations for teams of all sizes.
This article outlines common disruptive behaviors of "pig teammates" in project teams and provides concrete strategies—clarifying responsibilities, reducing conflicts, improving communication, confronting stubborn members, and motivating lax contributors—to help project managers maintain progress and team cohesion.
A senior IT leader’s frustration with a middle‑platform project reveals how vague goals, insufficient budgeting, lack of real business scenarios, and misaligned expectations between management and consultants can doom enterprise transformation initiatives, offering hard‑earned lessons for future R&D managers.
This article outlines ten essential components of project management—including overall management, scope, schedule, cost, quality, resources, communication, risk, procurement, and integration—while providing practical tips, stakeholder analysis methods, and visual guides to help teams execute projects efficiently.
The article outlines three developmental stages for engineers—from merely implementing PRD specifications, to understanding business and selecting appropriate technical solutions, and finally proactively contributing business ideas—while describing practical methods for demand exploration, project initiation, management, and data‑driven iteration within a mobile development context.
This article explains the differences between remote and distributed software teams, outlines the advantages of a distributed model, and provides practical strategies, tools, and communication techniques for effectively coordinating and leading large, multi‑location development projects.
A project manager recounts how poor quality focus, insufficient team oversight, lack of design, uncontrolled requirement changes, and missing code reviews led to a disastrous rollout, and shares the corrective actions and key lessons to avoid similar failures in future software projects.
This article presents a detailed case study of a mid‑size development team’s front‑end and back‑end technology stack, server environment, project workflow, and management practices, aiming to share practical solutions and lessons learned for building and maintaining enterprise‑grade Java applications.
The article details Rust’s recent governance overhaul, introducing a new Leadership Council that replaces the core team, outlines its responsibilities, lists its inaugural members, and discusses the broader implications of the community’s shift away from a centralized leadership model.
This article reviews the lack of a standard Python project structure and compares four popular scaffolding and build tools—Cookiecutter, PyScaffold, PyBuilder, and Poetry—detailing their installation, generated directory layouts, and typical make/ tox/ poetry commands for testing, documentation, and packaging.
This article explains how AOV (Activity on Vertex) and AOE (Activity on Edge) networks model task dependencies and durations, showing practical examples for course scheduling and construction project management, and demonstrates topological sorting and critical‑path analysis to create clear, conflict‑free schedules.