Overview of processes and how they map to generic SDLC
PRINCE2 (Projects in a Controlled Environment) methodology is a structured project management method that can be applied to a business, service or department.
The adoption of principles determine whether a project is using PRINCE2, not the adoption of processes and documents alone. The 7 principles are (a) business justification, (b) learn by experience, (c) defined roles and responsibilities, (d) manage by stages, (e) manage by exception, (f) focus on products, (g) tailor to suit the environment.
Prince2 is connected to the Software Development Lifecycle as the SDLC revolves around projects, finding solutions and therefore adheres to the process of taking a set of business requirements and, through a series of structured stages, translates these into an operational IT system.
Similarly, the System Development Lifecycle is all about the planning, understanding, analysing, building testing and implementation of a new system (BCS Development information systems page 14). Delivery being often managed through the project structure (cost, time, budget & quality) shows that Prince2 (- a project management framework) is closely identified with the System Development Lifecycle as all the six stages of systems development are heavily involved with planning, design, test & build variables. In an agile SDLC the system followed in this process would often be referred to as ‘iterative development’ whereby stages will often be repeated to deliver aims & objectives through this approach. (BCS Development information systems page 11)
All teams including Project management, Business analysis, Systems architecture, Programing and testing, Configuration management/change control, Quality control & assurance and Service management are generally all heavily concerned with projects.
Roles and Responsibilities
There are four levels of a PRINCE2 project organisation roles and responsibilities this includes:
- Corporate or programme management, these are outside of the project management team, and are responsible for the Project Mandate i.e. naming the executive and defining the project level tolerances
- The Project Board, these affiliates including the Project Board Executive, the Senior User and the Senior Supplier are responsible for providing the overall direction of the project and are accountable for project success. These members i.e. the Business sponsor, has a high level of authority, with the ability to delegate appropriately.
- The Project Manager, this person is responsible for the day-to-day management of the project within the constraints of the Project Board and will delegate responsibility of the creation of projects to the team manager or specialist team members themselves.
- Team members, i.e Business analysts, solution developers – responsible for delivering the projects products within quality, time & cost. Team managers will perform the daily management of team members.
Advantages and Disadvantages
EASE OF MANAGEMENT – As the method is product based, already systemised and organised into different segments, roles and responsibilities This can help the project team to remain focused and deliver a quality outcome at the end of the day.
ENHANCED COMMUNICATION- The model encourages communication between all members of the team and also between the team and other external stakeholders, thereby giving the team more control of the project.
OPEN DECISION MAKING- The stakeholder is made sure of all the updates and status of agreed actions by reports at regular intervals, it therefore gives them the chance to have a say when it comes to decision making.
REDUCED COSTS -Use of assets and various other resources be controlled greater by the use of your team, thereby ensuring that you are also able to cut down on costs a great deal.
PRINCE2 may find difficulties in catering some of the modern project management needs. I.e. as project management methods have rapidly increased in the software development field over the past decade such as Agile, Scrum, Six Sigma & Waterfall it may not offer the flexibility and benefits that another method can facilitate.
For example an agile method may be more appealing to adopt for projects where there is no need for extensive control over the deliverables. If you’re working with a team that is self-motivated and communicates in real time, this type of project management works well because team members can rapidly adjust things as needed, throughout each task.
In comparison, the PRINCE2 methodology identifies with a structured, coherent approach to manage the project in a logical, organised way, following defined steps.