The Remaining Work field in Microsoft’s Azure Boards is usually talked about in the context of burndown charts. But if you are in a scrum master role and have more than a few developers on your team, you might find the Remaining Work field useful for helping you coordinate work. What Is “Remaining Work”? You […]
Since mid-March, my husband and I have been working from home full time; our two teenagers also began online schooling around that time. Like many households, we suddenly had to figure out how to maintain harmonious relationships while keeping the same levels of productivity. Influenced mostly by having to compete for office space and bandwidth, […]
Estimating work is helpful for managing teams and planning for the future. But working through every nuance to provide an estimate can cause frustration and be time-consuming.
I recently worked with a client who was extremely frustrated with deadlines that seemed to come from nowhere, made no sense to him, and didn’t fit with his idea of Scrum as a methodology. He believed that according to Agile/Scrum, “the business” was not allowed to give deadlines to development teams. Scrum, he believed, allowed […]
The sprint retrospective is one of the main Agile ceremonies. By definition, it is an opportunity for the team to reflect on the work completed over a short period of time and make changes. However important that may seem, eventually, you’ll consider canceling your team retros.
The daily stand-up meeting is an important component of the SCRUM process. It helps the whole team stay in-sync and up-to-date on what’s happening with the project, and it alerts everyone to blockers as soon as they become an issue. However, if you do a stand-up meeting wrong, it can become a real drag—and a […]
The demo is one of the most important aspects of the sprint ceremony. At this point, your client has already seen the visual design of new features, but this is their first chance to see features in action. I’ve been a part of some very successful feature demos, and some that haven’t gone so well. […]
So you have your product backlog chock-full of sprintable items. User stories, dev chores, a few bugs—all estimated, of course, right?!? Your team is ready to rock, so where do we start? We start with my favorite scrum thing: the Sprint Planning Meeting.
The best process is owned by its team, but everyone has to start somewhere. That’s why I drafted this, a template for Atomic Object’s Agile process. It’s designed to be a starting point for our maker teams as they come together to tackle a new project.
Developing complex custom software applications is difficult, even in ideal circumstances. In a Scrum workflow, it is desirable to have as few stories as possible in progress at any given time. This helps to maximize throughput and to ensure that multiple stories aren’t partially completed in a given sprint without points to show. Unfortunately, dividing up […]