Introduction

in this chapter, you will learn about the overall digital product manufacturing process and the outline of the Design Process concept in SYNAOS.

You will learn what kind of events are in the process and what roles are involved in the product development cycle.

Let’s explain the first high-level vision so that you can understand the concept easier and we will move on to the principles and details of the Process Design.

 

Standard Product Development Process (High Level)

 

 

To start the topic of roles, and events it is necessary to explain the entire development process of the digital product. Sometimes it is a complex and time-consuming process involving different roles in the organization (depending on the Organisation Level Strategy).

Each role has its own task, and usually has a different area/section replaced inside a process. Third parties, e.g. customers or potential users of the application, may be involved in the product development process to verify assumptions or test delivered tasks. The entire digital product development process is usually adapted to the characteristics of the organization, industry, and roles in the organization.

Organizations are forced to create their own process and product development cycle so that engineers, managers, technical, product owners, designers, testers can deliver the finished product to the market in an orderly and faster way.

 

 

Product Development Process Events

 

Design Phase

The design phase is a complex process of creating the vision of a project, module, component, or functionality. Usually, it starts with understanding the needs or getting to discover the problems of users or clients. Inside this phase, designers verify assumptions made and the final presentation of the project that will be handed over to front-end developers for implementation.

Design Phase

The design phase is a complex process of creating the vision of a project, module, component, or functionality. Usually, it starts with understanding the needs or getting to discover the problems of users or clients. Inside this phase, designers verify assumptions made and the final presentation of the project that will be handed over to front-end developers for implementation.

Development Phase

The process of transferring the Designers’ vision to real code and delivering the final version of the digital product or ticket/request to the testing phase. The work will result in delivering a working product for a testing phase.

Validation Phase

The phase in which the work is tested and the team measures user satisfaction. Different roles may be involved in this phase depending on the size of functionality and end-use. If we find bugs or new ideas arise in this phase, the work can return to the previous phases to correct or update the product. Product Owners should verify this on every iteration cycle and in every phase.

Rollout/Delivery Phase

This event takes place when the product or its functionality has passed the tests and it’s ready for the next release. Usually, Product Owners and Businesses decide when the company should release our work. The other roles can be involved in this phase. It’s good to understand that it’s a fully iterative process and even if we deliver something we can back to this in the next few weeks which change requests or new upgrade tickets.
The process of transferring the Designers’ vision to real code and delivering the final version of the digital product or ticket/request to the testing phase. The work will result in delivering a working product for a testing phase.

Validation Phase

The phase in which the work is tested and the team measures user satisfaction. Different roles may be involved in this phase depending on the size of functionality and end-use. If we find bugs or new ideas arise in this phase, the work can return to the previous phases to correct or update the product. Product Owners should verify this on every iteration cycle and in every phase.

Rollout/Delivery Phase

This event takes place when the product or its functionality has passed the tests and it’s ready for the next release. Usually, Product Owners and Businesses decide when the company should release our work. The other roles can be involved in this phase. It’s good to understand that it’s a fully iterative process and even if we deliver something we can back to this in the next few weeks which change requests or new upgrade tickets.

 

 

 

Roles

User

It is one of the most important roles in the development cycle. Why? Because the company’s success depends on how effectively users use the product and whether the problem of users/clients are solved. Before each creation of solutions, it is worth asking who I am doing it for and what is the real value that I can bring to the people who will use it. The user is not always the customer who bought the product or who is a sponsor.

Remember: Remember: Listen to this role because it will tell you if your solution solves their problem, is it easy to use your functionality or interface, and did we meet the user’s expectations. Don’t try to be an advocate of the user if you are part of the organization or you are involved in the development process. Validate your ideas only with real users.

Client / Sponsor

This is a role or organization which is responsible for the business aspect of the organization to which the product goes (usually on the business and user’s needs). Sometimes a client has an own Product Owners who define direction with Development Team. In the product production cycle, this role may determine the direction of product development in the coming months. In the Development Process Cycle, the representative of this role should initiate or end a process. At the beginning of the cycle, Client should

 

UX Designer / UX Researcher

An extremely important role that makes sure we have a good understanding of the problems, collect requirements, verifies what is important for this phase, and propose and validate the useful solutions. UX Designer also focuses on choosing the right techniques and testing your assumptions in order to empathize with the user at an early stage and choose the most convenient solution.

Its position is mainly placed in the first half of the entire Design Process. Works closely with business, users, and UI Designer.

 

UI Designer

This role is responsible for how the final product will look. UI Designer focuses on colors, typography, contrast, accessibility, user micro-interactions so as to display information to the user in a better & easier way for their user. The most common roles he/she works with are UX Designers and Developers.

UI Designer supports the final work of the UX Designer in order to improve the final outline of the concept and then goes to design. Usually, it works on a certain standard so that the designed components are consistent with other components in the application. After his work is approved, he prepares application views for Developers to improve their work. Process Handoff is individual and may be different depending on the task.

 

Front-end Developers (UI Developers)

Front-end Developers, sometimes also known as UI Developers. They usually have the same knowledge and skills as UX / UI Designers. They are responsible for the implementation of the ticket/requests provided by UI Designer. They combine the logical layer with the design layers to create functional and final working functionality, component, screen, or product. In the case of reported bugs, they also fix them directly in the code.

 

Testers

It is not always a dedicated role, it can be, for example, any other role in the product development process that understands the assumptions of the work and the final vision. Testers can report bugs or deficiencies or suggest improvements. Then the functionality or product can go back to the previous phases. Mostly Product Owners should devise about this.

 

Product Owner

And depending on the specifics of the work, this role has the necessary knowledge about the requirements and decisions agreed with the Client/sponsor. The second important activity of Product Owners is the verification of work progress so that they can inform other roles or the client about the progress of work and about issues.

Product Owners can be in direct contact with other Product Owners from the client’s side, with whom they set up a product roadmap for the next phases. It’s good to add that Product Owners should have knowledge about users and feel the product. They have one of the greatest influences on the decision-making process.

 

Backend Developers

Technical engineers responsible for maintaining all information logic and other application layers (not visual). So that the system can properly aggregate data and use it by Front-end Developers.

Remember: There are no stupid questions, only stupid answers. Therefore, do not be afraid to ask questions. You have the right to ask and drill. Your goal is to understand customer requirements and what we really need to deliver. Don’t go into details, ask general questions that will allow you to reach your goal faster.