T-76.4115 Iteration demo T-76.4115 Iteration Demo Neula PP Iteration 21.10.2008

T-76.4115 T-76.4115 IterationIteration demo demo

T-76.4115 Iteration Demo

NeulaPP Iteration

21.10.2008


Agenda

2


Introduction to the projectThrough

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


4


Status of the iteration’s goals and deliverables

5


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


7


Realization of the tasks

8

Dani Eero Lasse Lauri Ohto Paavo Riku Ville Grand TotalApplication prototypes 2,0 2,0Benchmark projects 1,5 1,5 0,5 1,0 3,0 1,0 1,0 9,5Choose and set up server 7,5 7,5Communicating to stakeholders 2,0 2,0Communications meeting 1,0 1,0 1,0 1,0 1,0 5,0Gather information of OpenSocial 1,0 1,0Gather knowledge on requirements 1,0 1,0 1,0 3,0Gather requirements from Suunto 3,5 3,5Kickoff meeting 5,5 6,5 5,5 5,5 6,0 6,0 5,5 6,0 46,5Make FB testapp 2,0 2,0 2,0 6,0Make iGoogle testapp 3,5 5,5 9,0Managing requirements 6,5 3,0 1,0 3,5 10,5 5,5 30,0Meeting with mentor 1,0 1,0 1,0 1,0 4,0Perjantaisessio 7,5 7,5Plan and Write requirements document 2,0 2,0Platforms and Technologies 13,0 11,0 24,0Scheduling 0,5 13,0 13,5Server configuration 3,0 3,0Set up communications 12,5 1,0 1,0 9,5 24,0Set up version control 2,0 2,0Study course requirements 0,5 3,5 4,0Team req. meeting 4,0 8,5 4,0 4,0 4,0 4,0 4,0 4,0 36,5Testing CVS setup 0,5 0,5Weekly meeting 1,5 1,5 1,5 2,0 4,8 3,0 2,5 5,5 22,3Write iteration document 3,0 3,0Write project plan 4,0 3,8 26,0 33,8Grand Total 30,0 50,5 32,0 24,0 24,7 36,5 81,5 26,0 305,2


Realization of the tasks

9


10


Resource usage

11


12


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


14


Changes to the project

• Requirements have had to be collected more rigorously than expected

15

Sprint cycle

Iteration cycle

Requirements cycle


Changes to the project

• Requirements engineering has been set into the schedule

16


17


RisksID Risk Effect How to avoid Contingency plan Responsible Severity Probability at start

of projectProbability

R1 The 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ä 5 4 3

R2 Team 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ä 5 4 1

R3 The 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.


R4 Communication 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ä 5 5 2

R5 The 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


R6 Most 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.


R7 The needed technologies can not be mastered in time. We are not able to make the prototype descriptons reality

The goals cannot be met Concentrate 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äki 5 4 2

R8 Important 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


R9 The 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 goals Eero Palomäki 3 4 4

R10 Used 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 5 2 1

18

• 10 risks have been identified


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


20


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


Results of the iteration - Teams

22


Results of the iteration – Project management software

• Neula.zoho.projects.com• Tasks• Time logging

– timesheets

• Documents• Forum• Meetings

23


Results of the iteration - Wiki

24

• TKK Wiki• Current issues

• Work realized follow-up• Current Issues• Meeting memos

• Contact information• Iteration Achievements


Results of the iteration - Goals

25


Results of the iteration - Tools

26


Results of the iteration – Prototype descriptions

• 10 pdf’s – using existing interfaces

27