Product Manager

The product manager collects all necessary data for the team, communicates with a stakeholder, indicates the budget for the project during the Discovery Stage. He is the main person, who communicates with the client.

Main responsibilities

• • Coordination of all communication for the project;
• • Financial and time restrictions monitoring during the Site / Flow Map stage at the Discovery phase;
• • The product manager serves as an escalation point .

UX Analyst

UX Specialist is required when you have the some understanding of your product (vision, general navigation) but can’t imagine how exactly it should look like and think through all the details.

Main responsibilities

• • UX Consultation;
• • UX prototyping;
• • Customer journey Map/ User flows building;
• • Research;
• • Competitors analysis.

Product Concept

At the Product Concept Stage we create detailed descriptions for all business goals of the project, structurize major workflows.

We collect all functional and non‐functional requirements for the project which provide insights for understanding the context and starting the development.

SWOT / Research

This phase is needed in order to synchronize expectations and understanding between the client and the team.

The main goal of this Step is collecting and analyzing information about the project, acquaintance with the project and its needs, its intended market, target audience their understanding of the needs, wants, attitudes, expectations, and frustrations of project consumers and prospective customers.

In accordance with clients need and information that is available for the Project we offer two approaches: if there is no information about the Project and its competitors – we use the Research stage – stage with searching data and information for the project. If the list of competitors is available – we use SWOT – collection and systematization data for the project.

Sitemap / Flow Map

For a competent and more accurate Estimation for the project, it is obligatory to understand the scope ow work and the size of the project.

There are two ways to this:
Flow map – measure the volume of work only for a certain flow. Sitemap – when the entire project scheme is created including the pages scheme.

The completely full Flow or Site Map couldn’t be created without previously collected relevant data and information for the project.

Estimation for the Project

At this stage, the client got the itemized Estimate, which allows our client to see the exact price for every Screen, Page, Feature.

During planning the funds for every aspect of a project, the Client reduces the risks of such hidden surprises as additional costs.

On the discovery phase for a software project, our team together with the Client decides on the most suitable technology stack and core features for the development stage of the project.

Project Plan

At this step, all data and available information, that has been received before are converted into to ready-made action plan.

All information that our team grabbed before this stage we will transform at the:

• • A detailed description of the project needs;
• • Project plan;
• • Information due to planning costs and activities during the whole project;
• • Approach for this current project;
• • Decomposition for the development and design team.
• • Project milestones;
• • Project deliverables.

Product Manager

The product manager collects all necessary data for the team, communicates with a stakeholder, indicates the budget for the project during the Discovery Stage. He is the main person, who communicates with the client.

Main responsibilities

• • Coordination of all communication for the project;
• • Financial and time restrictions monitoring during the Site / Flow Map stage at the Discovery phase;
• • The product manager serves as an escalation point .

System Architect

System Architect is required for the synchronization between the client and his business goals.

He composes all information in that way, that the project will be available to start and everything looks cool and your team can get to work.

Main responsibilities

• • Gathering of requirements;
• • Conduct an analysis of possible solutions and technologies;
• • TDD creation or provide the basic structure (scheme) of a project;
• • TDD and scheme creation into tasks;
• • Plan and Estimation creation;
• • communication with Stakeholder(s).

Product Concept

At the Product Concept Stage we create detailed descriptions for all business goals of the project, structurize major workflows.

We collect all functional and non‐functional requirements for the project which provide insights for understanding the context and starting the development.

Project Architecture

Architecture for the project – this is a step that couldn’t be missed.

The architect takes part in the processes of collecting and analyzing the requirements for the developed project. Depending on the project, the architect oversees the overall architecture, API ( if any) and also makes the development of project and program documents.

Research for the Development

During this stage, the team spends time to get acquainted with different technologies and in order to determine the best solution for the project, as well as get acquainted with the project documentation.

Even the proposal for the project is based on data from the Research Stage: which technology will be the most beneficial for the client, and also will not be outdated for the market, and will make it easy to scale the project.

The stage allows the team to understand the crux of the matter for this particular project, and build a plan for further actions.

Product Roadmap

Product Roadmaps helps to visualize all project steps in one place. This is the custom, step-by-step plan for our clients’ product is going to meet a set of business objectives.

The product management team in Rondesign prioritizes incoming ideas to make sure the roadmap aligns against the business goals.

Own Product manager is on the lead the roadmapping process but seeks cross-functional input from the development team, sales, marketing, and the executive team to ensure that the plan will deliver against the Project.

WBS

WBS is entire project volume of the project decomposed by tasks.

“If the task is not in WBS – it is not in the project” it is our main criteria for all tasks of the project. Custom made WBS helps organize projects correctly, helps to distribute responsibilities and split up the for in the right way. This is one of the most important and useful documents for the project.

Code Review

Code review – often done as part of enterprise projects, less often as part of startups and small and medium-sized businesses.

When there is a huge amount of legacy code on the project – and you need to review it and decide what technologies you can use with it at the next stages.

