Last week we finished our first sprint! It has been an exciting and interesting three weeks. In this post, we will update you with all the things that have happened since the ROEF festival. Besides that, we will explain what we are planning to do in the second sprint.
In the past three weeks we got insights through different events. After the ROEF festival, we started to prepare for the Global Goals Jam. The Scream application was tested for the first time at this event.We thought that the Global Goals Jam would be the perfect moment for us to get insights about how people react to a chatbot. That is why we prepared a chatbot simulation. We added our chatbot simulation to the Slack-channel of two Global Goals teams.
More information about the Global Goals Jam can be found here.
Insights Global Goals Jam:
At the Global Goals Jam we found out that there were some difficulties concerning the use of the Scream application and Slack.
- Technical difficulties
- Usability difficulties
- Time & space difficulties
These difficulties made it hard for the participants to actually use Scream and Slack. Therefore our chatbot simulation was not used by the participants.
This insight changed our initial planning. We now had to reschedule the ending of our first sprint. That is when we tried to really figure out “what is Scream?”.
On the 27th of September we had a Visual Thinking workshop. This method helped us to define our problem and gain a better understanding of Scream. We used this visualization to explain our vision to our product owner at the partner review on the 29th of September.
Insights Partner Review:
We explained to our product owner that we thought that it would be hard to add a chatbot to an platform that is not “mature” yet. He understood our perspective and we started to discuss different directions for our project. We decided to focus on DOCUMENTATION, because this is the crucial step to prevent design waste according to the Scream method. We realized that choosing this challenge is going to be complex, because it has a lot of facets. Even so, we find this challenge very interesting and we think overcoming this challenge would contribute to the Scream method.
In the second sprint we investigate more thoroughly who the actual user of Scream is. Besides that, how do these users document their process (if, how, why, when)? Sharing is an important part of preventing design waste as well. Therefor we need to find out how and if we can motivate teams to share their process with the world.
Our next post will hopefully provide you with more insights about these topics!