T-76.4115 Iteration demo
T-76.4115 Iteration Demo
Neula
PP Iteration
21.10.2008
T-76.4115 Iteration demo
Agenda
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
2
T-76.4115 Iteration demo
Introduction to the project
Suunto’s goals
Increased usability
Value for customers
Through
gadgets
Our Key issues
Understanding the
customers – Suunto
and its users
Brand recognition
Understanding
possiblities for
sports web 2.0
Enabling external
development
High level of
collaboration – as
external developers
3
T-76.4115 Iteration demo
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
4
T-76.4115 Iteration demo
Status of the iteration’s goals and
deliverables
Creating the
iteration demo
Creating the documents
Creating the documents
Implementing the infrastructure
Gathering requirements
Input from
customer
Gathering requirements
Input from
customer
Understanding the problem
Understanding the problem
Creating the
requirements
document
Writing the
project plan
Understanding the
course
requirements
input from
Team
Feedback
from
customers
Customer
requirement
s
Infrastructure
Team - Working on
requirements
Deploying the
infrastructure
Understanding the
problem of the
customer
Infra needs
gathering
Understanding
problem domain
Possible
infra needs
5
T-76.4115 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-76.4115 Iteration demo
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
7
T-76.4115 Iteration demo
Realization of the tasks
Dani
Application prototypes
Benchmark projects
Choose and set up server
Communicating to stakeholders
Communications meeting
Gather information of OpenSocial
Gather knowledge on requirements
Gather requirements from Suunto
Kickoff meeting
Make FB testapp
Make iGoogle testapp
Managing requirements
Meeting with mentor
Perjantaisessio
Plan and Write requirements document
Platforms and Technologies
Scheduling
Server configuration
Set up communications
Set up version control
Study course requirements
Team req. meeting
Testing CVS setup
Weekly meeting
Write iteration document
Write project plan
Grand Total
Eero Lasse
1,5
1,5
7,5
1,0
5,5
6,5
3,5
Lauri Ohto
2,0
0,5
1,0
1,0
1,0
1,0
1,0
5,5
5,5
2,0
5,5
6,5
1,0
13,0
3,0
1,0
11,0
0,5
12,5
1,0
2,0
4,0
0,5
8,5
4,0
1,5
1,5
1,5
4,0
0,5
2,0
4,0
30,0 50,5
32,0
24,0
Paavo Riku Ville Grand Total
2,0
3,0 1,0 1,0
9,5
7,5
2,0
2,0
1,0
1,0
5,0
1,0
1,0
1,0
3,0
3,5
3,5
6,0
6,0 5,5 6,0
46,5
2,0
2,0
6,0
9,0
1,0
3,5 10,5 5,5
30,0
1,0
1,0
4,0
7,5
7,5
2,0
2,0
24,0
13,0
13,5
3,0
3,0
1,0 9,5
24,0
2,0
3,5
4,0
4,0
4,0 4,0 4,0
36,5
0,5
4,8
3,0 2,5 5,5
22,3
3,0
3,0
3,8
26,0
33,8
24,7
36,5 81,5 26,0
305,2
8
T-76.4115 Iteration demo
Realization of the tasks
50.0
45.0
40.0
35.0
30.0
25.0
20.0
15.0
10.0
5.0
0.0
9
T-76.4115 Iteration demo
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
10
T-76.4115 Iteration demo
Resource usage
400.0
350.0
300.0
250.0
Realized hours
200.0
Planned hours
150.0
100.0
50.0
0.0
37
38
39
40
41
42
43
100
80
60
40
Planned hours
20
Realized hours
0
Planned hours
11
T-76.4115 Iteration demo
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
12
T-76.4115 Iteration demo
Quality metrics
• Work practices are working very well
– Friday meetings
– Friday and Tuesday working together
– No disturbing communications problems
• Requirements engineering picking up speed
13
T-76.4115 Iteration demo
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
14
T-76.4115 Iteration demo
Changes to the project
• Requirements have had to be collected more
rigorously than expected
Requirements cycle
Brainstorming
Iteration cycle
[Development]
New prototype
descriptions
Creation of
prototype
descriptions in
the team
Sprint cycle
[Meeting]
Discussion and
ranking of
prototypes
Feedback and
refining
15
T-76.4115 Iteration demo
Changes to the project
• Requirements engineering has been set into
the schedule
16
T-76.4115 Iteration demo
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
17
T-76.4115 Iteration demo
ID
Risk
Effect
How to avoid
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 preSet a deadline for new
defined process and rules gadget descriptions,
for the prototype
demand input from
descriptions and the
Suunto, begin to
creation of backlog
implement after the
deadline
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
R3
Risks
Responsible
Severity
Paavo Häppölä
5
Probability at start Probability
of project
4
3
Split team up into smaller Riku Seppälä
parts that have their own
meetings. Share
responsibility
5
4
1
The documentation is not The project doesn't
done properly, the
benefit Suunto as much
customer is only given
as planned
source code but no
exchange of tacit
knowledge is made
Concentrate on the
Create the
Riku Seppälä
documentation and ask documentation after the
for feedback from Suunto project is finished.
3
5
4
R4
Communication doesn't The targets are not met,
work, Suunto doesn't
we deliver an unusable
understand what we're product
doing and we don't know
about their requirements
Plan enough meetings
Add meetings to discuss Paavo Häppölä
and send clear
communication issues
descriptions of gadgets
to be implemented, not
just a description of
functions. Engage Suunto
in the innovation process
5
5
2
R5
The workload is
distributed unevenly
Have set times for
Remake the teams and
working together and a delegate more
weekly meeting where responsibilites
everyone has to be
present or have a
legitimate reason for not
being present. Follow up
on tasks accomplished
and concentrate on
scheduling
Riku Seppälä
3
4
1
R6
Most of the time is spent Customer and project
for optimizing for the
members are dissatisfied
course requirements and
not for the actual project
outcomes
Keep documentation
Concentrate more on the Riku Seppälä
light and let project
customer needs.
manager handle the
documentation for the
course. Everyone doesn't
have to be involved, keep
everyone up-to-date at
meetings instead
4
5
4
R7
The needed technologies The goals cannot be met
can not be mastered in
time. We are not able to
make the prototype
descriptons reality
Concentrate on what is Go back to the designs
most important, the
and design simpler
important functionalities gadgets. Use more
and leave the most
familiar technologies
difficult implementations
to the end. Don't promise
too big.
Eero Palomäki
5
4
2
R8
Important persons from Time runs out. The
Know when people are
the customer side cannot requirements elicitation present. Use the
be reached
takes up too much time. telephone for
communications. Have
set practices and
deadlines for gathering
requirements
Take more control of
requirements
Riku Seppälä
3
4
1
R9
The technologies and
support needed from the
client cannot be
delivered on time
Lower the goals
Eero Palomäki
3
4
4
Eero Palomäki
5
2
1
R10 Used tools and
technologies are poorly
supported and
development becomes
difficult
Some members get
frustrated and others not
engaged. Quality suffers
and no one enjoys the
project
Contingency plan
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
Time runs out.
Use well documented
Switch to other tools,
and/or familiar tools and lower the goals
technologies
• 10 risks have been
identified
18
T-76.4115 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-76.4115 Iteration demo
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
20
T-76.4115 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-76.4115 Iteration demo
Results of the iteration - Teams
22
T-76.4115 Iteration demo
Results of the iteration – Project
management software
• Neula.zoho.projects.com
• Tasks
• Time logging
– timesheets
• Documents
• Forum
• Meetings
23
T-76.4115 Iteration demo
Results of the iteration - Wiki
•
•
•
•
TKK Wiki
Current issues
• Work realized follow-up
• Current Issues
• Meeting memos
Contact information
Iteration Achievements
24
T-76.4115 Iteration demo
Results of the iteration - Goals
25
T-76.4115 Iteration demo
Results of the iteration - Tools
26
T-76.4115 Iteration demo
Results of the iteration – Prototype
descriptions
• 10 pdf’s – using existing interfaces
27