AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Define session demo2/17/2024 ![]() It's important to note that sprint demos aren't something the team should timebox. Each developer shows off their work, answers any questions the stakeholders have, then cedes the floor to the next developer on the team. The next developer takes over and presents the changes that they've finished. Once the conversation around a feature or bug fix finishes, the team moves on to the next item. Each sprint builds on the last, and the software continues getting better. Those new ideas about the software feed back into the scrum process. This conversation about new features helps to spark ideas from the stakeholders about what the next step should be. The goal of both the scrum team and the stakeholders is to build the best software they can. ![]() Instead, holding a sprint demo is a chance for developers and stakeholders to be in conversation with one another about new code. They're not just opportunities for the team to show off their work or prove that they're actually doing something all day. This is why sprint demos are so valuable. Successful scrum teams develop software iteratively, building on previous work little by little and constantly improving. These questions are an opportunity for stakeholders to identify the next development steps for the project. Then, once a developer has provided a quick walk-through of all the user-facing parts of their work, stakeholders ask questions. Additionally, this is a chance for a developer to show off what they've done. They're the ones who worked on that software they know how it works the best. When sprint demos are at their best, they're a collaborative event where both developers and stakeholders talk about the new software.Ī developer starts by demonstrating some new feature that they've completed during the sprint. Some teams will identify a person who actually performs the software demonstration, but this isn't ideal. The best demos are performed by the team as a whole. Figure: How sprint demos fit into the agile product development process The team demonstrates fixed bugs, new features, and infrastructure necessary for future work. Stakeholders and developers alike are coming together to share in the work they've accomplished. The work that they've done is important, and you want to share it with the people who are most excited about it. Many teams aren't able to complete all their agreed-upon work in every sprint, but that's the target each team should aim for.Ī sprint demo is your team's chance to show off to the business stakeholders. Ideally, by the time the end of the sprint arrives, the team has finished all the work. Once the team agrees with project stakeholders on the work to be completed, they bear down and write code. The important thing to understand is that a sprint is a well-defined block of time with a well-defined work commitment attached. Other teams choose one week, and I've even seen a few that went as long as a month. That work is based on input from the project's stakeholders and ideally is the most important work the team could be doing for that sprint. At the start of an agile sprint, a team commits to a certain amount of work. In a traditional scrum method, the sprint demo comes at the end of a sprint. In this post, we're going to talk about the purpose that sprint demos serve to a team as part of a sprint review and how you can make sure yours provide value to your team and your business. And if you're not doing a good job with your sprint demos, it's easy to miss the value they bring. After all, a full development sprint is usually packed to the gills with things to do. It's understandable that teams sideline sprint demos. ![]() Over 85% of software developers are using agile software development methodologies (source: Stack Overflow’s annual Developer Survey) but one of the most commonly ignored ceremonies is the sprint demo. Many teams miss out on the value of these ceremonies and consider them nothing more than bothersome meetings. But it also comes with some ceremonies that can seem a bit opaque. ![]() And it reduces developer stress, enabling developers to do better work. It improves team velocity, shipping new features to customers more quickly. The scrum methodology provides many benefits to development teams.
0 Comments
Read More
Leave a Reply. |