Feedback Demo Sprint 2

Today we had a Demo from Sprint 2 for our product owner Boris Slaghuis.

In the presentation, we told everyone what research we did and what we tested. We have also shown our style sheet and 3D model of our installation.

We agreed with the teachers that we are a little bit behind on the schedule.

WhatsApp Image 2019-06-03 at 15.49.50

Teachers feedback:

  • no target group and sponsors yet
  • we have to do more technical things
  • we must already have prototypes and tests
  • we must have a more detailed vision

Research & analysis: Still a lot of work to do until getting a finished idea to work

Conceptualizing: Still unclear on how it’s going to work, to be used and to be build

Design & Prototyping:   Need more work (efficiently) on prototype and design

Design & Realization: Need more work

Testing & Implementation: not yet

Technical Knowledge & Analysis: not yet

Entrepreneurial Skills: Still without a target group and sponsors

This presentation and opinions received after it is something we can work on for the next weeks.  It is going to be a lot of work.

We have to go to the more technical parts of the project, find the sponsor and the target group. I think that everyone will be mobilized, it should be good.

@appleflapjc @burdetiadrian8 @izabelatyprowicz @oyvindknustadgmailcom @uselessmarkies @ruhrexp

Paper Prototype test video

https://drive.google.com/open?id=1PtH3MPWYXQ7cE5peWEiXRuawgYytDpoq

Izabella filmed the paper prototype test that we did with Alexandra Danila. I edited those clips into a video found in the link above.

@burdetiadrian8 @izabelatyprowicz @appleflapjc @oyvindknustadgmailcom @uselessmarkies @ruhrexp

Prototype Testing

We tested the paper prototype. It didn’t go as well as we hoped. We should have practised doing the drum sounds. We mimicked the sounds the drum module will make with our mounths and looped it using an app. This was the part where we need some practice. We did get some useful feedback from our test subject however. We will use this feedback for our second prototype and for our final installation as well.

 

@appleflapjc

@izabelatyprowicz

@oyvindknustadgmailcom

@uselessmarkies

@ruhrexp

Design Document – Feedback

IMG_3975

We received the following feedback about the Design Document:

Concept description:

  • Don’t get too technical about it yet
  • Everyone, without technical knowledge, should understand this

Moscow method:

  • What are these used for?
  • Speakers for what kind of sounds?
  • How many displays?
  • Focus on functionality!

Concept sketches:

  • Don’t put old iterations in here.
  • We want to give a clear image of what’s being built in the first part of the document.

List of requirements:

Performance: 

  • Be more specific of the specs of the installation
  • In what kind of timeframe are people using this?

Life in service:

  • Keep in mind that kids can bash our installation too!

Target product cost:

  • Doesn’t say anything
  • We should DEFINE “Very low”

Transport:

  • Same as “target product cost”
  • HOW do we transport this and DEFINE “easy”

Size and weight:  

  • Put some things in here
  • It doesn’t have to be accurate YET

Customer Journey Map:

  • It looks complete
  • We need more possibilities to find the installation. (flyers, social media, etc.)
  • We need more entry points! (currently, it has 2)
  • Maybe make it more graphical!?
  • What is a success? The endpoint? Measurable success? HOW do we measure that? (coupons? forms?) Define “success”.

Morphological Chart:

  • Put images in here
  • Don’t limit yourself to the hardware
  • ONLY THINK ABOUT THE FUNCTIONALITY FIRST

State diagram:

1st diagram:

  • Think about how to turn it on
  • (distance sensors?)
  • The black dot represents the US turning the thing on. We shouldn’t be touching the thing after that

2nd diagram:

  • Attraction Mode
  • And play should be somewhere else
  • Loop button is not a state

Deployment Diagram:

  • Where is the computer?
  • This should tell us, where do we use and what

@appleflapjc @izabelatyprowicz @oyvindknustadgmailcom @uselessmarkies @ruhrexp

 

 

Product Owner Consultations – Feedback

61454704_186883358893579_777085808640262144_n

Today we had a meeting with the Product Owner – Boris Slaghuis.

This is the feedback that we’ve received:
  • Our target audience is too small if we promote music schools and music stores.
  • Focus more on concert halls.
  • Broaden the pool with Festival goers
  • There are a lot of themed festivals in Enschede, we can get a broader audience by promoting those.
  • Focus more on main events that attract more people
  • work more on attracting more people to the city
  • Check the document about the target group.
  • we should work on prototypes and testing our installation to know how it will work in reality
  • With all the different festival themes we can make it a universal installation.
  • we should work on promoting the city
  • the target group is the target group the people of Enschede/ city, not the store
  • we should test what people like
  • the idea is really cool but it doesn’t attract people and target group
  • why we are using the music?
  • the idea of the planets was already a good idea

@appleflapjc @burdetiadrian8 @izabelatyprowicz @oyvindknustadgmailcom @ruhrexp

 

Client presentation

On monday 20th may we had to present our concept to our clients in a 5 minutes pitch. Thom did a really good job sharing our idea and they ended up liking it, giving us valuable feedback in return.

One of the things they said is that we have to find a better solution so that our installation gives value to the city of Enschede. We explained that in our vision each planet represents a different important location in Enschede. They gave us a better alternative which is to tie our idea to music centers( music schools, orchestras etc) around Enschede.

@burdetiadrian8 @izabelatyprowicz @appleflapjc @ruhrexp @oyvindknustadgmailcom @uselessmarkies

New tasks and responsibilities

Today we all met to talk about what we have to do in the near future and to assign tasks to us.
We put all the tasks on vivifyscrum on our board so that we can remember everything and let everything be clear. We also assigned points and shared responsibilities.

This is how our board looks like:
hmg

60974663_414102012520801_2955860050033246208_n

We talked about the concepts with the consult teachers, who were excited about our concept. They gave us also feedback about stuff were we have to think about, or tips too look at.


We also had a Guest  Lecture with Heinze Havinga & Mark Melenhorst.

We get important information and inspiration on how to measure the value of our experience.

I think that these meetings were beneficial, helped us a little, they led us in the right direction and inspired us. Then we had the opportunity to ask questions to the student in the third year. I think it was helpful for us.

 

@izabelatyprowicz @appleflapjc @burdetiadrian8 @oyvindknustadgmailcom @uselessmarkies @ruhrexp