T Iteration demo T Iteration Demo Neula PP Iteration

T Iteration demo Agenda 2 Introduction - Our key issues Status of the iterations goals and deliverables Realization of the tasks Resource usage Quality metrics Changes to the project Risks Other results of the project

T Iteration demo Introduction to the project Through gadgets 3 Increased usability Value for customers Brand recognition Enabling external development Suunto’s goals Our Key issues Understanding the customers – Suunto and its users Understanding possiblities for sports web 2.0 High level of collaboration – as external developers

T Iteration demo 4 Introduction - Our key issues Status of the iterations goals and deliverables Realization of the tasks Resource usage Quality metrics Changes to the project Risks Other results of the project

T Iteration demo Status of the iteration’s goals and deliverables 5 Understanding the problem Gathering requirements Understanding the problem Gathering requirements Creating the documents Implementing the infrastructure Creating the documents Creating the iteration demo Writing the project plan Input from customer Understanding the course requirements input from Team Creating the requirements document Feedback from customers Customer requirement s Team - Working on requirements Understanding the problem of the customer Understanding problem domain Infrastructure Deploying the infrastructure Infra needs gathering Possible infra needs

T Iteration demo Status of the iterations goals Creating the documents – Documents finished – Creation of documents and the projects needs did not fit well together for us. Implementing the infrastructure – Server rented – Programming environments set up – Testing and studying technologies done – Working practices tested and it works Gathering requirements – Brainstorming – Analysis – Prototype descriptions Understanding the problem – Research, testing, analysis – Prototype descriptions 6

T Iteration demo 7 Introduction - Our key issues Status of the iterations goals and deliverables Realization of the tasks Resource usage Quality metrics Changes to the project Risks Other results of the project

T Iteration demo Realization of the tasks 8 DaniEeroLasseLauriOhtoPaavoRikuVilleGrand Total Application prototypes2,0 Benchmark projects1,5 0,51,03,01,0 9,5 Choose and set up server7,5 Communicating to stakeholders2,0 Communications meeting1,0 5,0 Gather information of OpenSocial1,0 Gather knowledge on requirements1,0 3,0 Gather requirements from Suunto3,5 Kickoff meeting5,56,55,5 6,0 5,56,046,5 Make FB testapp2,0 6,0 Make iGoogle testapp3,55,59,0 Managing requirements6,53,01,03,510,55,530,0 Meeting with mentor1,0 4,0 Perjantaisessio7,5 Plan and Write requirements document2,0 Platforms and Technologies13,011,024,0 Scheduling0,513,013,5 Server configuration3,0 Set up communications12,51,0 9,524,0 Set up version control2,0 Study course requirements0,53,54,0 Team req. meeting4,08,54,0 36,5 Testing CVS setup0,5 Weekly meeting1,5 2,04,83,02,55,522,3 Write iteration document3,0 Write project plan4,03,826,033,8 Grand Total30,050,532,024,024,736,581,526,0305,2

T Iteration demo Realization of the tasks 9

T Iteration demo 10 Introduction - Our key issues Status of the iterations goals and deliverables Realization of the tasks Resource usage Quality metrics Changes to the project Risks Other results of the project

T Iteration demo Resource usage 11

T Iteration demo 12 Introduction - Our key issues Status of the iterations goals and deliverables Realization of the tasks Resource usage Quality metrics Changes to the project Risks Other results of the project

T Iteration demo Quality metrics 13 Work practices are working very well – Friday meetings – Friday and Tuesday working together – No disturbing communications problems Requirements engineering picking up speed

T Iteration demo 14 Introduction - Our key issues Status of the iterations goals and deliverables Realization of the tasks Resource usage Quality metrics Changes to the project Risks Other results of the project

T Iteration demo Changes to the project Requirements have had to be collected more rigorously than expected 15 Sprint cycle Iteration cycle Requirements cycle

T Iteration demo Changes to the project Requirements engineering has been set into the schedule 16

T Iteration demo 17 Introduction - Our key issues Status of the iterations goals and deliverables Realization of the tasks Resource usage Quality metrics Changes to the project Risks Other results of the project

