1 / 27

Suunto Project Iteration 21 Agenda: Enhancing Usability and Collaboration

This document outlines the agenda for Suunto's project iteration on October 21, 2008. It highlights key goals, issues, and the progress made in terms of increased usability and customer value through advanced gadgets. The agenda includes discussions on collaboration with external developers, status updates on goals and deliverables, documentation creation, infrastructure implementation, and risk management. Additionally, it covers prototypes, testing processes, and team responsibilities, ultimately aiming to improve understanding of customer needs and enhance brand recognition.

jatin
Télécharger la présentation

Suunto Project Iteration 21 Agenda: Enhancing Usability and Collaboration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. T-76.4115 Iteration Demo Neula PP Iteration21.10.2008

  2. Agenda

  3. Introduction to the project Our Key issues Suunto’s goals Through gadgets Increased usability Value for customers Understanding the customers – Suunto and its users Brand recognition Understanding possiblities for sports web 2.0 Enabling external development High level of collaboration – as external developers

  4. Status of the iteration’s goals and deliverables

  5. Status of the iterations goals • Creating the documents • Documents finished • Creation of documents and the projects needs did not fit well together for us. • Implementing the infrastructure • Server rented • Programming environments set up • Testing and studying technologies done • Working practices tested and it works • Gathering requirements • Brainstorming – Analysis – Prototype descriptions • Understanding the problem • Research, testing, analysis • Prototype descriptions

  6. Realization of the tasks

  7. Realization of the tasks

  8. Resource usage

  9. Quality metrics • Work practices are working very well • Friday meetings • Friday and Tuesday working together • No disturbing communications problems • Requirements engineering picking up speed

  10. Changes to the project Requirements cycle • Requirements have had to be collected more rigorously than expected Iteration cycle Sprint cycle

  11. Changes to the project • Requirements engineering has been set into the schedule

  12. Risks • 10 risks have been identified

  13. Risks • Many of the initial risks have been minimized • Communication problems • Problems related to work practices • Technologies • Infrastructure • Some still exist… • Customer satisfaction • Also more uncontrollable ones…

  14. Results of the iteration • We already discussed: • Understanding the problem • Requirements process • Time logging and time tracking • Tasking • Schedule • Risks identified • Other: • Teams and responsibilities • Project management software • Wiki for status • Project goals • Tools • Prototype descriptions

  15. Results of the iteration - Teams

  16. Results of the iteration – Project management software • Neula.zoho.projects.com • Tasks • Time logging • timesheets • Documents • Forum • Meetings

  17. Results of the iteration - Wiki • TKK Wiki • Current issues • Work realized follow-up • Current Issues • Meeting memos • Contact information • Iteration Achievements

  18. Results of the iteration - Goals

  19. Results of the iteration - Tools

  20. Results of the iteration – Prototype descriptions • 10 pdf’s – using existing interfaces

More Related