Planning Iteration Demo Suunto Training Program Planner

imara AGENDA Introduction Project status Work results

imara Project context Business context Development context Adding value to new sports portal Important feature Third party development

imara PROJECT STATUS Goals and deliverables Resource usage Quality Assurance

imara Final iteration goals fulfilled Final product according to requirements High quality user interface Easy to use Graphically in line with Suunto design High quality code Internally: integration Externally: no known bugs Deliverables of high quality Some minor bugs still exist Two days of integration at customer site Customer constantly involved

imara All deliverables done Continuous Integration Final project plan Technical specification Quality Assurance report User's manual Final report Progress reports Written as an FAQ document All documents and source code delivered to customer All documents reviewed

imara Realization of the tasks No unresolved tasks

imara Resource usage We worked hard in Iteration 2 Almost all working hours used 1500 / 1539 hours worked

imara Project metrics Lines of code per week Approx Total Lines of Code Commits per week Approx. 18 Total number of commits 294

imara QA Practices Most important QA practices were Automatic unit and Selenium tests Explorative testing & heuristic evaluation Code reviews Peer programming Peer-group testing Continuous feedback from the customer Close communication and a supportive atmosphere

imara 11 Quality Goals All documented requirements have been implemented Unit test coverage good Functionality The feedback from the customer, peer-group and internal heuristic testing have been encouraging Innovative solutions Usability Unit tests are written Coding conventions are followed No blocker or critical bugs remain Code quality The layout is in line with mySuunto portal Layout has been approved Layout Implemented to all fields Localization Risks have been actively followed A lot of small changes/fixes towards the end complicated testing Risk management

imara Quality Dashboard Component Quality Status CommentsConfidenceReasoning Backend GOOD Unit tests have been written to all functionalities Automatic testing MEDIUM Unit test coverage has not been formally audited Frontend MEDIUM General feedback positive Innovative solutions Some minor adjustments remain GOOD Peer-group Heuristics Automatic Selenium tests Customer feedback Integration GOOD The backend functionalities work seamlessly through the frontend GOOD Tests have been designed to employ different layers of the software

imara Defects and Other Quality Metrics 55 unit tests written and all passing! 22 Selenium tests written and 20 passing! No blockers or critical bugs remain:

imara Testing Tools TargetToolUsed Create unit tests for all backend functionalities nUnit System and acceptance testing Selenium Continuous integrationCruise Control Listing of defectsJIRA Segregation of dutiesWeekly Meetings

imara Risk Management Risks were evaluated after each sprint Some risks materialized, but no major setbacks occurred Main problems and solutions Uneven workload  Less involved developers were given individual assignments Sickness and leaves  Reassigning tasks and planning ahead Unclear requirements due to iterative development  On-going and mutual dialogue with the customer

imara Changes Requirements have changed constantly One major change in requirements in the last sprint Small but constant changes in the UI throughout the project Late test results from the customer All major bugs fixed within two days

imara WORK RESULTS Demo of development environment Work practices used Reflection

imara Project Results Fully functioning software All customer requirements satisfied Almost 100 test cases Preliminary integration with the customer performed QA ideas delivered to the customer Ideas regarding third party applications delivered to the customer

imara Architecture Overview Training Program Planner DAL BLL SAL Presentation Layer SAL (stub) To be integrated...

imara WORK PRACTICES Demo of development environment Work practices used Reflection

imara Work practices used Pair programming Communication Process improvement Och en massa annat fint

imara Demo Demo för själva produkten är före denhär presisen Här kunde man demoa jira / ccnet / selenium / etc

imara Lessons learnt for the future What we learned To work as a team A new development environment What we will do better Blabla

imara Thank you for a well executed project!

imara BACKUP SLIDES

imara Iterative development plan Iteration (> 5 weeks) Sprint (< 5 weeks) Heartbeat (1 week) Week Iteration 1 Iteration 2Planning Sprint 1.1Sprint 1.2Sprint 2.1Sprint 2.2 Meetings with Suunto