MediaLAB Amsterdam Design Process 2014
M EDIALAB AM STERDAM DESIG N PROC ESS 20 1 4
About (4-13)
— MediaLAB Amsterdam — Manifesto — Team
Program (14-45) 2
— Design Process — Scrum — Toolkit — Workshops
TA B LE OF CON TEN T
@MediaLAB Amsterdam (46-61) — Multidisciplinary team — Presenting your work — Rules of thumb
Schedule (62-76)
— September — October
— November — December/January 3
4 M EDIALAB AM STERDAM DESIG N PROC ESS 20 1 4
About
M EDIALAB AM STERDAM DESIG N PROC ESS 20 1 4 6
“We don‘t design for the sake of designing, we design for a purpose” Marco van Hout
Our current age sees everything as an object of manufacture, as something which can be got hold of and improved or altered, to produce better or more effective outcomes. Though this is what makes us human, we
A B O UT
should stay focused on designing for a purpose: to meet a need, to achieve a goal, or to make a statement.
7
M EDIALAB AM STERDAM DESIG N PROC ESS 20 1 4 8
About MediaLAB Amsterdam
Research and design with a focus on current, relevant and meaningful digital media and applications. It offers talented students a structured, high-paced, 20-week program in which they experiment and search for solutions in challenging projects formulated by academic and industry partners. The project teams are multidisciplinary and international, comprising students from different cultural backgrounds and from both academic and applied study areas. Each team writes a full academic paper and presents a working prototype to the challenging partners. The teams work five days
A B O UT
a week at Studio HvA or at the partner’s premises. The students have one day a week to work individually on the documentation of their internship or graduation project. The program is in English and available to all final year students from universities and applied universities. During the program students follow an agile Human-Centered Design process supported by an expert from the MediaLAB, several workshops, and coaching by external experts. MediaLAB Amsterdam is located in Studio HvA and is part of CREATE-IT, the applied research centre of the School of Design & Communication at the Amsterdam University of Applied Sciences.
9
M EDIALAB AM STERDAM DESIG N PROC ESS 20 1 4
The Agile MediaLAB Manifesto Our highest priority is to satisfy society with the early, open and continuous delivery of valuable research and meaningful solutions. We welcome change and acknowledge the need to continuously adapt tools, approaches and requirements to meet changing needs and respond to other results. We deliver working prototypes frequently and test them continuously with real people. Researchers, designers and engineers must work together daily and connect with other stakeholders as much as possible throughout the project. We build projects around motivated individuals. We give them the environment and support they need, and trust them to get the job done.
10
A B O UT - M AN IFESTO
The most efficient and effective method of conveying information to and within a development/research team is face-toface conversation. Useful research and working prototypes are the primary measures of progress. Agile processes promote sustainable research. Sponsors, partners, researchers and developers should be able to maintain a constant pace indefinitely. Continuous attention to scientific, technical and design excellence enhances agility. Simplicity – the art of maximizing the amount of work not done – is essential. The best theories, requirements, solutions and designs emerge from self-organizing teams. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly.
11
M EDIALAB AM STERDAM DESIG N PROC ESS 20 1 4
Loes Bogers
My background is in critically engaged electronic arts, and media & cultural studies. I hold a BA in Media & Culture: New Media from the University of Amsterdam and an MA in Interactive Media from Goldsmiths College, London. In recent years I’ve worked as innovator in arts education for youth and worked on projects at the Patching Zone (NL) and Kitchen Budapest (HU). Forget about practice, there’s only do: let’s get our hands dirty.
l.bogers@hva.nl
Gabriele Colombo
I hold a Master degree in Communication Design from Politecnico di Milano. My focus is on data visualization, infographics and visual story telling. In the past years I have gained a good experience in designing visual tools to facilitate academic and market research projects. I have worked at The Visual Agency, an Italian design agency focused on infographics and I often collaborate as a visual designer with the Digital Methods Initiative. I like big excel files, risotto, old maps and typographic ligatures.
g.colombo@hva.nl
Gijs Gootjes
12
My background is in Media Entertainment & Pop Culture. Since 2008 I’ve been researching and designing media applications with various partners from the MediaLAB. Besides my work at the MediaLAB I‘ve started an R&D lab at the NOS, the Netherlands News Network. I love to work on topical issues and trends in media and technology. Coordinating the MediaLAB gives me the opportunity to create collaborations between research, education and creative industries and work with talented and highly motivated students. In my spare time I love to visit Amsterdam’s creative hotspots. I can advise you on places to go for inspiration or just an icecold beer.
g.gootjes@hva.nl
With a passion for human centered design, I bring over 12 years of experience in applied research and design practice. In the past decade I have specifically specialized and pioneered in design for emotion, building the foundations of this emerging field. I am a co-founder of Susa-Group, a strategic design consultancy. As board member of the International Design & Emotion Society and as trainer / public speaker I have the opportunity to travel and see many countries, but the best trips are to my atic where I love to create abstract paintings. As research and design program coordinator I foster the role and importance of applied research and the need for structure, critical
A B O UT
Marco van Hout
thinking and deep questioning in our design process.
m.van.hout@hva.nl
Tamara Pinos
My interests in art and technology motivated me to move to The Netherlands where I have discovered the fun of tinkering, affecting computing and serious games. I hold a BA in Computer Engineering from the Pontificia Universidad Cat贸lica del Ecuador and a MSc in Media Technology from Leiden University. I am co-founder of Advance Consulting, a software development company based in Quito-Ecuador and have experience as a programr, project manager and dancer.
t.v.pinos.cisneros@hva.nl
Margreet Riphagen
For the last ten years I have gained experience in various disciplines of new and interactive media. I hold a bachelor degree in Integrated Communication Management, a post bachelor in Business Science and a master in Information Studies, track Human Centered Multimedia. After working at the Waag Society and Media Guild for more than five years, I now work for the Amsterdam University of Applied Sciences since 2008. Also I am involved in the Institute of Network Cultures with various research projects. My motto is keep your feet on the ground and keep reaching for stars.
m.riphagen@hva.nl
13
14 M EDIALAB AM STERDAM DESIG N PROC ESS 20 1 4
Program
M EDIALAB AM STERDAM DESIG N PROC ESS 20 1 4 16
A high-paced, agile design program with room for experimentation and personal development. MediaLAB Amsterdam uses a combination of an iterative design cycle and Scrum process in order to foster both the creative process and enforce teams to work structured and goal oriented.
P RO G RAM
This has proven to be a powerful combination for the multidisciplinary design teams that work on projects in the labcontext that we provide. The process is further fed by workshops, an extensive (research) method toolkit, expert meetings, and supported by (embedded) researchers and MediaLAB coaches.
17
M EDIALAB AM STERDAM DESIG N PROC ESS 20 1 4 18
Design Process
The MediaLAB Amsterdam design process is a problem solving method that helps create and evaluate solutions in response to challenges. In the process MediaLAB tries to evoke real curiosity in order to make the teams feel highly motivated for finding answers and solutions. This involves lots of iterations, making, prototyping, going out on field studies and test each idea, concept or prototype with actual users.
SPRINT PLANNING
DESIGN METHODS TOOLKIT
D ESIG N PROC ESS
IDEATION
IDEATION AND PLANNING (2)
RESEARCH CREATE
sprint
RESEARCH CREATE
translate
(3)
SPRINT REVIEW (4)
SPRINT RETROSPECTIVE (5)
19
RESEARCH
20
translate
CREATE
M EDIALAB AM STERDAM DESIG N PROC ESS 20 1 4
At the start of every design challenge, and after, at the start of each new stage in the design process, research has a central role. Research will provide plenty of insights; of how people act/think/feel and who the intended users are, within the context of the challenge.
D ESIG N PROC ESS
RESEARCH, TRANSLATE AND CREATE.
Those insights are the key to a solution, however they will have to be translated into actual requirements for the design: which are key for the optimal solution? That is something that can be decided based on research and be implemented and tested by creating a prototype. A next step could be again to research what you created by setting up a test with users. During the project there is a constant flow, following both directions; from research, translation to creation, and from creation, translation to research.
21
M EDIALAB AM STERDAM DESIG N PROC ESS 20 1 4
Scrum
Scrum is an iterative and incremental process for design and development of products and services and has a very specific way to organize a team. Tasks will be achieved faster and with higher quality with the help of the Scrum-Framework. This is possible because of the high self-motivation of the team, which chooses itself how tasks will be executed. The project partner’s demands will be iteratively prioritized and quickly realized. At MediaLAB Amsterdam, the flow of the design process is embedded in a sprint-based schedule, supported by Scrum roles, rituals, sessions and artifacts that support the process.
22
SCRUM
SPRINTS A sprint (or iteration) is the basic unit of development. The sprint is a “timeboxed� effort; that is, it is restricted to a specific duration. The sprints in the MediaLAB program have an average duration of three weeks. However, teams are free to fit and exercise more sprints within those scheduled three weeks.
sprint
RITUALS At the MediaLAB we use specific rituals during each sprint. Each sprint starts with an ideation and planning session, has a mid-sprint translation/ transfer session, and ends with a sprint review meeting and retrospective. During a sprint, the team has daily stand up meetings.
IDEATION
translate 23
M EDIALAB AM STERDAM DESIG N PROC ESS 20 1 4
1 — Daily stand up meeting
The daily standup meeting takes place at the same time and place of every working day. The daily scrum meeting is held in the morning, as it helps set the context for the coming day’s work. These scrum meetings are strictly time-boxed to 15 minutes. This keeps the discussion brisk but relevant. The daily stand up meeting is not used as a problem-solving or issue resolution meeting. Issues that are raised are taken offline and usually dealt with immediately after the meeting. During the daily scrum, each team member answers the following three questions: a - What did you do yesterday? b - What will you do today? c - Are there any impediments in your way? 24
PLANNING
SCRUM - RITUALS
2 — Ideation and planning
IDEATION
Every sprint has a ideation and planning session. In this session the creative process is triggered by the facilitation of a brainstorm and ideation session in which ideas are identified and sketched out quickly. The most promising ideas are placed in a hierarchy and it is decided which have potential to be taken along in the sprint. After this, tasks are identified, but more important the exact sprint goal (and duration) is set out. It is important to have a very clear goal, so that the team can cut the effort down into smaller sized pieces that contribute to achieving that goal more smoothly, using the planboard (§ pag 34, Toolkit) 25
M EDIALAB AM STERDAM DESIG N PROC ESS 20 1 4
3 — Translate and transfer
translate
In the middle of the 3-week sprint, there is a scheduled translate and transfer session, in which, your team and the project-related researchers come together and translate research insights and decide which things to act on in this sprint or the next (transfer).
26
SCRUM - RITUALS
4 — Sprint review
After the team has finished the planned deliverables for this sprint, it is time for the sprint review. In this meeting, which is organized with all stakeholders present, decisions on the progress and how to proceed are made, including next steps and possible needs and wishes. Specifically, the team will present the work they did during the sprint and will run through the sprint backlog together with stakeholders.
27
M EDIALAB AM STERDAM DESIG N PROC ESS 20 1 4
5 — Sprint retrospective
At the very end of each sprint, the retrospective is being held. Sprint retrospective is a meeting to reflect on both the results and the process with the team. It is meant to change, improve or stick to the way they work and function as a team.
28
DESIGN METHODS TOOLKIT
SPRINT PLANNING
RESEARCH CREATE
sprint
RESEARCH CREATE
MediaLAB Design Process
IDEATION
IDEATION AND PLANNING
translate
SPRINT REVIEW
SPRINT RETROSPECTIVE
M EDIALAB AM STERDAM DESIG N PROC ESS 20 1 4
ROLES Scrum has only three roles and the relationship between these roles is easily defined and easy to understand.
Scrum Master (SM)
Team
30
Product Owner (PO)
SCRUM - ROLES
1 — Product Owner
PO
The Product Owner is the final authority on the requirements for the product and responsible for the product vision and improving return on investment. The PO manages the end user and stakeholder’s expectations, prioritizing the product backlog, release planning and providing clear and testable requirements to the team. A PO collaborates with the team, end users and stakeholders ensuring that the goals are met and that they accept the deliverables at the end of each sprint. The project partner is the PO, and during the sprints the team coach serves as dedicated Product Owner. 31
M EDIALAB AM STERDAM DESIG N PROC ESS 20 1 4
2 — Scrum Master
SM
Responsible for facilitating the team: creating a trustful and inclusive environment, facilitating team meetings and negotiations with the product owner and removing team and organisational impediments. SM’s keep the process moving forward, ensuring that the values and principles of scrum along with its framework are followed. He/She also facilitates the stand-up meetings and the retrospective, and organizes the planning and ideation sessions and the sprint reviews.
32
The SM is a crucial role within the team, ensuring its success. Therefore, at the start of the semester, each team has to make sure to appoint someone who fits the characteristics of a good SM. Important: the SM is also a team member.
SCRUM - ROLES
3 — Team
TEAM
The multidisciplinary design team is cross-functional, autonomous and self-organising. The team is responsible for researching the requirements, translating those and making their own design and implementation decisions. The team members track the progress of their own work with the guidance of the scrum master and the team commits to create deliverables being accountable to the product owner for delivering as promised.
33
5
DONE
PENDING
IN PROGRESS
SCRUMBOARD
TO DO
M EDIALAB AM STERDAM DESIG N PROC ESS 20 1 4 34
Artifacts
SPRINT BACKLOG
3
USER STORIES
2
TASKS
4
PRODUCT BACKLOG
1
SCRUM - ARTIFAC TS
1 — Product Backlog The requirements for the product are listed in the Product Backlog. It is an always changing, dynamically prioritized list of requirements ordered by Business Value. Requirements are broken down into User Stories. 2 — User Stories User stories are short, simple description of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system. They typically follow a simple template: As a <type of user> I want <some goal> so that <some reason>
3 — Sprint Backlog The Sprint Backlog contains all the committed User Stories for the current Sprint broken down into Tasks by the Team. All items on the Sprint Backlog should be developed, tested, documented and integrated to fulfill the commitment. 4 — Tasks The goal is to have all tasks fixed for the current sprint without having to add new tasks. 5 — Scrumboard The Scrumboard gives you a quick way of visually seeing the status of your iteration. Add and move stories into different columns to change their statuses, such as to-do, in progress, pending for approval and done. Every Team member works on tasks and the PO decides when the tasks go from pending to done.
35
M EDIALAB AM STERDAM DESIG N PROC ESS 20 1 4
MediaLAB method toolkit
To support research planning, ideation and testing, MediaLAB Amsterdam has developed a special method toolkit, which is a combination of a 60+ method cards collection and a plan board.
36
MED IALAB M ETH ODS TOOLK IT
PLAN BOARD
Use the plan board to have a clear idea of what the goals are, how much time needs to be invested and what the results will mean for a possible solution. O-DO, IN PROGRESS, PENDING FOR APPROVAL AND DON The plan board asks the teams to take a User Story as a starting point. Then, go to the method cards deck and choose a method according to the goal the User Story represents.
USER STORIES
METHOD CARDS
TIME ESTIMATION
SINGLE TASKS
Then time needs to be estimated (how long will execution, preparation and analysis take?). Based on the necessary steps in the method, the User Story can be cut down into single tasks (and serves as input for the scrum board).
39
M EDIALAB AM STERDAM DESIG N PROC ESS 20 1 4
Method cards The MediaLAB Amsterdam method card collection is a very wide range of design and research methods that can be used to get the necessary insights.
Define Goals and Intentions
Know Context
Know User
Frame Insights
Ideation and Concepts
Create and Test
The methods are divided in categories relating to the type of insights that can be gained with them. The methods can be about defining goals, knowing context, knowing the user, framing insights, ideation, prototyping or testing. Most of the cards can be used throughout the complete design process. The teams are encouraged to use a variety of methods (in order to have a wide variety in insights) and use them continuously. The method plan board is literally the backside of the scrum board, making them interdependent. 40
SE
I
R
K
SO
A O
N IA L
0 1
N
YA
K
A
TR IG
G
ER
M EDIALAB AM STERDAM DESIG N PROC ESS 20 1 4 42
Workshops An important part of the support in the design process consists of the workshop program. These workshops are facilitated by experts from the MediaLAB and from the field and follow the work intensity and current needs of the teams as the program evolves. Students will learn about ideation, selection of ideas, user experience (design), user testing, prototyping, business model canvas, etc. Every workshop withholds relevant information and skills for each sprint.
WO RKSH OPS
Workshop Scrum September 8 9:30 - 12:00
Scrum
This workshop covers the principles and process (theory) underpinning the mechanics, rules and roles of the Scrum framework. Attention is paid to the rituals, artifacts and roles, and specifically how they relate to the program and creative process within the MediaLAB. Students learn through instruction and team-based exercises, and are challenged to think in terms of the Scrum principles to better understand what to do when starting their project. After this workshop, scrum teams still need a lot of practicing and trial/error, but it is beneficial to team dynamics and project progress from day one! 43
M EDIALAB AM STERDAM DESIG N PROC ESS 20 1 4
Problem Definition
In order to clearly understand the “problem” the team has been asked to solve, this workshop will show how a design brief can be written based on a deep understanding of stakeholders, needs, values, requirements, restrictions and opportunities that surround the assignment. Furthermore, teams are inspired to think beyond descriptives and become creative thinkers.
44
WO RKSH OPS
Workshop Problem definition September 15 9:30 - 12:30
D ESIG N
Workshop Tinkering September 17 9:30 - 12:30
Tinkering
Tinkering is all about exploring materials (often technical materials) and finding new applications by engaging with them in playful, somewhat unstructured ways. In this workshop, students will experiment with Makey Makey (an Arduino-based device that lets you turn nearly anything into a computer key) and Scratch (a free programming language, originally developed by MIT for kids, where you can create your own interactive stories, games, and animations). Build a playful installation, game or prototype in just the time of this half-day workshop! 45
M EDIALAB AM STERDAM DESIG N PROC ESS 20 1 4
Workshop Ideation October 6 9:30 - 12:30
IDEATION
Ideation
In this workshop, students start once more with checking their understanding of the problem at hand. In order to generate good ideas, it is vital to fit them well within context. The workshop introduces several high-paced and productive exercises that can be used to generate lots of ideas in a short time frame. Teams will then try and cluster the ideas into potential solutions. One of the most important goals of the workshop is to have fun, open your mind and change the way you look at the world.
46
WO RKSH OPS
Workshop User Experience Design October 29 9:30 - 12:30
User Experience Design
This workshop engages the teams in a hands-on â&#x20AC;&#x2DC;design for experienceâ&#x20AC;&#x2122; practice. By introducing a systematic approach to designing products that deliberately elicit predefined emotional responses, the workshop aims to facilitate a shift from an intuitive to a structured and manageable perspective on user experience in conceptual design processes. Denying the experiential and emotional impact in the design of new concepts is like denying they are designed for humans.
47
M EDIALAB AM STERDAM DESIG N PROC ESS 20 1 4
Workshop User Testing November 19 9:30 - 12:30
User Testing
User testing is important but is often overlooked due to budget, time, and resource constraints. This workshop will explain how user testing can support the design process and can be employed to deliver better a user experience and a more meaningful end product. Learn how to choose between unmoderated and moderated testing. Learn when to integrate testing at different development/ design phases. Learn how to maximize the ROI by knowing what to test. How to extract useful patterns from qualitative and quantitative tests. 48
WO RKSH OPS
Workshop Business Model Canvas December 17 9:30 - 12:30
Business Model Canvas
The Business Model Canvas, is a strategic management and entrepreneurial tool. It allows to describe, design, challenge, invent, and pivot any business model. In this workshop, teams will be challenged to imagine the business behind their concept and foresee opportunities, constraints, challenges, etc. Seeing the potential of the concept from a business perspective will help to sharpen the offering and final deliverable, and will support future scenarios for the continuation of the project after the semester. 49
@MediaLAB Amsterdam
M EDIALAB AM STERDAM DESIG N PROC ESS 20 1 4 52
Your team is bigger than you might think! You are supported by many. Besides your fellow team members, many other people are directly involved in the project. An expert from the MediaLAB Amsterdam team, your graduation or internship mentor, the project partners
@ MEDIALAB AM STERDAM
and, in the course of the design process, developers, external experts, creative consultants, etc.
53
M EDIALAB AM STERDAM DESIG N PROC ESS 20 1 4 54
Multidisciplinary and multicultural teamwork
At MediaLAB you work in a team comprising people with different skill sets and from different educational and cultural backgrounds. Even local cultural differences between people from the same country can have a big impact on the way they work with each other. Working in a team with a varied composition therefore requires a special attitude, both professionally and socially. Here are some things you should take into account.
â&#x20AC;&#x201D;
T EA M WORK
Language
Multidisciplinary and intercultural teams are great for creative processes. However, when people who work together have different languages, this can be an obstacle to success. Speaking in your mother tongue is very different from speaking in a second or third language.
So consider your words carefully; there are issues of interpretation, but also of cultural differences, especially when the spoken language is not the first language for either of you. Use visuals, write down your ideas, sketch. Make sure you are understanding each others.
55
M EDIALAB AM STERDAM DESIG N PROC ESS 20 1 4
Communication Styles â&#x20AC;&#x201D; Methods of communication that are normal for one group of people may appear ineffective or inappropriate to another group.
A person from a culture in which loud voices and interruptions are not seen as aggressive may intimidate someone from a culture that teaches more reserved modes of expression.
Learning in advance about the cultures of your team members before you work on a team with them can help you understand their methods of communication.
56
—
T EA M WORK
Hierarchy
The importance of authority varies greatly between cultures. Some groups give great respect to people in positions of authority, while people from other cultures are perfectly willing to question an authority figure if they see him doing something wrong. Authority is based on different criteria in different cultures. The nature of a team should be made clear to all participants at its inception. At the beginning of the semester you will therefore write a team ‘plan’ in which ways of working together, but also values and roles are written down and agreed on.
57
M EDIALAB AM STERDAM DESIG N PROC ESS 20 1 4
Conflict — When conflict does occur within a team, members from different backgrounds may react to it in dramatically different ways. Some people will repress their reactions to an insult or slight, while others will fight back. These reactions are based on individual personality to some extent but are also conditioned by a person’s background.
Resolving conflict between team members effectively requires an understanding of everyone’s view of what caused the conflict. Being open, but respectful to each other’s background, is the best remedy for conflict resolution.
58
T EA M WORK
Language
Communication Styles
Hierarchy
Conflict
59
M EDIALAB AM STERDAM DESIG N PROC ESS 20 1 4 60
Presenting your work
At the end of the design process you will have the opportunity to share with the world what you have created. We use the website as a communication portal for all our projects, but you will also have the opportunity to present your results to the creative industry during a final event organized at MediaLAB Amsterdam. This will be the showcase of your final design and prototype. You will present yourselves as experts to an audience consisting of friends, family, partners from the creative industries but also creative agencies looking for the latest trends and scouting for talent.
One of MediaLAB Amsterdam’s most important communication channels is its blog. Here, project teams keep followers and friends updated on the latest developments and insights in their projects or in related fields. As a team we trust you are just as proud as we are of our work, and just as keen to share its news on a regular basis. In the first week you will learn how our blog works and how you can best communicate and promote your team’s work there.
P RESEN TIN G YOUR WORK
BLOG
SHARING, WORKING, DOCUMENTATION To work together efficiently you’ll need tools to collaborate on projects, share documents and calendars, and communicate. There are huge numbers of digital tools to help you with this: use them! The right tools will put the most relevant information within easy reach. 61
M EDIALAB AM STERDAM DESIG N PROC ESS 20 1 4 62
Rules of thumb
No ambitious program would be achievable without some good old rules of thumb about things you can do, or should do (act); things to remember; and things to respect. We expect you to take note of these and commit them to memory. We are open for initiatives, so if you have anything to add or suggest (a change), please do not hesitate to talk to someone from the MediaLAB team and your team members. Weâ&#x20AC;&#x2122;ll find a way to make everybody happy.
RUL ES OF TH UM B
act 1 — Every team works and studies for five days a week from 9:00 until 17:30. 2 — Schedule when you will spend time on individual research, your own graduation project, or your personal development plan 3 — Appreciate the value of the structured morning-scrum setup; it is there to help you and your team aim for the highest level of quality 4 — Finish things in time, as agreed upon with your team in your meetings
63
M EDIALAB AM STERDAM DESIG N PROC ESS 20 1 4
remember 1 — Involve or CC your MediaLAB expert coach in communications with the project partner. In case of a meeting, inform them in time about the details. The expert will always want to be present at partner meetings 2 — You can request a day off with your PM. Of course you will have to inform your team too. One day requests: a week in advance. More than one day? At least 3 weeks in advance. Be aware that your requests may or may not be granted, depending on project needs. 3 — The MediaLAB team is not responsible for your personal grades (except for international students)
64
RUL ES OF TH UM B
respect 1 — Keep to the team agreement document that you filled in at the start of the process 2 — In the event of illness, please contact your expert coach before 9:30 3 — Keep the MediaLAB tidy, shiny and awesome! 4 — Workshops are obligatory. There are no exceptions, as these are a vital part of the program. If you arrive late, the doors will stay closed 5 — Some distraction is good, but don’t overdo social media, appointments with others during working hours, etc. Keep the work/fun ratio balanced 6 — You are not alone, and your team members will need to feel the same dedication coming from you as they are putting in themselves. Keep the same energy level and the motor will run beautifully!
65
Schedule
Schedule — September MONDAY
TUESDAY
WEDNESDAY
THURSDAY
FRIDAY
1
2
3
4
5
sprint 0
KICK OFF
MONDAY
TUESDAY
WEDNESDAY
THURSDAY
FRIDAY
8
9
10
11
12
sprint 0
deadline: user scene
DESIGN CULTURE
WORKSHOP SCRUM
- MORNING
INTRODUCTION
-AFTERNOON
PARTNER VISIT
REVIEW AND RETROSPECTIVE
MONDAY
TUESDAY
WEDNESDAY
THURSDAY
FRIDAY
15
16
17
18
19
WORKSHOP PROBLEM DEFINITION
WORKSHOP TINKERING
sprint 1 PLANNING
deadline: design brief
MONDAY
TUESDAY
WEDNESDAY
THURSDAY
FRIDAY
22
23
24
25
26
sprint 1 TRANSLATE SESSION
translate
Schedule — September/October MONDAY
TUESDAY
WEDNESDAY
THURSDAY
FRIDAY
29
30
1
2
3
9:30-12:30
MAKE SESSION AT MK24
sprint 1 REVIEW AND RETROSPECTIVE
WRITE UP
PEERPITCH
deliverable 1
MONDAY
TUESDAY
WEDNESDAY
THURSDAY
FRIDAY
6
7
8
9
10
IDEATION
IDEATION
WORKSHOP IDEATION
WORKSHOP IDEATION
sprint 2 PLANNING
- MORNING
-AFTERNOON
MONDAY
TUESDAY
WEDNESDAY
THURSDAY
FRIDAY
13
14
15
16
17
sprint 2 TRANSLATE SESSION
IDEA SELECTION TEAM SESSIONS
translate
deadline: design brief
MONDAY
TUESDAY
WEDNESDAY
THURSDAY
FRIDAY
20
21
22
23
24
9:30-12:30
sprint 2 REVIEW AND RETROSPECTIVE
PEERPITCH
deliverable 2
WRITE UP
Schedule — October/November MONDAY
TUESDAY
WEDNESDAY
THURSDAY
FRIDAY
27
28
29
30
31
sprint 3 PLANNING
WORKSHOP UX DESIGN
MONDAY
TUESDAY
WEDNESDAY
THURSDAY
FRIDAY
3
4
5
6
7
sprint 3 TRANSLATE SESSION
translate
- MORNING
-AFTERNOON
MONDAY
TUESDAY
WEDNESDAY
THURSDAY
FRIDAY
10
11
12
13
14
9:30-12:30
sprint 3 REVIEW AND RETROSPECTIVE
PEERPITCH
deliverable 3
MONDAY
TUESDAY
WEDNESDAY
THURSDAY
FRIDAY
17
18
19
20
21
sprint 4 PLANNING
WORKSHOP USER TESTING
Schedule — November/December MONDAY
TUESDAY
WEDNESDAY
THURSDAY
FRIDAY
24
25
26
27
28
sprint 4 TRANSLATE SESSION
translate
MONDAY
TUESDAY
WEDNESDAY
THURSDAY
FRIDAY
1
2
3
4
5
9:30-12:30
sprint 4 REVIEW AND RETROSPECTIVE
PEERPITCH
deliverable 4
- MORNING
-AFTERNOON
MONDAY
TUESDAY
WEDNESDAY
THURSDAY
FRIDAY
8
9
10
11
12
sprint 5
sprint 5
TRANSLATE SESSION
PLANNING
translate
MONDAY
TUESDAY
WEDNESDAY
THURSDAY
FRIDAY
15
16
17
18
19
sprint 5 REVIEW AND RETROSPECTIVE
WRITE UP WORKSHOP BUSINESS MODEL
deliverable 5
Schedule — December/January MONDAY
TUESDAY
WEDNESDAY
THURSDAY
FRIDAY
22
23
24
25
26
XMAS PERIOD
XMAS PERIOD
XMAS PERIOD
MONDAY
TUESDAY
WEDNESDAY
THURSDAY
FRIDAY
29
30
31
1
2
XMAS PERIOD
XMAS PERIOD
XMAS PERIOD
XMAS PERIOD
- MORNING
-AFTERNOON
XMAS PERIOD
MONDAY
TUESDAY
WEDNESDAY
THURSDAY
FRIDAY
5
6
7
8
9
final sprint
final sprint
TRANSLATE SESSION
PLANNING
translate
MONDAY
TUESDAY
WEDNESDAY
THURSDAY
FRIDAY
12
13
14
15
16
final sprint REVIEW
TRY-OUT
final deliverable
Schedule — January MONDAY
TUESDAY
WEDNESDAY
THURSDAY
FRIDAY
19
20
21
22
23
MONDAY
TUESDAY
WEDNESDAY
THURSDAY
FRIDAY
26
27
28
29
30
9.30 BUSINESS MODEL CANVAS VALORIZATION SESSIONS
DELIVER PACKAGE TO PARTNERS
- MORNING
-AFTERNOON
MediaLAB Amsterdam Design Process 2014 medialabamsterdam.com