git log --all
All posts
32 posts on Agile foundations, frameworks, roles and artifacts, newest first.
-
How to Eliminate Waste in Software Development: A Value Stream Mapping Guide
Find the waste in your software delivery with a value stream map: trace real work, measure wait and process time, name the waste and fix the biggest delay.
-
How to Implement DSDM: A Step-by-Step Guide
Implement DSDM on a real fixed-deadline project: staff the roles, run Feasibility and Foundations, build a MoSCoW list, plan timeboxes and protect the date.
-
How to Read a Burndown Chart: Patterns, Fixes and a Template
Set up a sprint burndown, capture the data daily, recognise the four common shapes, and act on what the chart shows before the sprint is lost.
-
The FDD Process: Feature-Driven Development's Five Processes, Step by Step
Run Feature-Driven Development's five processes on a real project: model, feature list, plan, design and build by feature, then track progress by milestone.
-
How to Write User Stories: Template and Examples
Write user stories that lead to the right software: a story template, Given/When/Then acceptance criteria, an INVEST checklist and five worked examples.
-
MoSCoW Prioritisation: A Working Guide with Templates
Run MoSCoW prioritisation that holds: define Must, estimate, run the workshop, keep Musts under 60% of effort and use it when time runs short.
-
Sprint Backlog Example and Template: Plan a Sprint Step by Step
Build a sprint backlog that holds up: work out capacity, write the Sprint Goal, pick the items, plan the work in day-sized tasks and adapt when things change.
-
How AI Coding Tools Change Agile, and What They Can't Fix
AI coding tools speed up implementation in Agile teams but leave the real constraints in place: vague requirements, weak user feedback and slow approvals.
-
Scrum Explained: Pillars, Accountabilities and Events
Scrum explained plainly: it doesn't create high-performing teams, it exposes underperformance. Here is what its pillars, accountabilities and events demand.
-
Scrum for Experienced Teams: Getting Past the Plateau
Experienced Scrum teams plateau when they measure velocity. Track sprint goal hit rate, flow and DORA metrics, run data-driven retros and make Done real.
-
Burndown Charts: How to Read Them Honestly
Burndown charts are optional in Scrum and useful only when read honestly. How to read the line, which chart fits which question, and how charts get gamed.
-
Definition of Done in Scrum: What It Should Contain
A Definition of Done only works when it is written down, shared and enforced at today's real standard. What a good DoD contains and how to fix a weak one.
-
Sprint Backlog in Scrum: A Plan Built Around the Sprint Goal
A sprint backlog is the Developers' plan for meeting the Sprint Goal. What it should contain, how to structure the board, and four problems that derail it.
-
Product Backlog in Agile: What It Is and How to Structure It
A product backlog is an ordered decision about what to build next, anchored to a Product Goal. How to structure it, refine the top and delete the rest.
-
User Stories in Agile: The 3 C's, INVEST and Story Maps
User stories are prompts for a conversation, and the card matters less than the talk. How to use the 3 C's, INVEST and story mapping without writing specs.
-
Stakeholders in Agile: Roles, Types, and How to Manage Them
Most Agile stakeholder problems come from unclear decision authority and absent users. Map who decides, bring real users in, and close the feedback loop.
-
Agile Coach Role: What Good Coaching Leaves Behind
A good Agile coach builds capability that lasts after they leave. Judge one by what persists, by outcomes agreed up front, and by their work beyond the team.
-
Agile Development Teams: What Self-Management Really Takes
A self-managing agile development team decides who does what, when and how, yet still needs clear goals, constraints and organizational support to work well.
-
The Scrum Master Role: What the Job Description Misses
A good Scrum Master removes organizational impediments, coaches rather than advises, and builds a team that needs them less each year. Most job ads miss it.
-
The Product Owner: Decision-Maker, Not Backlog Admin
Most Product Owners administer a backlog instead of making product decisions. The role means prioritizing against stakeholders, saying no and staying available.
-
Disciplined Agile (DA): A Toolkit for Experienced Teams
Disciplined Agile is a toolkit of process goals, not a process. It suits experienced teams in varied contexts and tends to overwhelm teams new to Agile.
-
Large-Scale Scrum (LeSS): Feature Teams and When to Use It
LeSS scales Scrum by removing structure: one Product Owner, one backlog, feature teams. It is simpler than SAFe but demands far more organizational change.
-
Lean and Agile Practices in Daily Life: What Actually Works
Lean and agile practices work in daily life when you keep the feedback loops: a weekly review, one protected priority, WIP limits and a monthly retrospective.
-
Scaled Agile Framework (SAFe): When It Helps, When It Hurts
SAFe is enterprise change management in Agile clothes. It earns its overhead with 8+ dependent teams and slows smaller ones down. Start with three practices.
-
DSDM Explained: Fixed Deadlines, Flexible Scope and MoSCoW
DSDM fixes the deadline and flexes scope with MoSCoW prioritisation. It suits hard deadlines with engaged sponsors and fails when no one can make scope calls.
-
Feature-Driven Development (FDD): Agile for Large Teams
Feature-Driven Development (FDD) gives large teams on complex, stable domains a domain model, a feature list and chief programmers. Small teams rarely need it.
-
Lean Software Development: 7 Principles, Applied Honestly
Lean software development's seven principles are a diagnostic tool. Most teams waste effort on half-finished work, unneeded features and local optimization.
-
Extreme Programming (XP): The Agile Method for Code Quality
Extreme Programming (XP) is the Agile method about writing code well. Its TDD, pairing and continuous integration pay off even if you never adopt XP as a whole.
-
Kanban Explained: Why WIP Limits Matter More Than the Board
Kanban is a system for managing flow, and WIP limits are what make it work. Without them you just have a task board. How to set limits and track cycle time.
-
Agile Manifesto and Principles: Values, Not a Process
The Agile Manifesto sets out four values and twelve principles. Most organizations copy the rituals and skip the values; use it as a diagnostic for your team.
-
Agile vs Traditional Methodologies: Which Fits Your Project?
Agile vs traditional methodologies: Waterfall suits stable, regulated, fixed-scope work, but Agile wins for most software if your organization will change.
-
The History of Agile: From Toyota to Cargo Cult Agile
The history of Agile, from Toyota and iterative development to the 2001 Manifesto. The values held up; certification and cargo cult adoption diluted the brand.