Why the Pingala Project Methodology is important to you?
The security for your organization in planning and executing a project with Pingala, lies in using Pingalas framework of methodology and models, that are well proven and documented, all based on Microsoft’s ‘Success by Design’ framework and other Best Practice disciplines.
The framework is scalable and configurable to any customer and project needs. This is common sense to us since no One size fits all. This is carried out with defined Purposes, Deliverables, and Activities, supported by a set of sub models like an Azure DevOps model, a project Governance model, a Power BI reporting model and a number of templates and guides.
Participating in the right decision-making
Decisions and elaborations over the course of the project are essential to the common adaptation. This is being supported and emphasized in our Hybrid model (Phases & Iterations).
You will be involved in all aspects of the project, from the start phases of defining, through the phases where we Discover more on your business ‘In depth’ and the Build, Tests to ‘Go-Live’ phase, but also when we together prepare you for the ‘New normal’ when all is in Production, and when we follow-up and support your further voyage and evolvement on the new systems. All this will off course be of great value to your business and your employees and be truly emphasized the more you are involved in the full journey.
Doing things right
Always doing things right, also means having the right focus, and starting right. We know that having the right people in the project teams, using a proven way of working (methodology), together with a sound and realistic plan, creates the best starting point.
But starting right, also means executing the right activities at the right time and therefore our methodology underlines the importance of not rushing the project start and allowing the foundation for the project to be solid and set in the INITIATE phase, the most import phase in our model.
Figure showing a graphic representation of the Pingala Delivery Model
Our Governance model
The Pingala Governance model offers, supports, and aligns elements over the project life span, and ensures a proven approach and a set of artifacts for the Project Management Teams* efforts, to Govern the project with just the right amount with the most impact. The model includes, but is not limited to aspects like Change Management, Quality Management, Time & Cost Management, Project and Organization Management, Roles & Responsibility Management, Team Management and Risk Management.
* Project Management Teams are a broad description covering all roles involved in the Project Governance approach
Support teams and leadership
Our Execution model, support working in Teams and allowing them the opportunity to develop their own leadership. In the IMPLEMENT phase we work in Sprint Teams and uses Scrum principles. It is essential that these Teams include both yours and Pingala´s participants to ensure both involvement and ownership.
The roles involved in the sprint execution involves both a Solution Owner, a Scrum master, as well as the participants in the Sprint Teams.
Executing includes many of the known Scrum disciplines, like Backlog Refinement, Daily standups, retrospectives and Release and Demo activities.
Using the right and skilled people
When appointing participants for the project it is essential to find the right people. In Pingala we always aim to onboard the best and most skilled people for the tasks ahead. The same, however is important for you when you fill the roles needed.
To align expectations ahead of the project start, Pingala offers – not only a set of predefined roles on needed prerequisites and responsibilities for our own participants, but also a set of guided roles as suggestions to your participants. This alignment is supported by a RACI model – to clearly define the expectations on Responsible, Accountable, Consulted, and Informed between roles on major tasks and activities, within the project.
When the project goes Live in Production
You will NOT be left alone and behind when the Project closes and the ‘New normal’ goes into Operations or Support of the new systems. The Pingala methodology includes and offers activities to ensure a smooth and gentle transfer from the Project to the Application Managed Services (AMS) including guided ways to make sure that the continued Business Development and support will apply. Rest assured; we have done this many times before.