T Iteration Demo Hermes Team PP Iteration

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

T Iteration demo 3 Introduction to the project  Alloy in a nut shell  Goal:  Provide the user with a tool capable of sharing multimedia content and interact with his/her contacts.  Features:  Retrieve contact information (address, telephone, …)  Presence in instant messaging services (online, away, offline..)  Publish Blog  Publish content in services such as Flickr  Discussion groups  Location Information

T Iteration demo 4 Use Case example

T Iteration demo 5 Status of the iteration’s goals  Goal 1: Defining all stakeholders  OK. All stakeholders have been identified:  Tutor  Staff  Customers  Final users  Goal 2: Uncover the customer’s needs and map them into systems requirements  OK, customer’s needs have been identifies and requirements documentation has been created  Goal 3: Define development practices  OK, development practices have been discussed and agreements achieved

T Iteration demo 6 Status of the iteration’s deliverables  Project plan  OK, project plan document is completed  Requirements Specification  OK, all important requirements documented  Risk Management  OK, Document completed describing risk management policies and list of risks

T Iteration demo 7 Realization of the tasks Status RealizedPlanned Diff(Left) DEVELOPMENT Auto Capacitationok MANAGEMENT Project Planok Requirements Specificationok Risk Management Planok Total

T Iteration demo 8 Resource usage Real HrsPlaned Hrs JJRP (PM)70 RHC (QA)30 AS (A)30 Zhao J (D)2610 Abu R (D)2110 Tohuy Q (D)?10 Kavuri (D)1310 Li J (D)1810

T Iteration demo 9 Quality dashboard Part of the systemQualityConfidenceComments Project Plan2 Project Plan was created and reviewed by tutor and other members of the team Requirements Specifications 2 Requirements specifications was created and reviewed by customers. Risk Management Plan 2 Risk Management documentation was created and reviewed by tutor and other members of the team. Progress Report1Progress Report was created Confidence: 3. Tested 2. Reviewed 1. Created Quality: GOOD DON’T KNOW BAD

T Iteration demo 10 Risks  What is the current situation regarding the risks?  Rafiq (QaM) has prepared a risk management plan and identified 27 risks.  Juan (PM), Rafiq (QaM) and Arturo (Arch) has a meeting on last Saturday to analyse those risks and find out potential risks for the project  List of risks has been refined

T Iteration demo 11 Results of the iteration  Most important content of the major deliverables of the iteration  project plan  requirements  QA plan  Demonstration of first demo

T Iteration demo 12 Project plan  Present the following  Stakeholders and staffing  Customers: John Evans, Tommi Ilmonen  Tutor: Tuomas Niinimäki  Staff: Rafiqul Hasan Chowdhurry, Arturo Salinas, Ehao Yinji, Abu Rashid, Tohuy Quynh, Kavuri Sateesh Babu, Li Jingxuan, Juan Jose Rodriguez P  Project goals  Provide the user with an interaction tool  Provide the customer with information related to user’s behavior  Project practices  Bi-weekly meetings  Define goals and deliverables  Coding conventions  Time reporting  Communication practices  Deliverable responsible

T Iteration demo 13 Requirements  Functional requirements  User can send and receive instant messages from Google Talk  User can publish photos in Flickr  User can send a picture to her/his friends  User can receive streams (from RSS providers and other contacts)  User can post comments on a stream  User can share streams with other mobile users

T Iteration demo 14 Risk log

T Iteration demo 15 Demo

T Iteration demo 16 Used work practices  How have you been using the planned work practices, what are the experiences of  Bi-weekly meetings. No bi-weekly meetings yet  Time reporting – poor. Needs to be more strict  Communication Practices: Wiki tool hasn’t showed to be sufficient for communication, and phone calls have shown to have better results. Wiki tool however has been helpful to share documentation.  Deliverable Responsible: Ok, requires to improve communication  Are you going to  Communication not exclusive by wiki  Weekly internal meetings to enhance internal communication