Exercise two reflections
Today we got a lot done, brainstormed a bit and it seems even computer scientist can be very creative if they put their minds to it. We have created two personas and had different ideas about them, and they keep changing, we are wondering how to make it fun, but yet a useful persona for the purpose of our project.
From a group perspective we are learning to get along fine and we are dividing up the work very good, there was a bit of stress before the exam but now that is over. All and all the brainstorming process went very well, and group dynamics are great!
For this week we felt we are understanding the structure of the course better and so we are feeling better as well. This weeks exercise was clearer than the last one and everything just seems to be flowing at the moment. There is a bit to write this week, but it's nothing the four of us can't do.
The theory behind creating our personas and scenarios are fundamentals to our design according to Bodker(p.409 in the book) and can be pinpointed into four roles:
1. A basis for the overall design.
2. For technical implementation.
3. As a means of cooperation within design teams.
4. As a means of cooperation across professional boundaries, i.e as a basis of communcation in a multidisciplinary team.
For us, the three first roles are relevant, and we will see how it goes next week!
Moreover, Carrol claims that a scenario is an 'informal narrative description' and allows us to tell a story and define a problem within the story, as a means to achieve concrete design and at the same time brainstorm for innovation. It is also naturally a good way to define, iterate, and go through the design process once again, it simply helps the group grasp what problem it pragmatically is trying to solve, and what consequences can arise.
The theory behind creating our personas and scenarios are fundamentals to our design according to Bodker(p.409 in the book) and can be pinpointed into four roles:
1. A basis for the overall design.
2. For technical implementation.
3. As a means of cooperation within design teams.
4. As a means of cooperation across professional boundaries, i.e as a basis of communcation in a multidisciplinary team.
For us, the three first roles are relevant, and we will see how it goes next week!
Moreover, Carrol claims that a scenario is an 'informal narrative description' and allows us to tell a story and define a problem within the story, as a means to achieve concrete design and at the same time brainstorm for innovation. It is also naturally a good way to define, iterate, and go through the design process once again, it simply helps the group grasp what problem it pragmatically is trying to solve, and what consequences can arise.
That's it for this week!
/Denny, Ramtin, Mehrdad and Dawood
Inga kommentarer:
Skicka en kommentar