This challenge is the result of a “learning by doing” process within the Like A Coffee Community, a team work carried out with other Junior talents and mentors of this community. After the first training courses, we have activated a process of inspiration and design and we have come to the definition of this and other challenges. The aim we had during its development has always been to learn new aspects of data science and at the same time find a practical application in the @LAC model.
The theme of this challenge was born within the experiences of design thinking and project management that we usually face in projects. The importance of writing a correct user story concerns not only the project owner but also the designer and the developer. Having correct and well written user stories improves the quality of communication between all those involved in the project during its development.
Datawarehouse and Data Science are two hot topics in the world of programming, their presence is increasingly in demand, and it is precisely from this that the idea of this challenge was born.
The scope was to create an algorithm capable of recognizing the activity labels of each time entry and using this as an objective,and meanwhile, to create a database capable of containing those entries in a single environment, which brings together all the different sources currently in use in our community.
To achieve this goal we have created a series of algorithms that will be briefly described in this paper, starting with the decision of the database to be used, then moving on to the study of data, analysis and cleaning of the latter, and finally actually build one or more clustering algorithms, which were able to assign a label to each entry.
We understood that creating a textual clusterization algorithm, when the textual content is so large, is not an easy task to complete, but the result seemed very pleasing to us.
This paper follows our line of thought as we developed the project, highlighting our doubts and certainties. Our study noted the difficulty in developing an application of this kind, but also how useful it was to our training, which in the end was what we were aiming for.
In our daily work we use Asana as our project management tool which includes information about teams, requirements, tasks, issues and different data associated with them.
We combine project management with information storage on Google Sheets to manage in depth information about different issues in a project, for example, bug reporting, testing reports etc.
And we use the Miro application to manage the design and ideation process. Now we have started to integrate all of this information from multiple platforms into the digital whiteboard (Miro).
In a company, if all projects are managed in a similar way, then it reduces time necessary to get used to every new project. The way I see it, it is all about expectation management. All the involved parties know what they are getting with unified project management style.
While creating and managing QA processes we ended up using many different tools and it is time consuming for everyone involved to keep track of changes across multiple tools, therefore we were looking for a simplified way of presenting all the necessary information in one place. Also, since most people retain visual information better than written information, Miro board became a great solution since we can display and group content visually.
“Asana Cards” app allows us to import Asana tasks and display them on the board. These cards can be filtered by projects, assignees, sections, allowing us to easily group them in a desired way.
“Google Drive” app allows us to import different documents from Google Drive. This allows us to create extensive reports and graphs in Google Sheets and then display this document in the Miro board, locked on the desired sheet to show necessary information. Also we can edit the imported Google documents from Miro board itself, without switching to a different tool.
For project status calls we use a specific project related Miro board. In this board there is an overview of the project – current and past sprints, overall project statistics, open issues, next steps.
Currently we have been creating written meeting protocols for every status call. We hope to replace these text documents with engaging, visual, easy to understand digital whiteboard which gets continuously updated to reflect the current situation of the project.
The opportunity to have the information in a whiteboard allows us to have a wide and comprehensive view of all the content related to the current project. Both to have a history of the project that has a graphic visualization, and to have more schematization and synthesis when sharing information