Demonstrating and Validating the Sprint for Developers

The key outputs of a sprint in Agile software development are the deliverables. These are standalone features of a product that work on their own. Each sprint creates one or more deliverables that get showcased at the sprint review meeting. However, just creating the deliverables isn’t enough. After developers create deliverables in the sprint, they must demonstrate and validate the deliverables. While these terms may not seem to mean much on their own, they represent vital parts of the Agile software development process.


The definition of demonstrating is to, “clearly show the existence or truth of something by giving proof or evidence.” In the context of Agile software development, demonstrating refers to showing the existence of deliverables. Also, the demonstration shows how each deliverable feature works. This takes place in the sprint review meeting, held at the end of every sprint.

So what is a developer’s role in the demonstration process? First and foremost, developers create the deliverables. Without developers, there would be no software to show off in a sprint review meeting. Analysts can only go so far as to create specifications for how software should behave. Quality assurance technicians can make sure that features match how they were designed. Without the developers, though, there is no role to turn specifications into working software.

After developers have created the deliverables, it would seem that their role in the software development process is finished. However, they are still quite important in the demonstration phase. If questions come up in the sprint review meeting, developers are often most equipped to answer them. Other roles may know how the software was intended to behave. They may even be able to discuss what they’ve seen personally in testing. However, only developers who actively created the feature are properly able to address these concerns.

59 Seconds Agile - Demonstrating and Validating the Sprint

59 Seconds Agile – Demonstrating and Validating the Sprint


The verb validate is defined as, “to check or prove the validity or accuracy of something.” While it may sound similar to demonstrate, there are specific differences. Within Agile software development, validate refers to proving that completed deliverables match the original software request. Where demonstration shows what the scrum team and developers have accomplished, validation confirms that it is what stakeholders wanted. This gives stakeholders the opportunity to confirm that the new deliverables are what they asked for. Like the process of demonstration, validation occurs within the sprint review meeting at the end of every sprint.

Validation is a vital step in Agile software development because of the gap between stakeholders and development. A request changes hands several times before development begins. Stakeholders give their request to the Product Owner, who must pass the request through any authorization steps in an organization. As such, misunderstandings can make the finished deliverable vastly different from what stakeholders expected. By giving stakeholders a chance to voice their approval or rejection, they aren’t forced to receive software that fails to accomplish what they wanted.

Accept vs Reject

The core of the validation process is the acceptance or rejection of deliverables. For every deliverable that is included in a sprint review, stakeholders must decide to accept or reject the feature. This isn’t a time for fine-tuning and last minute adjustments, it is a single decision of whether the deliverable matches the request. If stakeholders have minor changes they would like to see in place, they can ask the developers to make these changes moving forward. If seeing the features in action changed stakeholders’ minds, they can put in new requests for those changes to be made later. A rejection is only applicable if the finished deliverable does not match what the stakeholders asked for. The Product Owner makes the final call on acceptance or rejection as the representative for the stakeholders.

Prev <— Continue Reading —> Next

Our Favourite Agile Books

Read Our Reviews

The History of Agile For Developers

Prior to the 1990’s software development was very slow, often taking years to complete development and release the product to market. The industry was following a very formal methodology for products and software development…

Read More

What is Agile to the Developer?

While traditional project management is still widely used, the benefits of an Agile approach to running a project are becoming more and more recognized. Where Agile has a distinct advantage over classic project management is the development of new products…

Read More

Why Use Agile as a Developer?

When determining if a move to Agile is right, a PESTLE can be used to simplify what factors should be considered. While Agile is sometimes thought of as a software development project management method, it isn’t just for these types of technology-centric companies…

Read More

The Agile Manifesto For Developers

Agile is a quick, simple, lightweight and effective way of managing projects. In traditional project management models…

Read More

The Agile Principles For Developers

When the Agile Manifesto was drawn up in 2001, it embodied four values and twelve principles that signaled a new approach to…

Read More

The Agile Fundamentals For Developers

