At Consult Circle, we aim to deliver all our projects at a high caliber by combining the flexibility and responsiveness of Agile with the governance of Prince2. We specialise in IT Infrastructure and Cloud projects focused on public and private sector clients.
Whilst Prince2 is a project management methodology and Agile is a framework, so let’s compare!
Prince2 focuses on business justification with an understanding of what products are required to meet business needs for the project, whereas Agile focuses on delivering those products incrementally in an efficient manner. Thus, combining the both would be even more valuable when used together.
By implementing Prince2 Agile in your projects, we always ensure that all principles from Prince2 are followed at all times:
– Continued business justification, by defining a minimum viable product (MVP) that shows just enough features to satisfy our customers and to provide feedback for future product development.
- Learn from experience, by always working with our customers with an “inspect and adapt” manner
- Defined roles and responsibilities of all Prince2 roles and Agile roles so that all team members have a clear understanding of their own role for the project.
- Manage by stages helps to tackle difficult tasks which are broken down into manageable stages.
- Manage by exception occurs when the management attention would only be brought in during significant deviations such as from a budget or an agreed plan. This principle is to ensure that management would only focus on such deviations and not to correct each and every cases.
- Focus on products must be clear before the beginning of the project. Defining the product description should be part of the planning activities and would help in guiding the project and have the correct expectations (acceptance criteria). Therefore, it would prevent any unnecessary meetings, time delays and unexpected costs.
- Tailor to suit the project environment, size, complexity and also risks. The project should be aligned with the existing management structure and also have project controls in place such as risk management, in order to view the project’s progress.
We ensure to plan, direct and deliver all our projects on time, within budget, and with quality objectives by making sure all the acceptance criteria for each project have been met.
We arrange discovery meetings to produce scoping business cases, project plans, and writing benefits identification and realisation. We then revise those where appropriate to meet changing needs and requirements.
We conduct and respond to risk assessments and business impact assessments such as RAID logs.
We identify, coordinate and manage internal and external stakeholders. We produce project status report and plans showing major milestones that needs approval from stakeholders during the planning and design phases and make them aware of project risks at all times.
We ensure that budget and resources are appropriately allocated and controlled. For all project costs, it is important to come up with detailed estimates in order to produce a budget plan.
By implementing Agile to our projects using the Kanban board, daily stand-up meetings help to keep those meetings concise and focus the day-to-day operational task. We keep our meetings within a specific time-frame which is usually between 10 to 15 minutes at the beginning of the day and focus on the team to answer three fundamental questions in regards to their workflow:
- What did I accomplish yesterday?
- What will I today?
- Are there any impediments causing obstacles to my progress?
Plan, coordinate and deliver testing and implementation of projects