T-76.4115 Iteration Demo

1. T-76.4115 Iteration Demo Apollo Crew I1 Iteration10.12.2008

2. Project status (15 min) achieving the goals of the iteration QA plan project metrics Work results (20 min) Technical specification Demo Used work practices (5 min) Agenda

3. Introduction to the project Source: Dipoli entrance hall

4. Introduction to the project • Client: Design Factory • Project: Information & reservation system • Welcome visitors • Guide and assist visitors • Manage events • Workspace reservation system • System will work in Design Factory’s entrance hall and via web. • Project also includes testing some new devices such as touch screen.

5. Status of the iteration’s goals • Infrastructure up and running • Development infrastructure & server, OK • Production server, OK • Implementation • Working skeleton, OK • Views and features that are described in Dashboard, PARTIALLY • Scope of the Sprint 2 was reduced. • Advanced UI concepts and ZK framework implementation, OK • Updated html-demo, OK • Release(s) to production server, OK • Group • Keep supportive and inspiring atmosphere, OK • Track stress and load levels, OK • Project planning • Identify and control risks, OK • Good stakeholder communication, OK

6. Status of the iteration’s deliverables • Project plan, OK • Iteration plan, OK • Quality assurance plan, OK • Requirements document, OK • Technical specification, OK • QA documents • Test cases, OK • QA report, OK • Test log, OK • Progress report, OK • Release to production server, OK • Internal deliverables • Working skeleton with some views and features, OK • Advanced UI concepts, OK • Extended and improved html-demo, OK

7. Realization of the tasks: I1 Situation 5.12.2008

8. Resource usage (1/3): Whole project Situation 5.12.2008

9. Resource usage (2/3): Implementation 1 Situation 5.12.2008

10. Resource usage (3/3): Updated plan Situation 5.12.2008 (R) realized hours (E) estimated hours after Sprint 2 = realized + expected hours in the end Sprint 3-5 hours are planned

11. Quality assurance plan (1/2) • Quality goals • QC1: Functionality • QC2: Usability • QC3: Code correctness • QC4: Maintainability • Levels of testing • Unit • Integration • System • Acceptance • Types of testing • Functional • Recovery • Stress and performance • Usability

12. Quality assurance plan (2/2) • QA activities • Test-case-based testing • Exploratory testing • Continuous feedback from the customer • Project document review • Code reviews • Coding conventions • Refactoring • Static analysis methods • Automated unit and acceptance testing • Unit test coverage analysis • Pair programming • Regression testing

13. Quality dashboard

14. Quality goals

15. Defects

16. Software size in Lines of Code (LOC)

17. Changes to the project • Scope of the Sprint 2 have been reduced. • Touch screen functionality from dynamic to static. • Workspace view to Sprint 3 • Group member roles have been changed. • Tuomo and Toni have changed their course from 6 credits to 8 credits. • UI concept designers have been acquired from Design Foundation. • There will be development during Sprint 3.

18. Risks (1/2): TOP 5

19. Risks (2/2) • Risk log have been updated 2 times during Implementation 1. • Materialized risks • R15: Members not able to do assigned tasks • Esa was sick for quite long time • Actions: Scope had to be reduced and schedule was modified • R02: Effort estimation problems • Getting to know with tools and implementation have taken time a little more than expected • Actions: Scope had to be reduced

20. Results of the iteration • Technical specification • Demo

21. Technical specification (1/3)

22. Tech.spec.(2/3): Architecture

23. Tech.spec.(3/3): Data model

24. Demo • Admin & passive screen • Touch screen (static)

25. Used work practices • Keep • Joint meetings on Wednesdays • Team spirit • Active communication by email • Workspace at Design Factory • Cooperation with customer • Internal weekly announcements • Wiki (dashboard) is good tool to track progress • Dashboard! • Problems • Other tasks take time from this project • Lack of resources: time and developers • Mentor’s have to do some development themselves and therefore they can’t always help others • Selected tools are not that easy to adopt • Communication with peer group and UI concept designers • Try • Two developer days weekly • More cooperation with UI concept designers and DF usability designers • Another contact attempt to peer group • Old weekly announcements will be skimmed through during Wednesday’s meeting • Proposing issues to Wednesday’s agenda via Tuomo • Time tracking is done more frequently • Developer days in which Mikael concentrates only on mentoring

26. What’s next: Sprint 3 • Sprint 3’s themes are quality and integrity • Quality • Correcting identified bugs and enhancements • Performing user, acceptance and process testing • Usability evaluations and feedback • Creating Selenium and Unit tests • Putting CI server to real work • Integrity • Refactoring • Unifying module implementations • Coherent UI’s • Other tasks • Finalizing especially UIs • Implementing some new features but main focus is in quality and integrity.

27. Questions and comments? • Thank you!