Sprint Demos can often feel procedural in nature. Every few weeks the software team shows off the functionality they've completed, much of which has been specified by business team's requirements and built in concert with the solutions team. If everyone is already familiar with the work, why even have the demo?
Here are the top 3 reasons you can NOT afford to skip that Sprint Demo!
1. Rectifying Assumptions
Interacting with prospects & customers every day, the business team is constantly selling upcoming products & features - but until the software is completed, everyone will have their own interpretation of how it will look and function. This is natural, as software is complex to build and even nearly impossible to fully specify in advance.
To drive this point, I always ask the same question. "What are the chances you could recreate a painting on on my wall using only the description I give you (as in, without seeing it)?" Even after a few hours of describing the object painted and detailing each brush stroke, we would still have a near-zero shot at getting even just the colors right!
If you've ever written a software specification, you will no doubt feel overwhelming pride at the balance of detail and conciseness you've achieved... right up till the moment an engineer asks a question so basic that it exposes a set of assumptions you didn't realize you never wrote down. "Sure, I can make the painting you describe, no problem! Quick question - was the sky light blue, or dark blue? Was it cloudy that day?"
Damn! After hours of detailing the image, how could we forget to aptly define such a large piece of the puzzle as the background sky?! The Sprint Demo is the earliest time for your team to sit in a room together and identify (+ rectify) all these assumptions.
2. Team Chemistry
Software teams are often segmented away from the business teams - one is decidedly inward focused while the other is the opposite. While both teams connect over the shared mission of creating world-class experiences for their customers, the software team almost never interacts with customers directly! Bringing both teams together and collaborating over the products they will collectively create is a critical aspect of the Sprint Demo.
Additionally, software teams are naturally focused inwards and can get jaded on the exciting business developments and hard work other people in the organization are putting in. Getting everyone on the same page every few weeks fosters a strong team chemistry across vastly opposite disciplines. And of course, improving multi-disciplinary communication pays exponential dividends as the team traverses deeper and deeper down the product roadmap. There's nothing that helps chemistry like normalizing difficult discussions and humanizing your teammates!
Sprint Demos also boost the chemistry within the software team itself! Software teams are graded as... well... a team! While individuals present their own work, the success of all Sprint Goals as a whole is what the business team is seeing and evaluating. This evaluation as a team creates a strong sense of shared responsibility and accountability for Sprint Goals, and once again reinforces a common mission and positive team chemistry.
3. Vertical and Horizontal Visibility
Ever had the feeling that the work you are doing will not be recognized by your company? As a software engineer buried deep in an org chart, the Sprint Demo is one chance you get to publicly present the work you've completed, make your impact known, and share your personality! Most startup cultures believe in "flattened" org chart, but how many actually promote open & direct communication between engineers and stakeholders?
If you don't know who the power players are within your software team, the Sprint demo will quickly become your best friend as you try to break down the barriers between you and the core contributors to your business. These regular presentations force clarity of thought, and sharing perspectives gives both teams immense insight into the details and challenges of the shared mission. Most importantly insight from the other half of the shared mission - the one that they don't work on every day! Sprint Demos help you evaluate your team for leadership positions, technical strengths, and communication skills on a regular basis.
In summary, you can't skip that Sprint Demo because it's one of the basic building blocks of keeping your business and software teams rowing in the same direction. The business team sits between customers and the people making the software for the customers - shouldn't they be in the room as early and often as makes sense? Intro the Sprint Demo - the earliest moment at which any functionality can be considered "ready for use" by customers. Plus, as discussed above, homogenizing teams and humanizing each other (more than words in an email or bug ticket!) is what builds great cohesive cultures.
Do you love or hate your team's Sprint Demos? What are some of the reasons you think they're necessary, and what are the common pitfalls you see? Smash the button below to hit my inbox directly!
