Service Enquiry

Project Methodologies

Porus has developed products and applications for many software companies, E-Businesses, Enterprises, and Manufacturing companies during its years in operations. Porus offers the experience, expertise and best of breed development models used in these projects to you. A brief description of some development models we follow for offshore software product development is presented below. Each model is fine tuned for a specific client engagement depending on the needs, time available and their documentation practices.

Prototype

Porus utilizes the prototype model for projects that involve development of new products, modules and applications. This model is also used where documentation is limited and functionality needs to be shown to work rapidly for prospective stakeholders. This model allows for rapid development and feedback by the prospective users of the system, thereby resulting in improved quality of requirements for the next and final versions of the development effort.
    This model:
  • Reduces cycle time
  • Gets user buy in rapidly
  • Mandates client and user buy in and collaboration at a higher level

Agile

Porus has a strong expertise of working with Agile development models in delivering successful projects. This model of development is suited for clients who have had a prior experience with Agile development or are looking for less emphasis on documentation, high teamwork, collaboration and rapid results. A version of the Agile model frequently used involves 4-6 weeks Sprint cycles and weekly Scrum meetings. Implementing an Agile model with Porus helps you:
  • Develop products and applications rapidly with minimal documentation
  • Accommodate rapidly changing client needs and requirement specifications
  • Involve your team with Porus consultants in development quite intensively
  • Build a competent co-development team for building your products and applications with high visibility, tight budgets and least overheads

    The features of our agile project management methodologies are:
  • Adaptive software development approach
  • Feature driven development
  • Extreme programming and rapid development models
  • Agile techniques including test driven design (TDD), agile modelling, agile change management, and database refactoring to improve productivity
  • Continuous delivery of useful software
  • Flexibility to adjust to late changes in requirements
  • Automated development increasing productivity and putting less strain on the quality review process
  • Continuous attention to technical excellence and good design
  • Regular adaptation to changing circumstances

Waterfall

Porus utilizes an adaptation of the waterfall methodology called 4D Methodology. The 4D Methodology is Porus's four-phase process for developing Web based applications, encompassing Discover, Design, Develop, and Deploy. Each phase in the 4D process represents a milestone that is used as a management checkpoint to review and approve progress, milestone deliverables and quality.
    Traditionally the waterfall model helps you:
  • Coordinate larger teams and projects in a logical, methodical manner
  • Manage costs and budgets with a planned schedule
  • Manage resource risks, technical risks and projects better
  • Have better documentation and plan projects through milestones and documents

Rapid Application Development (RAD)

This development model uses a combination of rapid cycles of iterative development and prototyping. Rapid cycles of prototypes and iterations yield new business requirements for each subsequent cycle. Porus uses this model for products and applications that need high collaboration between stakeholders and the development teams for the evolution of a complex product. Porus frequently uses its code generation tool, Coradigm in this development model to speed up development and manage business expectations. This model helps you:
  • Build complex solutions rapidly using highly collaborative teams
  • Reduce the need for detailed documentation early in the development cycle
  • Refine and validate features with stakeholders after each cycle or iteration