Embed Size (px)
Citation preview
Product Development Project
PROJECT PLAN Smart Clothing
Project Plan
1
Table of Contents 1. Version History ...................................................................................................................................... 2
2. Background ........................................................................................................................................... 3
3. Objectives and Scope ............................................................................................................................ 3
3.1 Project Objectives ............................................................................................................................. 3
3.2 Project Scope ..................................................................................................................................... 3
3.3 Project Goals and Success Criteria .................................................................................................... 4
4. Organization .......................................................................................................................................... 5
4.1 Organization chart ............................................................................................................................ 5
4.1.1 Organization of the Project team based on project functions .................................................. 5
4.1.2 Organization Hierarchy Chart ........................................................................................................ 5
4.2 Responsibilities ............................................................................................................................. 6
4.2.1 Responsibility Matrix .................................................................................................................. 6
4.2.2 Contact Details and Backup ....................................................................................................... 7
5. Project Process ...................................................................................................................................... 8
5.1 Process overview .............................................................................................................................. 8
5.2 Sub-processes ............................................................................................................................... 9
5.3 Methods ......................................................................................................................................... 10
6. Schedule .............................................................................................................................................. 13
7. Budget ................................................................................................................................................. 18
8. Risk Management ............................................................................................................................... 18
9. Change Management .......................................................................................................................... 19
9.1 Do we need to change .................................................................................................................... 19
9.2 How to change it ............................................................................................................................. 19
Project Plan
2
1. Version History
Version Author Date Comments
0.1 Evans Mungai 04.11.2013 Initial project plan draft
Project Plan
3
2. Background Nokia Research Center has been conducting research in the field of sensors of different form factors and meant for a vast number of use cases areas ranging from measuring proximity, humidity, temperature etc. This research has mainly been to create new business opportunities for Nokia as well as create Intellectual Property for the company. While there are many sensor designs already done by NRC, few of these have been used in consumer products. The sensors team in Nokia needed new ideas of how their sensors would be used. For this reason, a project was proposed that would involve people who would think “out of the box” and not succumb to the bias of having worked in the sensors research field for long. The Nokia team also chose an area that they have not ventured into before; clothing. PDP was chosen as the place to conduct the research on how their sensors would be used because of the large pool of student resources that the course had to offer. Terms such as e-textiles, wearables and smart fabrics are use in the research area of clothing with electronics. Areas such as sports, military and health care already have consumer products developed and in the market.
3. Objectives and Scope
3.1 Project Objectives The aim of this project is to generate new use cases for sensors in everyday life with a focus towards clothing. The clothing would be capable of measuring the user and the environment through sensors. The goal is to design new clothing embedded with sensors and user interfaces constructed from items typical to clothing. The proposed design could also be capable of communicating wirelessly to mobile phones and be capable of changing the material property based on the environment (monitored via embedded sensors). A service can also be designed to complement the clothing design. This service should solve a new problem, or an old problem solved in a new way.
3.2 Project Scope
1. The clothing should be affordable and used on a day to day basis i.e. not competitive sport
suits or suits used for industrial purposes etc. 2. The project should not focus on military clothing, medical clothing and wearable
gadgets/accessories. 3. The project should primarily focus on Nokia sensors but other sensors can be incorporated.
Project Plan
4
3.3 Project Goals and Success Criteria
1. The sponsor’s expectations are to have, at minimum, a wide market research on smart
fabrics. Their focus is mainly on the knowledge we generate at the end of the project as opposed to having an actual prototype. However, the teams’ and course’s expectations are to have a prototype. With both of these taken into consideration, we aspire to have a wide market research done and a prototype as well.
2. The team aims to learn on product development. This will be aided by the product development project course book and guidance by the staff.
3. The team aims to learn and improve in team work. Our experience during the two semesters will be of value in achieving this goal.
4. The team expects to enjoy this experience as well. Through organized fun activities and working to have a positive environment as we work together, we shall achieve this goal.
To succeed at the end of this project, our team would be satisfied in having come up with a solution and prototype of a problem within this research area. Our sponsor would be happy to have at least an innovative idea of how their sensors would be used in clothing.
Project Plan
5
4. Organization
4.1 Organization chart
4.1.1 Organization of the Project team based on project functions
4.1.2 Organization Hierarchy Chart
Project Plan
6
4.2 Responsibilities
4.2.1 Responsibility Matrix
Responsib
ilitie
s
Pro
ject
Man
ag
er
Learn
ing
Man
ag
er
Meeti
ng
/Lo
cati
on
Man
ag
er
IT M
an
ag
er
Safe
ty M
an
ag
er
Tim
e M
an
ag
er
Acco
un
ts M
an
ag
er
Do
cu
men
tati
on
Man
ag
er
Sn
acks M
an
ag
er
Fu
n M
an
ag
er
Blo
g/F
lyer
Man
ag
er
Researc
h F
ab
ric
Researc
h E
lectr
on
ics
Researc
h S
ocia
l
Desig
n C
loth
ing
Desig
n S
oft
ware
Desig
n E
lectr
on
ics
Desig
n I
nte
gra
ted
Team Members
Haiko
Inkeri
Patrik
Kiran
Evans
Hao
Liis
Karri
Alex
Dima (Dmytro)
Johnny
Vivek
MJ
Project Plan
7
4.2.2 Contact Details and Backup
First Name Last Name Email Phonenumber
Branch of
Study /
Expertise
BackUp
Resource
Haiko Kaczmarek [email protected] +358 (0) 466 421 274Energy
Engineering
Inkeri Aaltio [email protected] +358 (0) 41 524 96 17
Industrial
Design/
Clothing
Design
Patrik Waenerberg [email protected] +358 (0) 40 842 59 50
Telecommunic
ation /
Electrical
Engineering
Kiran Kumar [email protected] +358 (0) 466356223
Network
Technology /
Electrical
Engineering
Evans Mungai [email protected] +358 (0) 50 487 14 22Computer
Science (SDE)
Hao Wang [email protected] +358 (0) 44 956 11 21Mechanical
Engineering
Liis Västra [email protected] +358 (0) 44 567 58 27
Chemical
Engineering &
Industrial
Management
Karri Kurunmäki [email protected] +358 (0) 50 041 21 93 Business
Alex Forss [email protected] +358 (0) 405 156 013Mechanical
Engineering
Dima (Dmytro) Arbuzin [email protected] +358 (0) 414 942 436Computer
Science
Vivek
MJ
Project Plan
8
5. Project Process
5.1 Process overview
Empathize – starting phase of the project, the aim of which is to create a common ground for all
team members, the outcome of Empathize phase should be project plan and friendly open
environment inside the team, to ensure smooth workflow during next phases.
Research – second and very important phase, during which team will collect and analyze all
available information related to the project. The outcome of Research phase should be a
database with information about cloth, sensors, technologies, smart fabrics, etc…
Define – the phase during which team will validate all data from previous phase. Team will
define on different user groups and problems. The outcome of this phase should be different
possible use-cases of sensible clothes.
Ideate – next phase during which team will focus on certain concepts. The outcome of this
phase should be concept(s) to implement.
Prototype – phase of designing the product. The outcome should be working prototype of
sensible clothes.
Test – final phase of testing the product.
Project Process a not linear, so phases will be overlapping, and at some point team might repeat
some steps over and over again.
Prototype
Test
Define
Research
Ideate Empathize
Project Plan
9
5.2 Sub-processes
Empathize
• Team builduing
• Project Plan
• PDP Brief
• Inspiration and direction for ideas
Research
• User needs/service
• Internet research
• Clowth research
• Market research
• Technology research
Ideate
• Brainstorming for concepts implementation
• Create ideas for solutions
• Create solutions patterns
• Focus on optimal solutions
Prototype
• Design
• Testing on the way
• Procurement
• Duilding the prototype
• Developing software
Test
• Testing the concept\prototype
• Documenting
Define
• Validate:
• research
• observation
• Define problems
• Decide on the problem
• Define the task
Project Plan
10
5.3 Methods
Team builduing
• Going out
• Climbing
• Hopes and Fears
• Personal Stories
PDP brief
• Meeting up with sponsors
• PDP 6
Project Plan
• Brainstorming
• Group Discussion
Insparation and
directions
• Brainstorming
Clowth research
• Internet research
• Surveys
• Interviews
Technology research
• Internet research
• Pattens search
• Nokia presentation
Social research
• Interviews
• Online surveys
Empathize
Research
Project Plan
11
Validate
• Brainstorming
• Group discussion
Define problems
• Group discussion
• Voting
Define tasks
• Group discussion
• Voting
Deside on the
problem
Create ideas for solutions
• Brainstorming
• Meditation
Create solutions patterns
• Another method
• One more
Focus on optimal
solutions
• Common sence
• Brainstorming
Define
Ideate
Project Plan
12
Design• One method
• Another
SW developing
• One
• Another
Constraction• Method 1
• Method 2
Procurement
Test• Try it
• Special tests
Documentation
• Writing
• Typing
Presentation
• Rehersuals
Prototype
Test
Project Plan
13
6. Schedule
Project Plan
14
Project Plan
15
Project Plan
16
Project Plan
17
Project Plan
18
7. Budget
8. Risk Management
Risk Risk level Severity Impact Actions to Minimize Risk
Time spent on meetings is inefficient.
3 3 9 Limited time assigned for each topic and planning before
Information flow to and from remote members breaks
3 3 9 We will use whatsapp, email, drive and skype
Time management 3 3 9 Proper planning and good project management
Conflicts inside team 3 3 9 Open communication and clear rules
Work amount underestimated
2 3 6 Members track their working time
Lacking of professional skills 2 3 6 Outsourcing, asking help, proper research
Demotivation 2 3 6 Parties, recreational activities, track accomplishments
Getting injured when working on prototype
1 3 3 Safety officer will advise and assist
Going in a wrong direction with project
1 3 3 Design brief dictates our course
Problems with supply chain 1 3 3 Order from a reliable supplier
Going over budget 1 2 2 Planning economically
Project Plan
19
9. Change Management Change management is an effective approach to transitioning individuals, team, and organization to a desired future state. So the team must learn how to handle changes to the organization. In our project change management process, we divided change management into two parts: Do we need to change and how to change it.
9.1 Do we need to change
When decide which of the latest techniques or creative idea to adopt, we must consider four major factors:
The goal of our project
The feasibility of our proposal: time, money…
The desired of market
The interested of teammates
9.2 How to change it
In case we approve to make a change, we need to find effective approaches to change. There are three advices:
Ensure that standardized analysis
Report what we are going to change
Review our project process PS: I made our change management based on the figure named change management process (see figure1). I think the first part “do we need to change” contain 1. Request for change, 2.impact analysis and 3. Approve/Deny. The second part “how to change it” include the remaining part. If you have some good suggestion or advice, we could discuss it on session.
Project Plan
20
