T-76.4115%20Iteration%20Demo

1
T-76.4115 Iteration Demo

• BitPlayers
• PP Iteration19.10.2005

2
Agenda

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

3
Introduction to the project

• Topic ContextMUPE
• Customer HIIT (Helsinki Institute of Information
  Technology)
• Two phases
• Develop ContextMUPE system
• Develop ContextMUPE application demonstrating the
  new functionality
• Phase 1
• Goal Integrate MUPE (Multi-User Publishing
  Environment) and ContextPhone so they can
  communicate together
• Duration Implementation 1
• Phase 2
• Goal Develop with ContextMUPE an application
  that takes context information acquired by
  ContextPhone as input and reacts to it
  accordingly.

ContextMUPE
ContextPhone
MUPE
Context information
4
Status of the iterations goals

• Goal 1 Form project group by recruiting
  developers
• OK
• 3 developers recruited (Hattula, Lindstedt,
  Saarinen)
• 4th developer will be recruited only if necessary
  (extra developer is assigned to our group)
• Goal 2 Project Planning Select and adapt work
  practices to be used in the project, schedule the
  project
• OK partially
• High-level scheduling has been done
• Most of the work practices to be used are defined
  in the project plan, remaining practices will be
  defined during the iteration planning of
  Implementation 1.
• Goal 3 Understanding project domain
• OK partially
• All group members have read available
  documentation on MUPE and ContextPhone
• Discussions with customer to deepen understanding
• We are lacking some documents regarding MUPE and
  ContextPhone (eg. Interface specifications)
• Goal 4 Requirements specification on general
  level
• OK
• Requirements have been determined with customer
  and are described in Requirements document
• Goal 5 Develop high-level architecture
• OK
• Architectural solution has been discussed with
  the customer and a high-level design has been
  developed

5
Status of the iterations deliverables

• Project plan
• OK, except
• 5.1.11 Coding convention Will be determined with
  developers in iteration planning of
  Implementation 1
• 5.1.12 Peer testing Not planned yet as it will
  be carried out in February. Section will be added
  during iteration planning of Implementation 2.
• 5.2. Quality plan Will be created in iteration
  planning of Implementation 1
• 5.3. Tools List not complete, will be completed
  with developers (and customer) during iteration
  planning of Implementation 1
• 6.3 6.4 Task division of Implementation 1 2.
  Will be done during iteration planning phase of
  these implementations.
• Requirements document
• OK, all important requirements documented in
  general level and reqs 1,2,3,... in detail

6
Realization of the tasks
Status Real Plan Diff (Left)
Recruiting project group ok 1 4 -3
Meetings ok 36.5 31.5 5
Lectures ok 34 45 -11
Studying (technologies, project domain) ok 17 20 -3
Project Management unfinished 17 18 -1 5
Infrastructure unplanned 5 0 5 3
Requirements planning ok 12 22 -10 8
High-level architecture ok 7 10 -3
Total 176 201 -25
7
Working hours by person
Realized hours in this iteration
Real Plan Diff
Hattula 10,5 10 0,5
Kauranen 56 50 6
Kemppainen 25 30 -5
Lauerma 31 30 1
Lindstedt 9,5 20 -0,5
Saarinen 6,5 20 -3,5
Total 138,5 140 -1,5

• Developers work easy to estimate (role not big
  in this iteration)
• Tasks not divided equally, project planning
  budget exceeded and tasks not finished
• Requirements planning went more easily than
  expected, requirements document required more
  work than expected

8
Changes to the project

• No changes yet
• Possibility of additional developer joining the
  group

9
Risks

• Initial risks identified in project plan, no
  risks realized yet

10
Results of the iteration

• Briefly describe the most important content of
  the major deliverables of the iteration, e.g.,
  the following
• project plan
• Phasing of the project
• Regular schedule for iterations planning,
  development, refining
• requirements
• Defining functionality of ContextMUPE
• Filters
• Cache
• Interfaces
• Debugging

11
Project plan

• Present the following
• Stakeholders and staffing
• Project goals
• Project resources
• Developers Hattula, Lindstedt, Saarinen
• Development server and test phone provided by
  customer
• Project practices and tools
• Development tools
• Communication practices (meetings)
• SEPA subjects
• Discuss phasing if there are some major plans
  already

12
Used work practices

• How have you been using the planned work
  practices, what are the experiences of
• mandatory practices
• Resource planning very difficult to estimate
  time consumption, especially as group not formed
  from the beginning
• Time reporting process created, group not yet
  accustomed to the practice
• Practices to be used are defined in the project
  plan an will be developed further while creating
  the QA plan in the iteration planning of
  implementation 1

13
Questions?
14
Project organization
15
Project Goals

• Adding to the understanding of the possibilities
  in using context information in mobile multi-user
  applications.
• Being able to rapidly develop proof-of-concept
  applications using information of both the
  context of the individual mobile user and the
  overall environment.
• Improving the existing systems (MUPE and
  ContextPhone) by integration.
• Maintain and improve the usability and
  extendability of the MUPE platform.
• Developing a MUPE application demonstrating the
  use of context information of an individual user.