Standards of project management

A guarantee of predictability and safety. How do we do that?

We plan design works according to our own standard, developed during the many years of experiences gained in the course of cooperation with big corporations from various economic sectors. Based on our experience, that model of cooperation is optimal and safe for clients. That does not mean it is the only one. We also use other models, according to the wishes of the companies for which we work. We are flexible and believe that the nature of the project should determine the manner of its realisation and not the opposite.

Most of the time we work according to the following scenario:

Having signed an agreement (contract), both parties appoint project leaders who will lead a given project, respectively, at the client’s premises and in our company. We form a design project, each member of which has predetermined competences and scope of access permissions. We determine the manner of communication with the client and within the team. The whole scope of external and internal communication during the realisation of the project is defined in the “Procedure of Communicating with the Clients of the Risco Software Company”, created and implemented for that purpose, and, obviously, adapted to the needs of a given project, as well as the client’s expectations and procedures.

We hand over the tested system, with user manuals, to the client. At that moment the process of ‘user acceptance testing’ begins. After that, the system is implemented in the production environment.

Analysis and design

We analyse the functional and technical requirements received from the Client. We write down all the detailed expectations, create a system design, and present the prepared document for the client’s verification and acceptance.

The implementation of a prototype

We create a prototype of the application and present it to the client for verification. This stage is not obligatory – it takes place at the client’s request.

Implementation and unit tests

We create test versions of systems and applications.

Internal tests

Before submitting a test version of an application to a client, we conduct internal testing. We create test cases, which can be submitted to the client on demand.

We use rigorous procedures of quality control for the created software. The testing process consists of two parts. During the first stage programmers conduct the so-called unit tests, that is, an initial verification of their work. At the second stage the application is taken over by the team responsible for conducting comprehensive quality control. During the testing, apart from standard scenarios, more comprehensive tests are conducted: of efficiency, ergonomics, and safety.

The delivery of a test version and client’s acceptance tests

We create a test version of the software. The client will conduct acceptance tests on it. The client will receive user manuals together with the test version. Next, the test version is installed.

The implementation of corrections

After the client’s representatives have submitted their comments, we correct the software.

The delivery of the final version

After the last corrections we send the client the final version of the application, that is, the installation version in the production environment, together with a detailed procedure of installation and implementation.

Implementation

At that stage we assist in the implementation of the application in the production environment and remain at the client’s disposal in case of possible unpredicted situations.

Training

At the client’s request our team can conduct trainings for end users.

Procedures

Know-How