T Iteration demo Risks IDRiskEffectHow to avoidContingency planResponsibleSeverityProbability at start of project Probability R1The customer is not satisfied with the prototype descriptions We run out of time because it is too difficult to innovate good enough gadgets Concentrate on a pre- defined process and rules for the prototype descriptions and the creation of backlog Set a deadline for new gadget descriptions, demand input from Suunto, begin to implement after the deadline Paavo Häppölä543 R2Team cannot find common ground for communications and meeting practices Time is wasted and we never get to the implementation phase Start meetings early in the project and discuss the issues Split team up into smaller parts that have their own meetings. Share responsibility Riku Seppälä541 R3The documentation is not done properly, the customer is only given source code but no exchange of tacit knowledge is made The project doesn't benefit Suunto as much as planned Concentrate on the documentation and ask for feedback from Suunto Create the documentation after the project is finished. Riku Seppälä354 R4Communication doesn't work, Suunto doesn't understand what we're doing and we don't know about their requirements The targets are not met, we deliver an unusable product Plan enough meetings and send clear descriptions of gadgets to be implemented, not just a description of functions. Engage Suunto in the innovation process Add meetings to discuss communication issues Paavo Häppölä552 R5The workload is distributed unevenly Some members get frustrated and others not engaged. Quality suffers and no one enjoys the project Have set times for working together and a weekly meeting where everyone has to be present or have a legitimate reason for not being present. Follow up on tasks accomplished and concentrate on scheduling Remake the teams and delegate more responsibilites Riku Seppälä341 R6Most of the time is spent for optimizing for the course requirements and not for the actual project outcomes Customer and project members are dissatisfied Keep documentation light and let project manager handle the documentation for the course. Everyone doesn't have to be involved, keep everyone up-to-date at meetings instead Concentrate more on the customer needs. Riku Seppälä454 R7The needed technologies can not be mastered in time. We are not able to make the prototype descriptons reality The goals cannot be metConcentrate on what is most important, the important functionalities and leave the most difficult implementations to the end. Don't promise too big. Go back to the designs and design simpler gadgets. Use more familiar technologies Eero Palomäki542 R8Important persons from the customer side cannot be reached Time runs out. The requirements elicitation takes up too much time. Know when people are present. Use the telephone for communications. Have set practices and deadlines for gathering requirements Take more control of requirements Riku Seppälä341 R9The technologies and support needed from the client cannot be delivered on time Time runs out. The development becomes unneccesarily difficult, development effort goes to creating dummy interfaces etc. Understand the requirements, keep in contact with the IT of Suunto Lower the goalsEero Palomäki344 R10Used tools and technologies are poorly supported and development becomes difficult Time runs out.Use well documented and/or familiar tools and technologies Switch to other tools, lower the goals Eero Palomäki risks have been identified

T Iteration demo Risks Many of the initial risks have been minimized – Communication problems – Problems related to work practices – Technologies – Infrastructure Some still exist… – Customer satisfaction – Also more uncontrollable ones… 19

T Iteration demo 20 Introduction - Our key issues Status of the iterations goals and deliverables Realization of the tasks Resource usage Quality metrics Changes to the project Risks Other results of the project

T Iteration demo Results of the iteration We already discussed: – Understanding the problem – Requirements process – Time logging and time tracking – Tasking – Schedule – Risks identified Other: – Teams and responsibilities – Project management software – Wiki for status – Project goals – Tools – Prototype descriptions 21

T Iteration demo Results of the iteration - Teams 22

T Iteration demo Results of the iteration – Project management software Neula.zoho.projects.com Tasks Time logging – timesheets Documents Forum Meetings 23

T Iteration demo Results of the iteration - Wiki 24 TKK Wiki Current issues Work realized follow-up Current Issues Meeting memos Contact information Iteration Achievements

T Iteration demo Results of the iteration - Goals 25

T Iteration demo Results of the iteration - Tools 26

T Iteration demo Results of the iteration – Prototype descriptions 10 pdf’s – using existing interfaces 27