<< Retrospective After Every Sprint | Series Home | Clearly defined Product Owner / PO has a product backlog >> The core concept behind timeboxed iterations is that, every sprint, the team delivers running, tested features. So every two weeks, the team gets together and should be able to demo the features they built to…
Category: General
ScrumBut – Part 5 – Retrospective after every sprint
<< Sprint Planning Meetings / Sprint Backlog | Series Home | Demo Happens After Every Sprint >> When you think about the hardest part of Scrum, it isn’t the daily stand-ups. Nor the sprint backlog. Not even the demos at the end. The hardest part – and the oft missed part – is “Inspect and…
ScrumBut – Part 4 – Sprint Planning Meetings / Sprint Backlog
<< Daily Scrum | Series Home | Retrospective After Every Sprint >> Ah, the Sprint Backlog. While not quite as visible as the Daily Scrum, the Sprint Backlog makes up the core trifecta of Scrum. And what developer wouldn’t love it? Every two weeks (or four weeks, or whatever iteration length you have) we’ll get…
ScrumBut – Part 3 – Daily Scrum
<< Team Members Sit Together | Series Home | Sprint Planning Meetings / Sprint Backlog >> The most visible – and often most abused – part of Scrum is the Daily Scrum, also known as the “Stand-Up”. In this meeting, the whole team meets with the participants answering three questions: What did I do yesterday?…
ScrumBut – Part 2 – Team members sit together
<< Timeboxed Iterations | Series Home | Daily Scrum >> One of the realities of many corporate environments is that you work with a group of people called a “team” but a variety of factors prevent you from actually sitting together. At Alistair Cockburn’s keynote presentation (PPT) at Agile 2009, he showed an interesting slide…
ScrumBut – Part 1 – Timeboxed Iterations
<< Introduction | Series Home | Team Members Sit Together >> Perhaps the very first and most widely “adapted” practice in the Scrum world is that of the timeboxed iteration. Henrik’s Scrum Checklist identifies four subareas of concern: Iteration Length 4 weeks or less Always end on time Team not disrupted or controlled by outsiders…
ScrumBut – Part 0 – Introduction
Series Home | Timeboxed Iterations >> Last week, Jurgen Appelo wrote an article called Scrumbuts are the best part of Scrum. I followed up with my Scrumbuts are the downfall of Agile post. Ultimately Jurgen and I are in agreement – it is important to be able to have the maturity to modify a process…
ScrumButs are the downfall of agile
I normally am in good agreement with Jurgen, but not in with his new article. The ScrumBut Ken argues against aren’t targeted towards mature agile teams. The fundamental problem we have – in Scrum, in XP, in Crystal – is that teams don’t want to even *try* the practices. “There’s no way I can sit…
Supporting Corey Haines
Right now my good friend Corey Haines has a Pledgie campaign going to help him continue his pair programming tour. Some people may question why they should donate to something like this. After all, their are tons of tales in the software industry about people making it big in short amounts of time. Further, I’ve…
Software Craftsmanship in the Enterprise
On Wednesday I had the absolute pleasure of speaking at the first Software Craftsmanship North America conference in Chicago. I gave a talk entitled “Software Craftsmanship in the Enterprise” which covered the issues surrounding development in the enterprise today, and the steps necessary and both an organizational and individual level to adopt it in your…