Concept & Design

In my internship at IBM I worked in a team, which used Scrum as a project management methodology. The variety and unintegrity of the different software used, inspired me to recreate such an application and tailor it especially to Scrum teams.

Personae

The Product Owner

William O'Keele, 47 years old
Over 16 years management experience
Business & Marketing Background

The Product owner mainly concentrates on the vision and direction of the product. As being responsible for the business value of the company, he decides which features the product will contain and what the team will develop.

Goals

Trying to drive the product further and increasing the business value of the company, the product owner decides what to develop. He aims to produce the best functionality in a short time to outdo possible competitors. Also, he communicates with clients and stakeholders to held these customers and gain additional ones.

Tasks

He is the one responsive for the product roadmap and backlog. Adding, organising and prioritising user stories in the product backlog are some of his main tasks. Additionally, he approves user stories and pulls the key features into the sprint backlog. He
also needs to communicate the vision and goals to the Scrum team, so that everyone is aware of the future route. the product owner mainly uses the planning facilities of the product.

Usage Behaviour

Because of the fact that the Product owner uses Mercur to plan the product and monitor the current progress, he will use it as a reporting tool once in a while. Having other, more important tools for the day-to-day business.

The Scrum Master

Sharlene Tao, 36 years old
Certified Scrum Master of Scrum Alliance
In Project Management since 9 years

The Scrum Master acts as a facilitator for the Scrum team. in contrary to the Product owner, she does not have any management duties. She helps the team to overcome problems and makes sure that it stays productive and functional. in addition, she is vigilant about everyone following the Scrum rules.

Goals

As being the facilitator of the Scrum team, the Scrum Master wants to keep the team productive at all times. She also wants everyone to follow the Scrum rules and come to all meetings.

Tasks

Besides guiding the daily stand-up meetings, she also plans the other meetings in each sprint, including the sprint planning and review meeting, the sprint retrospective meeting and the backlog refinement meeting. the Scrum Master uses the calendar and meeting functionalities of Mercur. But also the reporting features
are of interest for this user. looking in the near future, based on calculations of the productivity rate of the team, the Scrum Mas- ter may be able to identify problems and initiate countermeasures early on.

Usage Behaviour

The Scrum Master spends most of the day using this product. She uses it as a main tool for planning meetings and to communicate with the team, in order to keep the team productive and fulfil her duties as a shield to the environment. Additionally she needs to communicate with the Product owner, so that he is always aware of the current status of the project.

The Team Members

Among others:
Beatrice Mouran, Software Developer
Peter Groban, Database Developer
Elena Tabor, Interface Designer
Michael Miller, Test Lead
Kaelan Walcott, Quality Assurance
Mary Steward, Tech Support

The team is a cross functional group of specialists with essential and complementary expertise. it usually consists out of four to nine people, with roles like Developer, Designer, Software Architect, tester, Quality Assurance and tech Support.

Goals

While the Scrum Master looks after the organisational aspects of the project, the team focuses on the product development itself. the Scrum team is self-organising and self-managing. it develops the user stories that are as- signed to the sprint by the product owner. the team itself decides how the stories are implemented.

Tasks

As being the user group that works daily with the product, a lot of features are especially geared to the team members. they use it in the everyday work environment and therefore it aims to fit in seamlessly in their job routine. Mercur combines a lot of functionality, including calendar
and day-planning facilities and the possibility to communicate with others. However one of the main benefits for the team are the time tracking and work monitoring features. the team members update user stories according the progress they have made, simply by clicking a button. At each point in time, they can monitor the progress steadily and also view its impact. the application supports instant reporting and displays information on the working progress, productivity rate and a burn down chart. calculations give the team an idea of the estimated completion date and already early on providence if the product can be delivered on time.

Usage Behaviour

The team will be using the product in parallel to their work. Mercur is a help tool to track activities and organise the working day. therefore it aims to provide easy to click functionality that does not distract the users, as they need to focus on their actual work.

Wireframes

Branding

R=104 G=195 B=247
#68C3F7
R=108 G=212 B=157
#6CD49D
R=236 G=76 B=55
#EC4C37
R=255 G=231 B=94
#FFE75E

Mock-ups

consights Branding & Website
Mobile Usability Research & Infographic

Get in touch

I look forward to hear from you.