T-76.4115 Iteration Demo

1
T-76.4115 Iteration Demo

• Team 13
• PP Iteration24.10.2007

2
Agenda

• Project status (15 min)
• achieving the goals of the iteration
• project metrics
• Work results (20 min)
• presenting the iterations results
• demo
• Used work practices (5 min)

3
Introduction to the project

• What is this project about?
• Web portal to Simulation system Simantics
• Bringing the power of simulations to the general
  public
• Creating a community for simulation users and
  model/solver developers
• Creating a marketing channel for solver
  developers

4
Status of the iterations goals

• Goal 1 Finished project plan
• OK
• Goal 2 Requirements specifications for
  Requirements Document
• OK
• Goal 3 Architectural plan for implementation
• OK
• Goal 4 Infrastructure for the project based on
  architectural plan
• Goal 4.1 Application server installation
• OK
• Goal 4.2 Package infrastructure in
  svn-repository
• OK
• Goal 5 Understanding the domain
• OK

5
Status of the iterations deliverables

• Project plan
• OK
• Requirements document
• OK, Requirements validated by the customer
• Architectural plan
• OK, high level planning done, also implemented in
  the infrastructure

6
Realization of the tasks
Status Realized Planned Diff (Left)
Design Ok 17 20 -3
Project infrastructure Partial 22 25 2 5
Project management Ok 96 110 -14
Programming Ok 0 0
Documenting Ok 0 5
Studying OK 0 45 -45
Quality assurance Ok 0 0
Total 135 205 -70

• Documentation took much more time than expected
• Studying (Hello world-code) not accomplished
  because of the infrasructure

7
Resource usage
Original plan (in the beginning of the iteration)
Joni J-P Nina Antti Ville Oleg Roch Juha Ferr Total
PP 50 50 40 15 10 10 10 10 10 205
I1 50 50 55 65 70 70 40 70 70 575
I2 50 50 55 70 70 70 70 70 70 570
Total 150 150 150 150 150 150 150 150 150 1350
Realization and updated plan
Joni J-P Nina Antti Ville Oleg Roch Juha Ferr Total
PP 48 37 25 10 1 10 1 1 3 122
I1 52 63 70 70 79 70 79 79 77 639
I2 50 50 55 70 70 70 70 70 70 570
Total 150 150 150 150 150 150 150 150 150 1350
(realized hours and updates)
8
Quality goals

• High quality documents
• Gives a good base for actual coding
• Quality plan will be made in the beginning of I1

9
Changes to the project

• No major changes during Project Planning-iteration

10
Risks
ID Risk Probability Severity
1 One of the team members leaves the group. 2 3
2 Server crash Data loss 1 3
3 Simantics-system is not ready to be implemented during this project. 1 2
4 Team member may not have enough skills to accomplish his tasks 2 2
5 Communication is insufficient 3 3
6 Sprints are too short 2 2
11
Results of the iteration

• Project Plan
• Working methods, goals and tools documented
• Requirements document
• A communication tool between team and the
  customer
• Architectural plan
• High level architecture
• Package architecture
• ER-chart
• Main components

12
Stakeholders
13
Project goals
Goal Verification criteria
1. A youtube-like public simulation site F1,F2,F4
2. A professional site build on the public site F3
Requirements document, ch 6 Functional
Requirements
14
Tools

• MS Word, Excel, Powerpoint
• Subversion
• TRAC
• Eclipse
• Subclipse
• RSE
• JBoss
• Hibernate
• Ant
• JUnit
• Cruise Control
• Communication
• E-mail
• IRC

15
Working Methods

• In addition of mandatory practices of this course
• Practices
• Scrum-like iterative methods
• Meetings with team and customer beginning of
  every sprint
• Weekly time reporting in our time tracking system
• Prototyping
• Helps in gathering the requirements
• Helps also in the high level design database
  design

16
Phasing

• 3 sprints/iteration
• Production update after every iteration
• Fast visible results

17
Used work practices

• Mandatory practises
• Time tracking is always challenging
• No problems with version control
• Documentation will really help in the next
  iterations
• Other practises
• IRC as a non-formal discussion channel works well
• Wiki has proven itself a useful tool as a
  information channel
• But it needs effort to keep it readable