T76'4115 Iteration Demo

1
T-76.4115 Iteration Demo

• Team Shigeru
• PP Iteration22.10.2008

2
Agenda

• Introduction to the project (5 min)?
• Project status (15 min)?
• achieving the goals of the iteration
• project metrics
• Work results (20 min)?
• presenting the iterations results
• Used work practices (5 min)?
• Questions and discussion

3
Background

• Cinemas are being digitalized all over the world
• This is an expensive process

4
Background

• Even today the cinemas aren't even nearly selling
  all the tickets, especially early in the day

5
Background

• Is it possible to do something else in the
  cinemas besides watching movies?
• (..and Formula 1)?

6
Introduction to the project
7
Introduction to the project
8
Cinema Gaming platform - Introduction

• The project team is going to create a platform
  for cinema gaming
• Idea is to test if gaming is possible and/or fun
  in cinemas
• Because of the selected technologies the users
  will play the game with mobile phones
• The project team will create 2 games, one more
  simple voting-type of game and one more
  complicated game

9
Status of the iterations goals

• Goal 1 Project planning
• OK
• Goal 2 Understanding the domain
• OK
• Goal 3 Requirements specification on general
  level including most important functional
  requirements and use cases
• OK
• Goal 4 Selecting appropriate tools
• OK
• Goal 5 Setting up development environment
• OK
• Goal 6 Creating an architecture that meets the
  project's needs
• OK
• Goal 7 Learning the technologies for the
  solution
• OK
• Goal 8 Identification of the risks
• OK

10
Status of the iterations deliverables

• Project plan
• OK, some chapter missing as they did not need to
  be ready for this date
• Requirements document
• OK, some chapter missing as they did not need to
  be ready for this date
• Instructions and guidelines for development
• Not completely OK, a large amount of the planning
  iteration went on planning the games and
  architecture
• Architecture for the system
• OK, high-end architecture has been designed but
  no real document about is yet created
• Specification for the first game
• We have confirmed the specification with the
  client but not a real document has been made yet

11
Realization of the tasks

• The project planning went under budget
• Lot of time used in personal learning and team
  meetings
• The fact that the team is creating a game changed
  many things
• The team can't just decide on a good game idea
• Lot of discussion and thinking done outside the
  project, gathering information and ideas

12
Resource usage
Original plan (in the beginning of the iteration)?

• There are more hours saved for I1 now
• The plan is to make the platform part ready
  during I1 so that all the biggest risks are faced
  as early as possible
• I2 is saved for making the more complicated game,
  documenting, testing and fixing.

Realization and updated plan
13
Project plan
14
Risks 1/1
15
Risks 2/2
16
Project plan

• Team Shigeru
• PP Iteration22.10.2008

17
Project group

• Rauno Järvinen (Project manager)?
• Christian Lindholm (QA manager)?
• Max Vilkki (Architect)?
• Johannes Vuorinen (developer, co Architect,
  server admin, server team leader)?
• Jaakko Assola (developer, co Project manager)?
• Dmitri Sosimov (developer)?
• Marko Tyrväinen (developer, mobile team leader)?
• Ilja Ojala (developer, co QA manager

18
Stakeholders
19
Iterations

• Two iterations divided into 2 sprints each
• Sprint contents
• Planning phase, deciding on features to be
  included. Agreed with the customer. Kick-off
  meeting at the beginning of each sprint
• Development phase, features for the sprint
• Testing and integration phase, the features are
  verified and tested properly
• Reflection workshop at the end of each sprint,
  all the methods and processes used are discussed
  and improved

20
Requirements document

• Team Shigeru
• PP Iteration22.10.2008

21
Requirements

• Divided into groups, some examples
• Administrative functionality
• Game moderator can configure the game during the
  session
• Player interaction
• Players have profiles
• User experience
• The game experience needs to be smooth
• Game development
• Game development with the platform has to be
  possible and easy
• Game interfaces
• HD quality video, high resolution
• Miscellaneous
• 100 mobile clients can join a single gaming
  session

22
User groups
23
Technologies and Architecture

• Team Shigeru
• PP Iteration22.10.2008

24
Technologies

• Server
• Java
• Java 3D for 3D and videossounds
• Client
• Mobile phones (Nokia N95)?
• J2ME
• WLAN used for connections

25
Architecture
26
Project group background

• Every member of the group has experience in Java
  development
• Main reason for choosing Java to both server and
  client
• Some developers have wide experience in J2ME
  knowledge transferring will be done
• Everyone has some learning to do

27
Used work practices

• Team Shigeru
• PP Iteration22.10.2008

28
Used practices 1/2

• Team meetings
• Every Wednesday morning
• Starts with a scrum like daily where everyone
  tells what he's been doing and what he is going
  to do next
• Problems come out
• Progress report
• Progress report is done every Wednesday
• TRAC
• TRAC will be used to follow the project
• All important information is found in TRAC
• Documentation
• Documentation is done in English
• All documentation will be found in TRAC
• Planning
• Iteration/Sprint planning will be done using TRAC
• Kick-off meeting at the beginning of each sprint
• All task and features for the sprint allocated to
  developers

29
Used practices 2/2

• Communication
• All important news and meetings will be informed
  by e-mail
• Weekly face-to-face meetings
• Skype used when face-to-face is not required
• IRC used for less important matters
• Tasks
• Tasks will be allocated to developers in TRAC
• Easy following of the project
• Hours reporting
• Working hours will be reported to TRAC
• Project manager gathers the hours to a table each
  week in the progress report
• Pair programming days
• As the project group is divided into smaller
  teams, it is very easy to use pair programming.

30
Process improvements

• During the first sprint kick-off a quick overview
  for TRAC is needed. The tool is new for many of
  the members of the group
• Plan a way to transfer the knowledge inside the
  group

31
Thank you for listening

• Questions?