Last time we planned the sprint. Now comes the second of the three questions: what are we working on right now? To answer that without a meeting, you ...
Your team is smart. They take estimating seriously. And the dates are still wrong, and the boss is still grumpy. It's not a skill problem. Here's the ...
Last time we turned a pile of 33 items into a real backlog. Now it's time to plan the next chunk of it. Which features go into the next sprint, and wh...
Planning, standup, refinement, review, retro... and somewhere in there you're supposed to write code. As a former Scrum trainer, you might expect me t...
Most backlogs are a pile. Features, bugs, and chores all mixed together, and you can't tell which is which. Issue types are how GitHub helps you sort ...
The last two posts were pretty heavy on theory. Now it's time to actually build something. We create a brand new GitHub project from scratch, fill it ...
If GitHub Projects and GitHub Issues have ever felt a little odd to you, there's a reason. The split between them grew out of GitHub's own success. On...
GitHub Projects will let you work just about any way you want, and that's exactly why so many teams end up with a very flexible mess. Before you confi...
A year ago I kept a wish list of things I hoped GitHub would add to Projects and Issues. Three out of four are done now. Here's what shipped, what it ...
If your team can't work on one thing at a time, that's not a process problem. It might mean your team isn't actually a team.