Projects and Analysis

Projects and Analysis

UMS Founders and Senior Management have extensive experience in the very areas that our Clients work in.

In contrast to some of our competitors who only emphasize the cost advantage, we also focus on providing the highest professional quality, fast turnaround times, as well as the highest flexibility and responsiveness. We know that our clients cannot take the risk of missing a deadline or delivering low-quality products. We know that our customers need a reliable, flexible and responsive partner who can relieve their workload so they can focus on their key responsibilities.

This is why we provide highly qualified resources with the proven ability to deliver excellent quality in shortest time-frames.

UMS Project Management Services consists of the following work categories:

  • Project Management on Projects
  • Management and Consulting on Projects
  • Ad-hoc work on Projects

  • But with no limitations to effectively deliver as per the Project Management disciplines below:

    • Change Control Management
    • Communication
    • Document Control
    • Document Sign-off
    • Issue Management
    • Management
    • Program Governance
    • Quality Management
    • Resource Management
    • Risk Management

    • UMS offers Project Management services using the following methodologies:

      • PMBOK
      • Agile
      • PRINCE2

Projects and Analysis Methodologies


Now in its fifth edition, the Project Management Body of Knowledge (PMBOK) is a collection of processes and knowledge areas accepted as best practice for the project management profession. As an internationally recognised standard (ANSI/PMI 99-001-2008 and IEEE 1490-2011) it provides the fundamentals of project management, irrespective of the type of project be it construction, software, engineering, automotive.

PMBOK recognises 5 basic process groups.

The five basic process areas are:

  1. Initiating.
  2. Planning.
  3. Executing.
  4. Monitoring and Controlling.
  5. Closing.

The ten knowledge areas are:

  1. Project Integration Management.
  2. Project Scope Management.
  3. Project Time Management.
  4. Project Cost Management.>
  5. Project Quality Management.
  6. Project Human Resource Management.
  7. Project Communications Management.
  8. Project Risk Management.
  9. Project Procurement Management.
  10. Project Stakeholder Management (added in the 5th edition),


PRINCE2 (Projects IN Controlled Environments) is a process-based method for effective project management. PRINCE2 is a de facto standard used extensively by the UK Government and is widely recognised and used in the private sector, both in the UK and internationally.

There are 7 high-level processes, each made up of a collection of activates. Any PRINCE2® project will use each of these processes to some degree, so let's summarise each process.

The 7 processes are:

  1. Start-up of a project : In this phase, an executive manager and a project manager are appointed together with a project management team. A project brief is prepared, and the project approach is defined.
  2. Initiation: The project brief is upgraded to a business case, and controls are set up to monitor the project.
  3. Direction: In this process, guidelines are established for how the project board should control the overall project.
  4. Control over a stage: The project is broken down into stages, which are controlled by assessing their progress, examining their status and reporting highlights.
  5. Managing stage boundaries: When a stage is nearly finished, the next stage is planned and the overall project plan is updated.
  6. Managing product delivery: Prince2 divides projects into work packages, and the method prescribes how such a package should be executed and delivered.
  7. Closure: This process includes the decommissioning of the project, the identification of follow-up actions and the evaluation of the project.


Agile software development (also called “agile”) isn’t a set of tools or a single methodology, but a philosophy put to paper in 2001 with an initial 17 signatories. Agile was a significant departure from the heavyweight document-driven software development methodologies—such as waterfall—in general use at the time.

The Agile Manifesto is based on 12 principles:

  1. Customer satisfaction by rapid delivery of useful software
  2. Welcome changing requirements, even late in development
  3. Working software is delivered frequently (weeks rather than months)
  4. Close daily cooperation between business people and developers
  5. Projects are built around motivated individuals, who should be trusted
  6. Face-to-face conversation is the best form of communication (co-location)
  7. Working Software is the principal measure of progress.
  8. Sustaunable development, able to maintain a constant pace
  9. Continuous attention to technical excellence and good design
  10. Simplicity - The art of maximizing the amount of work not done - is essential
  11. Self organising teams
  12. Regular adaption to changing circumstance.