•●• 2021 •●•

UX design in scrum environment



DEKRA a global partner for a safe, secure and sustainable world. This project regards the Audits division.

My role

Solo UX/UI designer responsible for the whole design process working within a scrum team consisting of developers, testers, business analyst, product owner and scrum master.


Internal processes redesign and automation project launched on the US market with plans for internationalization in 2022.

Design process in 2-week sprints

step 1


Each cycle starts with gathering requirements and business analysis. Before designing, we need to understand the current process. Its strong points and difficulties in order to find the correct problems to solve.

step 2


User testing is a valuable tool. Often you get surprised with the results. No one can tell you better if it works than the person that this solution is dedicated to.
A short summary of a test is available here - link.

“Oh, here the email’s title says ‘notification’ if I didn’t know to wait for it. I might have missed it.”

step 3


The first idea is never the right one, wouldn’t you agree?
This is when all the ideas are welcome; we experiment, learn, and validate, looking for the right solution before developers’ time is invested. We have a dedicated meeting called Refinement in Scrum that often happens online in tools like Mural or InVision to facilitate ideation on new ideas.

step 4


This step is owned by me. A reliable pattern library is a must to make it efficient and not hold back the team’s progress.

It’s not about constraints but getting it organized on the atomic level.
A well-built design system gives you the flexibility to be creative. Forms a baseline that incorporates all the conditions of accessibility, user interface interactions, and compliance with brand guidelines.

step 5


Consistency is key to creating intuitive user interfaces.
To ensure that happens together with developers, we have created a shared library consisting of all the basic building blocks of any interface, such as buttons, text styles, inputs, and interactions shared between design and code.
To store all this information we use Zeplin + Jira and Confluence.

step 6


One way to check their progress and their difficulties with the system is to track their movements using such tools as google analytics, Hotjar
recordings, funnels, and heatmaps - as shown in the example on the right.

All the data collected leads us to a new cycle of improvement.