Thinking of becoming a Scrum Master? Or are you already one, but you’re still new to the job? No matter what level of experience…

Read More

The Declaration of Interdependence For Developers

The Declaration of Interdependence establishes that all members, stakeholders, and customers are interdependent and…

Read More

The Agile Frameworks For Developers

There are many different Agile frameworks – all of them share the same philosophy and are built around the Agile Manifesto and Principles. But they vastly differ in their approaches, values, and structure. …

Read More

The Scrum Framework For Developers

The Agile Scrum framework is designed to deliver products and projects of any size. This includes projects, programs, and portfolios. Scrum provides guidelines on delivery techniques, events, and roles. Many of the same ceremonies are held within both a standard Agile scrum project and an Agile Scrum…

Read More

The Scrum Roles For Developers

Scrum is a useful tool for the creation, maintenance, plan, and execution of diverse products and services. The tool consists of…

Read More

The Scrum Team Size For Developers

The basics of Scrum can be easy but implementing them and succeeding with Scrum can be infinitely harder. Scrum …

Read More

The Agile Project Vision For Developers

At the heart of any great product is a great vision. It describes the primary goal or goals of a product and creates a focus that…

Read More

Forming the Scrum Team For Developers

Scrum is a framework that encourages delivery of potentially shippable product increments every 2-6 weeks. The work is…

Read More

Developing Epics For Developers

The term ‘epic’ in agile refers to a large user story that has not yet been defined in detail. Typically, an epic will cover a single…

Read More

The Agile Product Backlog For Developers

A Product Backlog is an organized collection of the existing User Stories (aka Wants and Needs) for an explicit business endeavor. Think of a shopping catalog of User Stories, ordered by urgency, that can be perused and selected from to determine what will be worked on during the current…

Read More

Release Planning For Developers

Although flexibility and adaptability are part and parcel of an agile methodology, this does not mean that no planning is required when…

Read More

Creating User Stories For Developers

User Stories are an integral part of the agile development process. They are an important agile technique that is used to frame…

Read More

Estimating User Stories For Developers

One of the principles of self-managing teams in Agile Scrum is working collaboratively with the Product Owner to effectively deliver…

Read More

Creating Tasks For Developers

According to The Agile Manifesto: “The best architectures, requirements, and designs emerge from self-organizing teams.” As a…

Read More

Estimating Agile Tasks For Developers

In Scrum, a list of user stories is produced and put together to form a product backlog, and each of these user stories will need to…

Read More

Creating the Sprint Backlog For Developers

The Sprint Backlog is defined as a group of user stories that are grouped together during the Sprint Planning Meeting. This…

Read More

Creating the Deliverables For Developers

Agile Scrum provides the framework for delivery of the vision of an organization. Execution of the vision includes processes, ceremonies and project deliverables that are also known as artifacts…

Read More

The Daily Stand-Up For Developers

The daily scrum is an opportunity for developers or anyone committed to working in the sprint to talk to each other to make sure the…

Read More

Product Backlog Prioritisation For Developers

The product backlog is a key element of Agile software development. It facilitates a development environment that creates valuable features and products for stakeholders…

Read More

The Sprint Review Meeting For Developers

The Sprint Review meeting comes at the end of the sprint and the goal of this meeting is to have key people in the room to be able …

Read More

Demonstrating and Validating the Sprint For Developers

As organizations migrate to Agile principles, there may be questions about how the organization can prove that there is value…

Read More

The Sprint Retrospective For Developers

A very simple step by step guide to help you choose the appropriate product development methodology from…

Read More

Releasing the Product For Developers

One of the most important milestones any project will ever have is finally releasing their product and putting it out there. It’s the…

Read More

Regression Testing For Developers

In companies using agile development, it is common to introduce changes in a product incrementally. Along with the new changes, unexpected issues may arise, testing whether the existing functionality is broken or not becomes very important…

Read More

Product Owners

Find out more about the Agile and the Product Owner Role

Read More


Find out more about the Agile and the Developer Role

Read More

More Articles

Read More

Chicken Appreciation Society

Translate »