Product Manager

The product manager collects all necessary data for the team, communicates with a stakeholder, indicates the budget for the project during the Discovery Stage. He is the main person, who communicates with the client.

Main responsibilities

• • Coordination of all communication for the project;
• • Financial and time restrictions monitoring during the Site / Flow Map stage at the Discovery phase;
• • The product manager serves as an escalation point .

UX Analyst

UX Specialist is required when you have the some understanding of your product (vision, general navigation) but can’t imagine how exactly it should look like and think through all the details.

Main responsibilities

• • UX Consultation;
• • UX prototyping;
• • Customer journey Map/ User flows building;
• • Research;
• • Competitors analysis.

System Architect

System Architect is required for the synchronization between the client and his business goals.

He composes all information in that way, that the project will be available to start and everything looks cool and your team can get to work.

Main responsibilities

• • Gathering of requirements;
• • Conduct an analysis of possible solutions and technologies;
• • TDD creation or provide the basic structure (scheme) of a project;
• • TDD and scheme creation into tasks;
• • Plan and Estimation creation;
• • communication with Stakeholder(s).

Product Concept

At the Product Concept Stage we create detailed descriptions for all business goals of the project, structurize major workflows.

We collect all functional and non‐functional requirements for the project which provide insights for understanding the context and starting the development.

Research for the Development

During this stage, the team spends time to get acquainted with different technologies and in order to determine the best solution for the project, as well as get acquainted with the project documentation.

Even the proposal for the project is based on data from the Research Stage: which technology will be the most beneficial for the client, and also will not be outdated for the market, and will make it easy to scale the project.

The stage allows the team to understand the crux of the matter for this particular project, and build a plan for further actions.

Sitemap / Flow Map

For a competent and more accurate Estimation for the project, it is obligatory to understand the scope ow work and the size of the project.

There are two ways to this:
Flow map – measure the volume of work only for a certain flow. Sitemap – when the entire project scheme is created including the pages scheme.

The completely full Flow or Site Map couldn’t be created without previously collected relevant data and information for the project.

Wireframes

This step facilitates the process of synchronizing of the team, client, development and project management teams -because they see the same one task and same functionality.

Wireframes help the client to solve the following tasks:

Сheck the logic of the ideas and functionality of each page/screen. Create a Clickable prototype which helps to check the navigation Make the user-test of the interface to let users identify logical issues. Understand whether the customer’s idea works well and clear for users.

Only Wireframes – helps to understand the full functionality for the project, because it shows it in the most detailed way.

Clickable Prototype

A clickable prototype identifies errors in the architecture before the start of development, as well as the whole team can easier test it, and it is possible to conduct user tests before the even start of development.

Clickable prototyping is a step that helps our client with the validation of their ideas beforehand. The clickable prototype also is a good decision when the client would like to implement a new platform at their business.

Visual Concept

We create a style or design system that not only meets the needs of the project but also is thoughtful for this particular project in terms of functionality, and it is easily scalable.

At this stage, we combine not only the Prototypes that were made previously but the data and information that has collected at the previous Stages.

Estimation for the Project

At this stage, the client got the itemized Estimate, which allows our client to see the exact price for every Screen, Page, Feature.

During planning the funds for every aspect of a project, the Client reduces the risks of such hidden surprises as additional costs.

On the discovery phase for a software project, our team together with the Client decides on the most suitable technology stack and core features for the development stage of the project.

Project Plan

At this step, all data and available information, that has been received before are converted into to ready-made action plan.

All information that our team grabbed before this stage we will transform at the:

• • A detailed description of the project needs;
• • Project plan;
• • Information due to planning costs and activities during the whole project;
• • Approach for this current project;
• • Decomposition for the development and design team.
• • Project milestones;
• • Project deliverables.

Project Architecture

Architecture for the project – this is a step that couldn’t be missed.

The architect takes part in the processes of collecting and analyzing the requirements for the developed project. Depending on the project, the architect oversees the overall architecture, API ( if any) and also makes the development of project and program documents.

Product Roadmap

Product Roadmaps helps to visualize all project steps in one place. This is the custom, step-by-step plan for our clients’ product is going to meet a set of business objectives.

The product management team in Rondesign prioritizes incoming ideas to make sure the roadmap aligns against the business goals.

Own Product manager is on the lead the roadmapping process but seeks cross-functional input from the development team, sales, marketing, and the executive team to ensure that the plan will deliver against the Project.

WBS

WBS is entire project volume of the project decomposed by tasks.

“If the task is not in WBS – it is not in the project” it is our main criteria for all tasks of the project. Custom made WBS helps organize projects correctly, helps to distribute responsibilities and split up the for in the right way. This is one of the most important and useful documents for the project.

Code Review

Code review – often done as part of enterprise projects, less often as part of startups and small and medium-sized businesses.

When there is a huge amount of legacy code on the project – and you need to review it and decide what technologies you can use with it at the next stages.