CI_sign

Over the last 5 years, there has been a dramatic increase in the use of Scrum Agile within a project management environment. The current job growth within the Scrum Agile arena has been due to an increasing number of companies turning to Scrum Agile from a project management perspective. This is due to the light weight methodologies highly popular iterative and incremental approach to software development which allows for flexibility, adaptability and transparency for all members of the project team including the client.
Agile techniques are best used in small-scale projects or on elements of a wider programme of work. There are also links to lean techniques and Six Sigma. It requires empowered individuals from the relevant business, with supplier and customer input.
Rather than focusing on intensive documentation, rigorous change control and contractual disagreements between clients and service provider, requirements and solutions evolve through collaboration between clients, self-organizing and cross-functional teams.
Although Prince 2 is a heavy weight methodology, in 2009, the manual was updated to be easily tailored to suit a number of project environment including Scrum Agile. Adapting the Prince 2 principles, helps Scrum Project Managers, keep an eye on the end product while analysing possible risks, maintaining quality, managing the budget and timeline.
With Scrum Agile learning comes from both the development and use of the system, where possible key steps in the process start with a simple implementation of a subset of the software requirements and iteratively enhance the evolving versions until the full system is implemented. At each iteration, design modifications are made and new functional capabilities are added. This allows for flexibility, adaptability and transparency.
This way, the client gets exactly what they want with very little change control issues and contractual disagreements. Quality is met through collaborative inputs from the client, technical lead and project team. This way we deliver a product that is fit for purpose and we get it right the first time round.
As a Prince 2 Practitioner with Scrum Agile development experience, you will uncover better ways of developing software by doing it and helping others do it. Through this process you will come to value:

  1. Individuals and interactions over processes
  2. Tools Working software over comprehensive documentation
  3. Customer collaboration over contract negotiation
  4. Responding to change over following a plan

The following information will highlight the pay rates and salary scales available for IT professionals within Prince 2 & Scrum Agile, as well as briefly introducing the common factors associated with Prince 2 & Scrum Agile job roles.
Pay Rates and Salary Scales for Prince 2 & Scrum Agile Jobs

  • Scrum Project Managers with Prince 2 certifications can expect to command a salary of over £75,000 per annum, or £500 – £850 per day if you are a contract basis.
  • If you are a Scrum Team Leader / PMO Analyst with Scrum Agile experience, then £45,000 – £50,000 annually would be a realistic salary, or £350 – £375 per day on contract.

These salaries / pay rates are typical for the London and surrounding area.

Typical Job Specification for Prince 2 Certified Project Managers with Scrum Agile Experience
When considering applying for Scrum Agile roles, please highlight the following skills (backed up by relevant examples) within your CV and application material:
Key Skill Requirements –

  • Strong background in SCRUM or another agile methodology would be highly desirable.
  • Strong requirement gathering / business analysis skills
  • Prince 2 Certification
  • Usability & UCD – User centred design skills
  • Experience of a formal Project Management and ideally holding a recognised qualification.
  • Understanding of common project management methodologies and disciplines.
  • Superb communication and organisational skills
  • MS Project, MS Office and Visio
  • Communicating and presenting at all levels.
  • Adept at reporting and producing documents to a high standards.

Furthermore, general requirements / experience that should be emphasised includes –

  • Educated to degree level
  • 3-4 years experience in an IT technical / project role with a relevant company
  • High levels of integrity and a strong work ethic with a demonstrable track record of “getting things done”
  • Ability to work well within a team and be self-starting/work alone when applicable
  • Effectively manages time and priorities and has a clear methodical approach to work

Gain Practical Work Experience