Consult

A. Researching the main idea of ​​the project.

B. Exploring the high-level main goals of the project.

C. Identifying project stakeholders, including the hidden ones. Hidden stakeholders can be participants of a project interested in a client’s business who are not clearly represented to the team, that can be state and international regulatory authorities, public organizations, non-obvious participants influencing users of the service directly or indirectly, ​including others.

• Identifying stakeholders’ goals.
• Adjustment of high-level goals while taking into account the stakeholders' goals. In order to minimize differences in project vision and move in the right direction, it is critical for the team to clearly understand and share the client’s goals.

D. Determining all of the client's primary high-level expectations, which are known at this stage.

E. Vision synchronization of this unit with the client.

F. Identifying all User Roles and key User Stores.

G. Gaining access to industry insights from Computools experienced professionals to place you at a competitive advantage and minimize the risk of costly errors.

H. Building strong communication to ensure that everyone is on the same page that is essential to success. This is done by forming a glossary of project terms.

• Computools prepares agendas before each meeting and records results in a summary. This summary is shared to all team members in a general channel. This allows the team and client to save time and minimizes human factor and the negative impact of it.
• Сommonly-accepted terminology in the industry reduces miscommunication.

I. Forming a complete list of roles.

A. Creating user stories based on company knowledge and experience.

B. Researching competitors' existing solutions and technologies.

C. Researching the groups of client needs to clarify the best user experience.

D. Analyzing data, ready-made solutions on the market, their real (and not declared) pros and cons as well as who use them.

E. Decomposing user stories to user roles based on the results of research. Visualizing a tree of user roles, stories and cases via MindMap.

F. Defining main restrictions and providing solutions for them.

• system licensing and other legal requirements
• corporate policies
• localizations
• peak number of users online
• permissible downtime
• requirements to fail-safe feature
• requirements to scalability based on potential customer base growth
• requirements to system expansion speed
modularity extensibility code reusability
• requirements to delivery speed
release delivery speed speed of certain groups of fixes replacement speed of certain content or logic (often when using the admin panel or CMS)
• requirements to security level
system access security level level of software protection from solution-vendor (operating systems, application servers, VM, etc.) DDoS Protection Data encryption in storage User data protection Phishing Protection protection against unique content copying security analysis of third-party dependencies other additional options
• sizes and types of information that will need to be stored
• repository security requirements
• system response speed: average and minimum
common at certain critical points of the system
• list of end-user devices (device types, operating systems, input device screen extensions, etc.)
• server device list of client's business to which transfer may be required
• requirements to external protocols, formats and interfaces
• reliability requirements
logging backups
• system support features
logging testing (automatic, manual). It includes both coverage and speed of testing cycles
• domain specific restrictions and requirements
• general UI and UX design requirement

G. Identifying the main transitive requirements, such as migration, learning complexity and speed.

H. Identifying the main risks.