Create a software for managing and monitoring projects and tasks within a team.
In this project I present the complete cycle for the realization of this technical test, using project management metrics, UX and UI design.
Set permissions for each team and its members (HR employee responsible for setting the employee’s permissions in the software);
Set possible options for the Team Manager (Evolution, status and execution of tasks of the employees in your team);
Options to change/add due date, task status, responsible employee and task assignee, to which project it is associated, and task description.
In the problem presented, it is considered beneficial to use the Agile methodology to proceed with the development of the proposed product.
In this specific case, for coordination and task monitoring of the statement, the following metrics (common in Agile planning) were used in the construction of the software:
- Task manager
- Task Assignee
- Name of the associated project
- Deadlines in the Sprint
- Choice of priority (Low, Medium and High)
- Task duration (Story points – defined in the planning of each task in the sprint)
- Detailed task description
This was the moment to define some important metrics to understand the value of the project.
At each point it is explained in a straightforward way what is intended.
- What are the goals of the project?
- For whom?
- What are the success metrics?
At the beginning of the project, and after observing the objectives, the use cases were defined. For this point it is important to discuss which personas will be able to use the software and what are the main activities they will be able to perform in it.
A competitor analysis was performed. The goal with this type of analysis is to match a UX law.
Users spend most of their time on other sites, so they prefer your site to work the same way as all other sites they know.
With this we realize that, in a complex platform, keeping some common similarities with competitors may improve usability and user interaction.
- Often used for product teams and developers;
- Integration with development/programming and design, analysis and research tools to build a product;
- Collaborative between teams in a company;
- Possibility to define the “Due date” in each project and each task;
- Generally used for various types of industries and business models;
- Integration with development/programming and design, analysis and research tools for building a product;
- Can assign “Due dates” to each individual task and sub-task.
To jump into the final visuals a choice of color palette, font and Scale Units was worked out.
Here, the ideas were put together in their respective wireframes, in order to correspond with the UX research and analysis done.
Kanban board to visualize the tasks and their overall status
Screen where you can view the details of a task
A pop-up screen where you can edit the task’s progress, add documents, and comment.
In the final stage the visual design was prepared according to the UX research, style guide and partly the wireframes. From the wireframes to this elaboration, certain parts were changed in order to obtain more detail and usability.
All the screens, modals and parts were made with Autolayout in figma.
All spacing has been taken into account, based on the 8px scale.
From color contrast for better accessibility, to layout correction, to using current design metrics, to prototype animation.
What did I actually find out?
Even though this project was short and very straightforward, I realized how complex each step can be, the need to always go back to review requirements is very important, which made me realize how focused we have to be, to always know what the goal and final destination is.
Personally, I summarized that this project reinforced my particular taste for building dashboards and products in this area, but also the way I like to be present in all the steps and stages of a product like this.