About Us

SEO Friendly - put keywords here

SEO Friendly - put keywords here, don't worry this will not show in the UI

CORPORATE HEADQUARTERS

JairoSolutions LLC
15437 Anacapa Road
Suite #25
Victorville, CA 92392

Office Hours:
8:00 am - 5:00 pm PST

Tel +1760.245.9722
Fax +1760.669.5645
Email: inquiry@jairosolutions.com

REGIONAL HEADQUARTERS

JairoSolutions, Inc.
Dr. 302 Diamond Bldg., Mac Arthur Highway, Matina, Davao City, Philippines, 8000

Office Hours: (Monday to Friday)
6:00 am - 3:36 pm GMT
10:00 am - 7:36 pm GMT
10:00 pm - 7:36 am GMT

Tel +63 082-297-2087
Email: asia@jairosolutions.com

Overview

JairoSolutions goal is to deliver maximum value to its customer by adhering to well defined and proven methodologies for Software Engineering and Project Management. We aim to promote continuous professional and technological growth as well as build camaraderie and unity among each other. We have a great desire for creating high quality, professional, and standard websites. JairoSolutions adopts the agile methodology of Scrum with XP.

Scrum and extreme programming provide complementary practices and rules. They overlap at the planning game (XP) and Sprit planning (Scrum). Both encourage similar values, minimizing otherwise troublesome disconnects between management and developers. Combined, they provide a structure within which a customer can evolve a software product that best meets his or her needs, and can implement quality functionality incrementally to take advantage of business opportunities.

Process Engineering

SCRUM is a loose set of guidelines that govern the development process of a product, from its design stages to its completion. It aims to cure some common failures of the typical development process. Now, scrum is often viewed as an iterative, incremental process for developing any product or managing any work.
Scrum projects support the use of any software engineering discipline. However, since XP (Extreme Programming) and Scrum share many core practices, Scrum and XP integrate well together. The phrase Scrum process with XP engineering practices refers to the use of Scrum to manage the steps taken to develop software, in conjunction with the use of XP to ensure the quality of the software.

Scrum and extreme programming provide complementary practices and rules. They overlap at the planning game (XP) and Sprit planning (Scrum). Both encourage similar values, minimizing otherwise troublesome disconnects between management and developers. Combined, they provide a structure within which a customer can evolve a software product that best meets his or her needs, and can implement quality functionality incrementally to take advantage of business opportunities. Following are several shared practices that facilitate this functionality:

» Iterations. All work is done iteratively, with the customer being able to steer and direct the project every iteration.

» Increments. Every iteration produces an increment of the customer's highest-priority functionality. If desired, the customer can direct the developers to turn these increments into live, operational functionality at any time.

» Emergence. Only that functionality that the customer has selected for the next iteration is considered and built. The customer doesn't pay for functionality that he or she might not select, and the developers don't have to code, debug, and maintain irrelevant code.

» Self-organization. The customer says what he or she wants; development determines how much they can develop during an iteration and figures out the tasks to do so.

» Collaboration. Business and engineering collaborate about how best to build the product and what the product should do between iterations.

These XP engineering practices were used for Project X:

» Simple System Design. An emphasis was placed on designing only what was needed to support the functionality being implemented.

» Test-First Coding. Unit tests were written prior to the construction of code. This practice forces developers to understand the interface and expected functionality of a class. The tests accumulate over the duration of a project, providing a library of regressions tests.

» Continuous Integration. The Open Source product Cruise Control was installed and configured to run every five minutes. This process would automatically check out all code from the repository, build the code, and run the library of tests. By continuously building and testing the code, the project team could ensure that the base software was stable and of a high quality.

» Refactoring. Refactoring allows for the incremental improvement of the design and class structure to support new functionality.

» Pair Programming. The project team took pair programming to the extreme, doing all work in small groups of either two or three. This included activities such as analyzing data and creating the data model, in addition to programming.

The scrum process has 3 main phases.

Planning
In this phase, the project is planned and high-level design decisions are made.

Sprint Cycle
The sprint cycle is an iterative cycle of about 3-4 weeks, in which the actual development of the product is done.

Closure
In this phase, the product's development is brought to a close, and the product is released.