Work organization in Ankora

Work organization within the project is based on Scrum. It is a framework that consists of iterative and incremental attitude towards troubleshooting complex issues. It allows delivering a product of the highest possible value in a productive and creative way. Within this framework, the process of delivering a product is separated into smaller iterations called Sprints, which facilitate rapid and suitable reactions to changes that accompany the development of this product. Every Sprint may be considered as a new project whose duration should not exceed one month and which should lead to achieving the Sprint Goal. The final result of every Sprint is always a “Done”, usable, and potentially releasable Product Increment. Such a solution helps to build a highly-developed model of information transfer that includes solid control of the whole process upheld by three pillars: transparency, inspection, and adaptation. To find out more about the Scrum framework, please visit:

Following product changes

Every product has its Product Backlog – an ordered list of everything that is known to be needed in it (features, functions, requirements, enhancements, fixes). The realization of items included in the Product Backlog can be easily followed by the deployment of Project Management Tools such as Taiga, Jira, Trello or Pivotal Tracker. They allow creating a board divided into several stages. While the position of tasks switches from one stage to another, it is anything but difficult to trace their progress from “To do” to “Done”. Each item of the Product Backlog has a sequence number and assigned subtasks if needed. It facilitates and simplifies task identification.

QA Process

● Review of requirements

● Test planning/writing test cases

● Unit testing

● Integration testing

● System testing

● Performance testing

● Cross-browser testing / cross-platform testing

● Updating test cases

● Regression testing

Key benefits for the development process:

● Errors cost less when detected at an early stage.

● Improved documentation means a higher quality project for lower labor input and more accurate estimates.

Everyday Communication

For everyday communication, we use the following tools:

• ● Slack – for discussing current issues and problems;

• ● E-mail – for sharing important information and agreements. While running a project we have to share various data types, which is why we create certain channels on slack so they can serve different purposes:

• ● “Daily” – sharing short notes summarizing Daily Scrums. The message always has the same scheme (A daily message related to an RPA project may also include short videos in order to enable a better understanding of the project’s progress)

Summary

We hope that this document will help you get acquainted with the way we work. We strongly believe that following the rules specified above will allow us to maintain efficient communication, which is extremely important to achieve transparency in terms of our cooperation. As we are aware of the uniqueness of each project and the fact that there is always room for improvement, we are ready to adjust our methods of communication and tools that we use to meet the expectations of our Clients.

Regular meetings

The heart of the Scrum framework is a Sprint, that consists of all the other Events. There are three statute meetings where the presence of the Client is required:

● Sprint Planning – it includes determining the Sprint Goal and planning the work to beperformed in the Sprint.

● Sprint Review “Demo” – it is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed. During the Sprint Review, attendees collaborate on the next things that could be done.

● Sprint Retrospective – it is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.

Additionally, the whole Development Team takes part in a Daily Scrum, where the presence of the Client is not required. It is daily, 15-minute time-boxed meeting, which serves planning the work for the next 24 hours. This optimizes team collaboration and performance by inspecting the work since the last Daily Scrum and forecasting upcoming Sprint work.