Agile
How to measure your team's velocity without gaming it
Velocity is one of the most used and most misused Scrum metrics. Understanding what it truly measures — and what it doesn't — is essential.
Read article →Blog
Thoughts on software development, UX, agility and the best practices of our craft.
Agile
How to improve your Daily Scrum in 5 steps
The Daily Scrum lasts between 5 and 15 minutes yet some teams dread it. Transforming it into a real synchronization tool rather than a status report changes everything.
Read article →
Agile
Sprint planning: making your estimates more reliable
Estimates in software development are notoriously imprecise — not through incompetence, but by nature. Here's how to structure Sprint Planning for more realistic commitments.
Read article →
Agile
Ideas to revitalize your Scrum retrospective
The retrospective is Scrum's most underestimated ceremony. Yet when done well, it can transform the entire dynamic of a team. Here's how to approach it differently.
Read article →
Agile
The 5 most common mistakes when adopting Scrum
Scrum is simple to understand, difficult to practice well. Many teams do 'Scrum-but' without realizing it and wonder why it doesn't work.
Read article →
Agile
OKR and Scrum: aligning strategy and execution
OKR and Scrum are two complementary tools operating at different levels. Well articulated, they create a bridge between company vision and teams' daily work.
Read article →
Agile
Estimating a software project: the difficult art of costing the unknown
Why is it so hard to give a fixed price for a software project? Because you're estimating the unknown. Here's how Scrum handles this honestly — and how to explain it to a client.
Read article →
Software Craftsmanship A
The Pomodoro Technique: taking back control of your attention
25 minutes of work, 5 minutes of break — then repeat. The Pomodoro Technique is one of the most effective and easiest time management methods to put into practice. Here's how to use it, which tools to choose, and why consistency is the real key.
Read article →
Agile
KPIs: why they're hard to get right and how the S.M.A.R.T principle helps
Defining good performance indicators is one of the most underestimated exercises in management. The S.M.A.R.T framework structures thinking — but doesn't replace understanding what you actually want to measure.
Read article →
Agile
The Scrum Master role: facilitator, not project manager
The Scrum Master is a facilitator whose goal is to remove obstacles blocking the team. A role often confused with project management, but one that requires radically different skills.
Read article →
Agile
The Quality / Cost / Deadline triangle: why you can't have it all
Fast, cheap, good quality: pick two. This iron triangle of project management is a reality every software project stakeholder must accept — and Scrum offers an elegant answer.
Read article →
Agile
The Product Owner role (PO)
The Product Owner is one of Scrum's three core roles. Their mission: maximise the business value of the product and the team's work. A demanding role, often misunderstood, that goes well beyond simple backlog management.
Read article →
Agile B
Lean Startup: why the method alone isn't enough
Lean Startup validates concepts with customers through iteration. But without a solid business model, it produces the same results as blind exploration. 93% of start-ups still fail.
Read article →
Agile
The Eisenhower Matrix: prioritising clearly between urgent and important
Not all tasks are equal. The Eisenhower Matrix offers a simple framework to distinguish what is urgent from what is important — and stop confusing the two.
Read article →
Agile
The Agile Manifesto — full text and commentary
Published in 2001, the Agile Manifesto fits in four values and twelve principles. Twelve years later, it remains the compass of every serious team. Here is the full text, with a few words on what it really means.
Read article →