Pallavi Monica Ekka
Speedy experience revamp proposal

Challenge

The current version of Speedy is built on features and developed without keeping a user-centered mindset. The interface is not intuitive and there were critical issues with data correctness and relevance of data.

Solution

The proposed solution looks at critical feedback from users and segregated based on different stages of a project lifecycle. It also lists some of the key features missing and a set of advanced experiences for Speedy.

The design comp added in this proposal tries to resolve some of the critical heuristic issues, key features and a consistent approach of displaying information across dashboards.

Collaboration & Co-creation

We realize that nearly anything really great in the world comes from a collectiv e of perspectiv es and coordinated effort, not from silos or isolated activ ity.

We brought together different teams using Speedy for a collaborativ e and co-creativ e workshop that enabled teams to contribute effectiv ely in minimal time for participatory design to address pain points and address solutions.

We used the activity Rose, Bud, Thorn to understand what’s working in the current product, what’s not, and areas of opportunity

Problem Statement

Identifying different user groups

Major Pain Points

  1. Current onboarding in a project is exhaustive and there is no clear guidance for the project admin
  2. Cannot assess the health of the sprint status easily
  3. The display of KPIs doesn’t give enough information for which the data was calculated and when it was collected
  4. Speedy KPI’s are not applicable to all programs
  5. The information available on the current dashboard is not enough to enable the user to make informed decision
  6. The current users are unable to track and assess their contribution to the particular sprint
  7. A high level comparative view between projects is missing in the executive dashboard

Extending the scope of Speedy

The pain points that we identified after the user interviews and workshops seem to be falling under different stages of a project. Users believe that Speedy can evolve into one tool which shows all the information necessary at each stage. To identify theseopportunities we went beyond the current scope of Speedy.

Pre-sprint

Features could be introduced in Speedy that could help the scrum master decide the scope of the sprint and help in resource planning and management.

During sprint

Speedy could be made more intuitive and insightful to help in quick and correct decision making.

Post-sprint

Features could be introduced in Speedy to help in retrospection of the completed sprint, release notes etc.

Scrum master Dashboard

Executive Dashboard

Feature List