T Iteration Demo BitPlayers PP Iteration

T Iteration demo 2 Agenda  Project status (5 min)  achieving the goals of the iteration  project metrics  Work results (10 min)  presenting the iteration’s results  demo  Used work practices (5 min)

T Iteration demo 3 Introduction to the project  Topic: ContextMUPE  Customer: HIIT (Helsinki Institute of Information Technology)  Two phases 1. Develop ContextMUPE system 2. 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. ContextPhoneMUPE Context information ContextMUPE

T Iteration demo 4 Status of the iteration’s goals  Goal 1: Form project group by recruiting developers  OK  3 developers recruited (Hattula, Lindstedt, Saarinen)  4 th 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

T Iteration demo 5 Status of the iteration’s deliverables  Project plan  OK, except:  Coding convention: Will be determined with developers in iteration planning of Implementation 1  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

T Iteration demo 6 Realization of the tasks StatusRealPlanDiff(Left) Recruiting project groupok 14-3 Meetingsok Lecturesok Studying (technologies, project domain)ok Project Managementunfinished Infrastructureunplanned Requirements planningok High-level architectureok Total

T Iteration demo 7 Working hours by person  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 RealPlanDiff Hattula 10,510+0,5 Kauranen Kemppainen Lauerma Lindstedt 9,520-0,5 Saarinen 6,520-3,5 Total 138,5140-1,5 Realized hours in this iteration

T Iteration demo 8 Changes to the project  No changes yet  Possibility of additional developer joining the group

T Iteration demo 9 Risks  Initial risks identified in project plan, no risks realized yet

T Iteration demo 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

T Iteration demo 11 Project plan  Present the following  Stakeholders and staffing Stakeholders and staffing  Project goals 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

T Iteration demo 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

T Iteration demo 13 Questions?

T Iteration demo 14 Project organization

T Iteration demo 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.