Prioritising the Climasmart Release Plan

Prioritising the Product Backlog Items

The Climasmart website is our deliverable for the DSA minor project I worked on with Team 2. Here is how we got started.

We started by brainstorming as many possibilities as we could come up with for user stories and then selected the key user stories to include in the Product Backlog for the Climasmart website. We reviewed each user story to determine the order of priority from the point of view of the user. We decided that user story 1 is the first step and requires developing the basic website first, with a strong focus on the front end and design and in order to convey value to the client, this would start with wireframes and workflows.

Next, we identified what the website will need to enable the user to do, we concluded that the process of interacting with the website should be divided into four energy categories. This provides the possibility to develop potentially shippable product incrementally, beginning with Transport (or other) and following on with Waste & Recycling, Energy, Lifestyle. For example, while planning the first Sprint we may conclude that it will not be possible to complete the development of all four energy sections and together with the client we will be able to identify which of the four would provide the most value to the user on its own, or possibly conclude that all four must be released at the same time.




Although allowing the user to connect to their social networks is important functionality we concluded that it is most important that once the user starts using data the site generates it should be very easy to find, interpret and compare progress from previous periods since starting to use the site. For this reason, we placed Visual Indication and Historical Data as priorities 6 & 7, immediately after the four main energy types (2,3,4 & 5) and before the social network integration (8,9,10). When we later elaborated on the actual Release Plan we concluded that this prioritisation could be optimised further.
According to the Backlog at this point of the project the user will have a functional solution for evaluating and monitoring their carbon footprint.

The next phase will focus on enabling the user to improve by means of suggestions and recommendations about how to make smarter choices.
Once the user has been fully enabled to achieve positive results we will introduce social networking so each user is not only improving their own carbon footprint, but is also equipped to actively promote the concept of carbon footprint and climate awareness in their social circle.



Prioritising the Sprint Backlog Items and Release Plan

After reviewing and discussing the Product Backlog with the Product owner it was decided that priority should be given to producing the first of the four data categories and the Transport category was deemed to be the most interesting for the end user to begin with and the most logical choice which would enable us to produce potentially shippable products in sprints 2,3,4,5.
Having decided that we would aim to produce a Potentially Shippable Product by the end of Sprint 2 which would be a functional website that would gather and elaborate data on the Transport category, it then emerged that providing this data alone would not be optimal, and the decision was made to proceed with and prioritise the following:

● Connecting to social networks
● Historical data
● Recommendations and finding people on Facebook that live nearby

This decision is believed to add more value to the end user by allowing them to fully engage with the website and begin informing and promoting the App to their friends and local community regarding their Carbon Footprint in the Transport category.



During Sprints 3, 4 and 5 for the remaining three categories we will then repeat the following development items for one category at a time;

● Simple Visual Indication with additional data
● Historical Data with additional data

This means that the website functionality in terms of data provided would increase incrementally through Sprints 3,4,5, while all other functionality would already be initiated by the end of Sprint 2. This is a good example of how we can add value to the end user and the client by producing potentially shippable products earlier as we progress through the Agile process.

Related: UX & Responsive Design