Scrum and Presentation Design – Part 2: Vision, Constraints and User Stories

Welcome to the second post in a multi-part series discussing the application of Scrum to Presentation Design. 

Read the first part here.

Step 1


The first step when starting a software development project using Scrum is the project vision. Why are we developing this product or service.

When designing a presentation the first step is exactly the same. Why are we designing this presentation. What is the purpose. If you don’t know the answer to this, you probably shouldn’t do it. You must have a vision. Some examples could be:

  • Changing people’s risk perception about investing in real estate.
  • Change people’s recycling habits.
  • Convince people to stop buying bottled water.
  • Inform people about the dire situation of the company’s financials.

These are all examples of why. Why are you doing this presentation.


Another part of step one of the Scrum framework as described in part 1 is project constraints. There are three types of constraints; time, money and scope.

A presentation design project has those exact same constraints.

  • Time – we have a firm deadline we need to meet because that is when we are scheduled to present or that is when our client is scheduled to present.
  • Money – we only have a certain amount of money to spend on the design. Maybe we can’t buy all the stock photos we want. Maybe we can’t hire that graphic designer to help us out.
  • Scope – We only have 5 minutes for our presentation. We can only use 10 slides.

These three are in balance. You can’t research everything (scope) if you only have 1 week to prepare the presentation (time). If you have a limited budget you may have to reduce the scope of your project to afford high quality stock photos for the points you want to make. Or if you have a limited budget you may need more time to prepare because you have to create your own illustrations instead of buying them.

The point here is that it is important to know what constraints your project faces so you can plan correctly.

Step 2

User Stories

The second step in the Scrum framework is creating something called user stories. This is a way for us to put ourselves in our user’s shoes and view the product or service from their angle. A user story goes something like this: As a <user> I would like to <action>, so that <value>. Of course, we must swap out <user>, <action> and <value>. To be able to do this we must know who our user is, what they like to do and what they value. For example, as a working mom I would like to turn on the washing machine remotely, so that it is done when I get home and I don’t have to worry about it having more time to spend with the kids.

Applying this to presentation design is basically the same as know your audience. We must know who our <user> is, our audience members, what they like to do and what they value. This will help us tailor our presentation to our audience. It will determine what images to use, what colors to use, what words to chose, what to wear etc. Depending on who you are presenting to this might all be different. Since we are presenting for the audience we must put ourselves in their shoes to be able to see things from their point of view so we can provide them the most value.

In a presentation with the vision “Convince people to stop buying bottled water” we may be speaking to a group of high-school students in an environmental class. We could have a user story or audience story like this: As a high-school student I would like to make my parents stop buying bottled water, so that I can help protect the environment.

Now, what does that mean for your presentation. First, remember that you may have many different user stories and you must prioritize them. The story that fits the largest number of your audience would probably be on top. Back to our story, if a large group of the audience felt the same then you might want to make sure you talk about how to convince other people to stop buying/drinking bottled water, some easy and good arguments they can remember and how to address objections.


By applying parts of the Scrum framework to presentation design we have seen how important it is to start out with a vision. Knowing why you are giving/designing the presentation. We have also seen how important it is to know the project constraints to plan the work correctly and finally how important it is to know who your audience is and how you can best connect with them.

Stay tuned for part 3…

Leave a Reply

Your email address will not be published. Required fields are marked *