How we work?

At Jura, we use a software development process that is fully documented and constantly improved. It is based on best practices and industry standards like Rational Unified Process, Scrum and TQM standards. This process enables us to successfully develop projects within your budget and time frames without compromising our traditional top quality.

The Software Project Life-Cycle is our core business process and provides an outline of the key objectives and responsibilities through various stages of the software process which enables us to provide a superior value to target customers. The software proces defined describes the standard way in which Software Projects are to be managed. The aim is to give advice and suggest methods which are likely to be appropriate in most circumstances in order to leverage project quality and project team productivity. Scrum helps us to work and deliver applications as soon as possible. We use it day-by-day to develop applications. With Scrum we gave a simple and efficient working method.

Requirements Phase A complete and unambiguos set of requirements is established to see what is required for executing a project, including solution functional equirements/quality objectives (FURPS+ ) and necessary resources (skills profiles and equipment). The project resources estimation enables company resource planning and management. If the customer is not able to articulate his requirements, it is the project team responsibility to assist the customer.

Definition Phase After software product definition (high level architecture) and project definition (project plan), a proposal is produced and presented to the customer for consideration. Negotiation follows, during which various aspects of the proposal may be discussed.

Implementation Phase This is the longest and the most complex Phase in the “Software Project Life-Cycle” when the previously agreed solution is actually developed. The proper execution of all previous Phases will result in a smooth software project implementation. During software project implementation the customer may require modifications. The codes, specification and testing are side by side. The software are develop incremental. After all iteration the software are ready to run in real environment.

To ensure product and process quality phase deliverableas are defined and phase reviews are performed. The process is as follows: In each Phase certain activities have to be performed which use deliverables for input and produce deliverables as output. For each Phase, Phase Deliverables are defined as a result of these activities and are of three kind: product, project and contractual obligations deliverables. A new phase should only be started after previous Phase is reviewed and authorization signiture is obtained.