Developer: “I’m not sure when the next Sprint planning is. The ScrumMaster hasn’t scheduled it yet” Two things concern me here. First, the seemingly variability of events. Second, the reliance on the ScrumMaster. In Scrum, we work on a cadence. Once we determine the Sprint length, we mostly stick to it with a few exceptions around…
Developers on Scrum teams split their time across 3 main areas each and every Sprint. Building the Product Increment During the Sprint, Developers work on Product Backlog Items that help accomplish the Sprint Goal and deliver a Product Increment. Developers on a Scrum team build the Product Increment. That is their main accountability. This involves all…
Scrum Master: “Team, the last Sprint was a colossal failure.” So when can a Sprint be considered a failure? Let us start by defining what does failure mean in this situation? Is it about the team's velocity being low? Is it the team not completing all the Product Backlog Items they took on in Sprint Planning?…
Many teams adopt Scrum but still approach development the same old way. Build widget A in Sprint 1, build B in Sprint 2, and build C in Sprint 3, and in Sprint 4, we put A+B+C together. In Scrum, a Product Increment is whatever you previously built, plus anything new you built in this last Sprint…
Scrum Master: “Team, tomorrow's daily Scrum has been canceled as I have a doctor appointment and I can't be there to run the meeting.” A statement like this indicates a misunderstanding of the purpose of the Daily Scrum, the role of the ScrumMaster as well as the importance of sticking to a cadence. A common misconception…
Agile technical coaching is about helping teams adopt agile engineering practices that are essential to succeeding with Scrum. These practices help teams and organizations realize the benefits of Scrum, like faster time to market, faster return on investment, reduced risk, improved quality, and increased adaptiveness to be able to quickly respond to changing requirements and changing…
New to Agile and Scrum? Learn the fundamentals of Scrum covering Scrum theory values, Scrum roles, Scrum events, and Scrum artifacts by watching this 14 part video series based on the Scrum Alliance® Scrum Foundations Learning Objectives that are aligned with the Scrum Guide. Watch the video series here.
Business Analyst: "I am a BA on the Scrum team and I'm responsible for writing the user stories." This is another common statement I usually hear from business analysts. Check out the previous post on the who of product backlog refinement that clarifies the responsibility of the business analysts and the rest of the Scrum team.
Agile Engineering practices are essential for succeeding with Scrum and ensuring that teams are capable of delivering a Product Increment at the end of every Sprint. Let’s walk through an 8 step approach to guide your team to adopt these practices and make them easier to learn and apply. Some of these steps you’ll be able…
Executive: “Of course we are agile, everyone is using Jira now!” A tool does not make you, your team, or organization Agile. I see many organization invest in tooling without investing in proper training and coaching. Our first Agile value is about focusing on individual and interactions over processes and tools. So, any tool we do…