You're all fired up about embracing agile software development and ready to build the ideal Scrum development team, but you’re not sure where to start. You might ask, "What is the perfect mix of team members needed to create my Super Scrum Development Team?"
As you build your Scrum toolkit, there are a few fundamental elements that are helpful for you and your team to understand on the path to developing an effective Scrum discipline. Scrum artifacts are the basic building blocks that allow you to plan, organize, and track the progress of your work.
I’ve found that the primary challenge in building software is, above all else, a communication problem. Someone needs to dream up what an application needs to do, and others need to build and test it. If there are communication issues along the way, that’s going to cost time.
Agile vs. Scrum. Scrum vs. agile. You hear them used almost interchangeably in the software industry. But are they really the same thing? If not, what characteristics set them apart?
I’ve talked about how Scrum leads to efficient, high performance teams a few times before.
And I’ve shared what organizations need to do to embrace agile development and Scrum.
But today I want to discuss something near and dear to my heart: the immense importance of your daily Scrum practices. Land these daily Scrum routines and you’ll be sure to rock your next sprint.
Some meetings are necessary. Others...aren’t.
You’ve probably attended both kinds of meetings at one time or another – eagerly participating in the former and suffering through the latter. Yet even effective meetings often devolve into repetition, circular discussion, and chit-chat.
Scrum ceremonies were designed to avoid all that. Since a Scrum team’s goal is to produce the highest business value in the shortest time, unnecessarily long meetings can kill their efficiency. For this reason, Scrum replaces “meetings” with highly effective and structured “ceremonies.”