Project Management

Development of our own Software development projects, and our adquired experience, made us see that no existing methodology for Project Management was in line with what we think should be a project management methodology for software development.

That is why we created our own software development Project Management methodology, which we call SoftWarePlan.

We offer our customers manage their software development projects by applying our methodology, which, correctly applied, ensures the success of any project regardless of its size.

SoftWarePlan is mainly based on our experience with a management methodology for implementing IT projects called Prince2, and theorical knowledge of some others project management methods.

SoftWarePlan consists of various phases and tasks, each with a defined deliverables:

Design phase

The design phase consists of three sub-phases. This phase is the most important in the project, because if companies are set to perfection this phase, planning, cost, quality and user satisfaction, is guaranteed.

• Requirements analysis.- Collect and analyze customer needs and requirements for project development, through these actions we get a comprehensive pre-planning of the project and an outline of it.
• Definition of the development project .- In this sub-phase we set the following objectives:
  • Choice of technology to use.
  • Definition of the technical requirements of the project, both in its development phase in its implementation phase.
  • Definition of the scope of the project both in technology as at functional level.
  • Design of the tasks of the project depending on the size.
  • Realization of project planning, definition of change management and risk management.
  • Definition of requirements for implementation, training and project implementation, and maintenance once established.
  • Presentation of the project.
• Specification of the project .- Functional specification and technical details of the project. This sub-phase supports the following phases of the project, as the deliverables of the same, signed by the client, including a detailed analysis of the following items:
  • Functional specification and technical details of the project.
  • Database structure and any amendments to do on it.
  • Input - Output structures for data integrations.
  • Internal test plan.
  • Integration test plan.
  • Piloting Plan.
  • Implementation and training plan.
  • Definition of the installation of the final product.
  • Definition of the maintenance needs of the product.
  • Design of the user satisfaction test with the product.
  • Confirmation of the planning of the sub-definition phase.

Execution phase

• Project development.- Development of the Software included in the project. Deliver at this stage, in addition to the Software, are the final structure of the database and the list of documented processes and sub-processes used and created during development.
• Internal test.- Results of internal test defined during design phase.
• Documentation.- User and installation manual. 

Quality and assurance control phase

• Integration test.- If necessary, often on projects of integration between applications.
• Piloting monitoring .- Installation of the pilots of the product, implement the plan as defined in the phase of design.
• User satisfaction control.- User test on their satisfaction with the developed software.
• Change management .- Based on the results of the previous two sub-phases, management, planning and change control to make. 

Deployment phase

• Training.- Monitoring and organization of training in terms of the plan as defined in the design phase.
• Installation.- Monitoring and organization of installation in terms of the plan as defined in the design phase. 

Manteinance and support

• Product manteinance & support.- Monitoring the implementation of agreements on the maintenance of the product taken during the design phase.