Implementation approaches

The main purpose of our company’s work is to work out a customer solution valuable for the concrete business not only taking into account «best practices» for the given industry. Moreover, the solution should be ready just in time and in line with the Billing model. To achieve that we follow a number of mythologies depending on the project (either it is a product set-up or a big amount of developments to meet the customer’s needs), formalization type and required paperwork.

Methologies:

  • Project Management Institute (PMI)
  • Project Management and Paperwork under the Russina Legislation in line with the GOST 34 and GOST 19
  • Agile Software Development (iterative and incremental development)
  1. Project Management Institute (PMI)

Project Management is performed in line with the Guide To The Project Management Body of Knowledge (PMBOK Guide). The purposes of the project are to achieve the balance between workload, costs, time and quality. A lot of attention is paid to Risk Management.

  1. Project Management and Paperwork under the Russin Legislation in line with the GOST 34 and GOST 19

As per the customer’s requirements especially in regards to the state authorities’ projects we follow GOST standards for the working out project documentation as described below:

  • GOST 34: A set of standards for the automated systems
  • GOST 19: A unified system of the software documentation (USSD)
  1. Agile Software Development (Agile)

On automating business process provided the customer does not insist on significant process formalization we prefer using Agile principle, in particular SCRUM and XP (Extreme Programming). We stick to the principles given in Agile Manifesto as follows:

We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:

  • Individuals and interactions over processes and tools
  • Working software over comprehensive documentation
  • Customer collaboration over contract negotiation
  • Responding to change over following a plan

That is, while there is value in the items on the right, we value the items on the left more.

The meanings of the Manifesto items on the left within the agile software development context are described below.

Twelve principles underlie the Agile Manifesto, including:

  • Customer satisfaction by rapid delivery of useful software
  • Welcome changing requirements, even late in development
  • Working software is delivered frequently (weeks rather than months)
  • Working software is the principal measure of progress
  • Sustainable development, able to maintain a constant pace
  • Close, daily co-operation between business people and developers
  • Face-to-face conversation is the best form of communication (co-location)
  • Projects are built around motivated individuals, who should be trusted
  • Continuous attention to technical excellence and good design
  • Simplicity
  • Self-organizing teams
  • Regular adaptation to changing circumstances