How is the task approval process built with the client

Today we will talk about how the receipt, distribution, approval and execution of tasks in our company takes place. At the first stage, the customer, together with our manager, determines the development team. Such a team is formed at the request of the customer and depending on the needs of the project. As a rule, the development team consists of a business analyst, team leader, project manager, frontend developers, backend developer, designer and tester.

At the first stage, when a full development team is formed, it is necessary to check access to the project and to all resources that are necessary for stable and productive work. At the second stage, we need to get a task from the customer. The task is formed at the stage of direct communication with the customer. First, the business analyst and project managers discuss with the customer his vision for the product and the deadlines for the work. At this stage, the business analyst will discuss and tell you how best from the business side to perform the tasks that the customer would like to see in his web application. Next, the business analyst at a meeting with the project manager will discuss the client's task and divide it into specific tasks for the development team. Then this task is processed by a business analyst and a project manager. They draw up a development plan, a project description, and initial documentation.

Our company uses Scrum and Kanban methodologies as Agile (flexible) methodologies. The Scrum approach is used on most projects. This means that the project manager or business analyst fills in the project backlog, where all the tasks that need to be completed during the implementation of the product are located. The next step is to set time intervals (usually one or two weeks) during this period of time, the development team performs tasks and closes the sprint, and after that the date of the demo is assigned to the customer for the work done for this sprint.

These diagrams help not only the customer to understand the product and evaluate his expectations from the product, but also the development team will follow these documents and not deviate from the tasks and flow of the designed web application. Also, this type of interaction between the user and the system, which is described in the diagrams, will help at the development stage to create exactly the kind of product that was originally ordered by the client.After approval and provision of documentation for the project to the customer and the team, as well as familiarization of the customer with the created tasks, the process of product development by the development team begins. A sprint is formed and scopes of tasks for the sprint are selected. After that, the process of prototyping and design begins, which will later be approved with the customer and implemented by the development team. A repository is being created for the backend and frontend parts of the application. It also installs the necessary dependencies and libraries, configures CI/CD, and creates invites for the product (development and production). After the task is implemented directly, which contains the functional part and corresponds to the design layout, the pull request opens (pull request is the stage when the developer has completed the task and is ready to provide his developments to a competent specialist who will review the written code. In case of any comments, the developer will correct them.). After that, the pull request goes through a merger process, namely, at the development stage of the project, there are several project development environments, often development and production. After the developer has completed the task, he sends his developments directly to development. After the task is completed by the developer, and the developments are sent to development, the task testing stage begins, after which this task is already sent to production, where the customer can also see it.

After the sprint ends and the completed tasks are in production, the completed tasks are shown by the team leader or project manager to the customer. After the demo, the customer can see at what stage the product is being implemented, express ideas and constructive criticism, if any. After that, a sprint retrospective is held, in which the entire development team participates and shares their impressions, or expresses an opinion on improving the development stages. Next comes the stage of evaluating and taking tasks into a new sprint, at the end of which the entire process described above takes place.

In conclusion, I would like to note that the key to a successful project is a well-chosen company that will provide a full cycle of development of any product, provide a brief guide on the use and maintenance of an already implemented project. Do you want to work with us? Fill out the feedback form https://www.it-justice.com/contacts . Thank you for your trust! We will contact you within 2 hours.