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.
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.
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
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.
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.
Speedy could be made more intuitive and insightful to help in quick and correct decision making.
Features could be introduced in Speedy to help in retrospection of the completed sprint, release notes etc.