Working Methods
Our high competences are confirmed by implemented projects and numerous
references from our Clients.
Visit also
our portfolio
Working methods
We discover ideas and transform them into effective services and products. Our experts combine the most effective methods, such as Design Thinking, User-Centered Design, Service Design, as well as classic business analysis. In the production process, we often use Scrum and Kanban. We support the quality of the implemented applications (Quality Assurance) through functional and non-functional tests (performance, integration), as well as security tests (OWASP - The Open Web Application Security Project® methodologies and tools).
In order to ensure the best communication with clients, we use tools such as Jira, Confluence, Slack, Miro, Adobe XD, and Figma.
Design Thinking
We use DT to create products and services (such as applications, websites, and e-commerce). In the center of the project path, we place users and their needs, benefits, and problems. We convert this knowledge into questions, which then serve us as material in the process of creating ideas and solutions (ideation). As part of the DT path, we build prototypes of different levels of fidelity and test them with the participation of users. Our UX Researchers create usability reports in the CIF (Common Industry Format) standard with design recommendations.
During our joint UX workshops, activities are carried out:
- discovering user needs
- defining project challenges
- generating ideas and solutions
- prototyping and testing
Business analysis
Business analysis determines the needs of the organization and provides recommendations for solutions. In practice, we conduct meetings with internal stakeholders, analyze documents and materials, and conduct interviews with industry experts. The result is a document that covers two main areas.
Knowledge directly related to the organization:
- The company's strategy and business goals for implementing the project.
- The organization's structure (expert competencies) and flow of information.
- Business rules (company policy) that have an impact on the proposed solution.
- Key documents (templates) used to build the project.
- The expected end state of the project and success metrics.
- Glossary of terms.
Processes occurring using the platform:
- Actors and their needs (who or what will use specific system functions?).
- Which systems will the system collaborate with?
- Who requires support in their work and for which tasks?
- Processes occurring using the platform - system modules (presented in the form of UML notation).
Scrum
We typically use an agile work environment (Agile) - SCRUM to build solutions. Thanks to this, we organize work in cycles that do not exceed one month for each product area. These are usually 2-week sprints. The result of each sprint is a ready-to-implement increment defined in the sprint register. Thanks to the organization of work in Scrum, projects are created more efficiently, and clients can refer to the results of work almost in a live mode. This allows for current modeling of created solutions. Scrum is an environment focused on people and effective communication. At its core are openness, focus, and teamwork. It works perfectly in contracts based on a mixed Time & Material / Fixed Price remuneration model.
Kanban
The implementation of projects based on task flow using kanban boards allows for:
- 1 visualizing the entire process for continuous improvement of collaboration;
- 2 limiting work to the necessary scope;
- 3 easy measurement and optimization of the cycle of creating a fragment of the solution.
Kanban boards in Visual cover columns such as "To Do," "In Progress," "Code Review," "QA" (Quality Assurance), and "Done" (ready for deployment). Depending on the specifics, the issue can be a specific task, a user/business story, or a bug report. Similar to Scrum, Kanban is organized in the Jira system.