T-76.4115 Iteration Demo Global Dance Floor

1. T-76.4115 Iteration DemoGlobal Dance Floor Team 14 PP Iteration21.10.2009

2. Agenda • Project status (10 min) • Achieving the goals of the iteration • Project metrics • Work results (20-25 min) • Project plan • Requirements • Preliminary architectural design • Used work practices (5 min)

3. Introduction to the project

4. What is Global Dance Floor? • An interactive music playback and dancing platform, on which users can vote with their feet • After a song, guiding lights instruct people to move to a green or a red zone • Hardware sensor calculates yes and no votes and a new song is selected based on the results • Voting results are visualized on a display • Client: TKK/SoberIT

5. Status of the iteration’s goals • Requirements specifications, creating use cases • Done • Understanding the domain, getting to know the hardware • Not fully done, hardware not yet supplied • Initial architectural design • Done • Setting up project management and development server • Done • Have everything planned to ensure an efficient start for the first iteration round • For the most part, yes

6. Status of the iteration’s deliverables • Project plan • OK, QA plan delivered later • Requirements document • OK

7. Realization of the tasks • Hardware platform has not yet been installed • No proof-of-concept testing/coding could be done • Hardware documentation arrived last week • No major decisions regarding the system (e.g. programming language) could be done with certainty • As a result, the project is behind schedule

8. Resource usage Original plan (in the beginning of the iteration) • Explain the reasons for major discrepancies in realizations • Explain the reasons for changes in the plan Realization and updated plan You may present graphs instead of tables! (realized hours and updates)

9. Quality goals • Evaluation of the status of the project's quality goals

10. Changes to the project • No major changes have occurred.

11. Risks • What is the current situation regarding the risks? • materialized risks? • new risks identified?

12. Results of the iteration • Briefly describe the most important content of the major deliverables of the iteration, e.g., the following • project plan (especially in PP review) • requirements (especially in PP review) • system architecture (especially in I1 review) • QA plan (especially in I1 review) • implemented use cases (I1-I2) • user’s manual (I2) • Demonstrate the developed software • first tell briefly to the audience what you are going to demonstrate • distributing a demo script to the audience helps following the demo • concentrate on new functionality Avoid repeating what you have already told in project status and concentrate on showing the concrete results.

13. Example: Project plan • Present the following • Stakeholders and staffing (a diagram?) • Project goals (discuss most important goals and verification criteria) • Project resources (already shown in the project status?) • Project practices and tools (discuss most important practices and tools you have chosen, what, why, when, …) • Discuss phasing if there are some major plans already

14. Example: Demo script • System Administrator • function X • function Y • … • Basic user • function Z1 • function Z2 • …

15. Used work practices • How have you been using the planned work practices, what are the experiences of • mandatory practices: time reporting, version control, … • any other practices • Are you going to • adopt some new practices • change the use of the current practices • stop using some adopted practices In the presentation you have time to discuss only the most interesting experiences and major changes. The mentor will read the rest of the material from the slides himself later.