gsi-general softwareinc company
CONTACT US

How We Work

With your priorities in mind, we have designed a sequence of steps to achieve your goals. Let’s go over them. Do you want to learn more?

BOOK A FREE CONSULTATION

Our Business Partners

vertrax
blueliv
couchbase
goheavy
kahua

Why Work With Us?

Dedicated individual immersed in software development, focused on creating innovative solutions
  • Direct and effective communication. You know at which stage your project is at every step of the way.
  • Agile development methodologies and best practices allow handling changes and incorporating new project requirements according to your demands.
  • Continuous integration and delivery of new and relevant features at the end of each iteration. Changes are welcome and handled together.
  • Short development cycles for delivering results.
  • Flexible size teams to meet the needs and priorities of your business.

Project Definition

First thing, let’s agree on your project, its timeframe, and budget.

1-2 Iterations
  • Iterations
  • Understand the complexity of the project.
  • Narrow the scope of the project.
  • Establish the goals.
  • Client
  • Project Manager
  • Business Analyst / Requirements Engineer
  • Developers
  • A time frame to deliver version 1.0 of the project’s MVP.
  • List of identified risks and measures to be taken to mitigate them.
  • Real-Time Communication Platforms (GotoMeeting, GoogleMeets, Zoom, Microsoft Team), Google Docs.

Let's journey together through the project's stages

Planning

Goal:

  • Agree on the set of features to implement in the iteration.

WorkFlow:

  • Planning meeting with all the stakeholders, including the client. Only once in the cycle. The purpose is to choose the functionalities to implement and clarify any doubts. It also helps to align the client’s expectation with the project team’s understanding of the project.
  • Daily review meetings, Monday to Friday, to focus on the accomplishments of the previous day, the work on the current day and discover blockers.

Involved:

  • Client
  • Project Manager
  • Project team (Requirements Engineer, Business Analyst, UX / UI Designer, Developers, Quality Assurance / Test Engineer, Deployment Engineer).

Expected Results:

  • List of functionalities to develop in the iteration.
  • List of identified risks and measures to take to mitigate them.

Tools:

  • Real-Time Communication Platforms (GotoMeeting, GoogleMeets, Zoom, Microsoft Team), Google Docs. Applications for project management (Jira, Redmine, TFS)

Goal:

  • Describe in natural language (understandable by you and the development team) the client's expectations in each of the functionalities to be implemented in the cycle.
  • Update list of system functionalities that will be developed in future iterations.
  • Design the UI taking into account the best UX practices for solutions on different platforms (Mobile, Tablet, Web, Desktop).
  • Design the architecture proposal for the implementation of the system

WorkFlow:

  • Meetings of the project team on demand.

Involved:

  • Project Manager
  • Project team

Expected Results:

  • User stories of the functionalities to be implemented in the development cycle.
  • List of system functionalities updated with future functionalities to be implemented. ●High-level UI design for the system platforms.
  • High-level UI design for the system platforms.
  • Description of the architectural solution to be followed by the development team.

Tools:

  • Design tools (Figma, Adobe XD) Google Docs, Applications for project management (Jira, Redmine, TFS)

Goal:

  • Develop the functionalities chosen in the iterations.

WorkFlow:

  • Planning meeting with all the stakeholders, including the client. Only once in the cycle. The purpose is to choose the functionalities to implement and clarify any doubts. It also helps to align the client’s expectation with the project team’s understanding of the project.
  • Daily review meetings, Monday to Friday, to focus on the accomplishments of the previous day, the work on the current day and discover blockers.

Involved:

  • Project Manager
  • Developers (FE, BE, Mobile) and Quality engineer.

Expected Results:

  • Solution that fulfills the user stories defining the functionalities for the current iteration.

Tools:

  • Mobile Tools, Unit tests, Applications for project management (Jira, Redmine, TFS)

Goal:

  • Evaluate the quality of the product to be delivered to you to guarantee that it complies with the functional and non-functional requirements agreed in the planning activities between the client and the project team.
  • Develop the manual and automatic test plan to be executed in the iteration.

WorkFlow:

  • Report each defect found in the execution of the test plans. Notify the developers for their correction in the development cycle.
  • Regression test to each of the bugs fixed by the developers.

Involved:

  • Project Manager
  • Developers (FE, BE, Mobile)
  • QA / Testing Engineer

Expected Results:

  • Test plan for each of the functionalities to be developed.
  • Features that meet customer expectations described in user stories.

Tools:

  • Applications for project management (Jira, Redmine, TFS)

Goal:

  • Integrate the functionalities developed in the cycle in a staging environment to evaluate their quality before they are released.
  • Have your feedback as early as possible on whether the implemented features meet the requirements agreed in the user stories.

WorkFlow:

  • Meeting to review the result of the work iteration. Only once in the cycle.

Involved:

  • Project Manager
  • Account Manager
  • Project team

Expected Results:

  • System functionalities approved for deployment in the production environment.
  • List of change requests for improvements or defects you found in the functionalities delivered.

Tools:

  • Real-time Communication Platforms (GotoMeeting, GoogleMeets, Zoom, Microsoft Team), Google Docs, Applications for project management (Jira, Redmine, TFS)

Goal:

  • Deploy the approved set of features to the production environment.
  • Test the deployment in the production environment to ensure that the previously deployed features were not affected.

WorkFlow:

  • Once the code is released into production, smoke tests are performed by test engineers to determine that the deployment was successful.

Involved:

  • Project Manager
  • Quality Assurance / Test Engineer
  • Deployment Engineer

Expected Results:

  • A new version of the fully functional system deployed in production that can be used by the customer.

Tools:

  • Deployment Tools

Client Testimonial

"...GSI has been instrumental in our success with clients such as Couchbase. GSI has a technically mature staff as developers and architects who possess drivers skills from commodity programming to Artificial Intelligence and cloud-native development ..."
Daryl Heinz
CEO, DFHeinz LLC.

Core Services

Cloud & DevOps / SRE

A cost-effective approach to leverage cloud-based solutions improving scalability and security.

Software Development

Customer-centric digital solutions developed with the latest technology.

Big Data & Data Analytics

Intelligence tools to organize and analyze large volumes of data for better business decisions

Quality Assurance

We work with your team to prevent, test and fix all the possible software quality issues.

Artificial Intelligence

Let’s build AI solutions to automate your critical processes and create personalized data-driven systems which move your business forward.

BlockChain

Adopting blockchain in your organization will benefit your business with our scalable, cost-effective, and powerful blockchain development solutions.

Scroll to Top