T Iteration Demo Apollo Crew I1 Iteration

T Iteration demo 2 Agenda  Project status (15 min) achieving the goals of the iterationachieving the goals of the iteration QA planQA plan project metricsproject metrics  Work results (20 min) Technical specificationTechnical specification DemoDemo  Used work practices (5 min)

T Iteration demo 3 Introduction to the project Source: Dipoli entrance hall

T Iteration demo 4 Introduction to the project  Client: Design Factory  Project: Information & reservation system Welcome visitorsWelcome visitors Guide and assist visitorsGuide and assist visitors Manage eventsManage events Workspace reservation systemWorkspace 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.

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

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

T Iteration demo 7 Realization of the tasks: I1 Situation

T Iteration demo 8 Resource usage (1/3): Whole project Situation

T Iteration demo 9 Resource usage (2/3): Implementation 1 Situation

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

T Iteration demo 11 Quality assurance plan (1/2)  Quality goals QC1: FunctionalityQC1: Functionality QC2: UsabilityQC2: Usability QC3: Code correctnessQC3: Code correctness QC4: MaintainabilityQC4: Maintainability  Levels of testing UnitUnit IntegrationIntegration SystemSystem AcceptanceAcceptance  Types of testing FunctionalFunctional RecoveryRecovery Stress and performanceStress and performance UsabilityUsability

T Iteration demo 12 Quality assurance plan (2/2)  QA activities Test-case-based testingTest-case-based testing Exploratory testingExploratory testing Continuous feedback from the customerContinuous feedback from the customer Project document reviewProject document review Code reviewsCode reviews Coding conventionsCoding conventions RefactoringRefactoring Static analysis methodsStatic analysis methods Automated unit and acceptance testingAutomated unit and acceptance testing Unit test coverage analysisUnit test coverage analysis Pair programmingPair programming Regression testingRegression testing

T Iteration demo 13 Quality dashboard

T Iteration demo 14 Quality goals

T Iteration demo 15 Defects

T Iteration demo 16 Software size in Lines of Code (LOC)

T Iteration demo 17 Changes to the project  Scope of the Sprint 2 have been reduced. Touch screen functionality from dynamic to static.Touch screen functionality from dynamic to static. Workspace view to Sprint 3Workspace 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.

T Iteration demo 18 Risks (1/2): TOP 5

T Iteration demo 19 Risks (2/2)  Risk log have been updated 2 times during Implementation 1.  Materialized risks R15: Members not able to do assigned tasksR15: 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 problemsR02: Effort estimation problems  Getting to know with tools and implementation have taken time a little more than expected  Actions: Scope had to be reduced

T Iteration demo 20 Results of the iteration  Technical specification  Demo

T Iteration demo 21 Technical specification (1/3)

T Iteration demo 22 Tech.spec.(2/3): Architecture

T Iteration demo 23 Tech.spec.(3/3): Data model

T Iteration demo 24 Demo  Admin & passive screen  Touch screen (static)

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

T Iteration demo 26 What’s next: Sprint 3  Sprint 3’s themes are quality and integrity  Quality Correcting identified bugs and enhancementsCorrecting identified bugs and enhancements Performing user, acceptance and process testingPerforming user, acceptance and process testing Usability evaluations and feedbackUsability evaluations and feedback Creating Selenium and Unit testsCreating Selenium and Unit tests Putting CI server to real workPutting CI server to real work  Integrity RefactoringRefactoring Unifying module implementationsUnifying module implementations Coherent UI’sCoherent UI’s  Other tasks Finalizing especially UIsFinalizing especially UIs Implementing some new features but main focus is in quality and integrity.Implementing some new features but main focus is in quality and integrity.

T Iteration demo 27 Questions and comments?  Thank you!