A Project Management Methodology for Agile Scrum
At QAT Global, we’re strong believers in Agile and put it into practice with virtually every project we work on. We’ve developed a repeatable process methodology we call Agility RPM℠ to maximize the time and resources on projects for clients, as well as, internal projects. Agility RPM℠ is an agile scrum approach to software development. Rather than a full process or methodology, it is a framework.
Versus providing complete, detailed descriptions of how everything is to be done on the project, certain responsibilities are determined by the team. Experience tells us the team is typically best suited to address its own challenges and objectives. Traditional Development Methodologies take the “one size” fits all mentality. An overview of the Agility RPM℠ process is shown below.
Agility RPM℠ introduces the concepts of a Product Owner (State Project Manager) and a Scrum Master (QAT Project Manager). The Product Owner defines the project priorities and accepts or rejects work results. The Scrum Master represents management to the project, is responsible for enacting development procedures and schedules and shields the team from external interference. Working together, these two roles will define Project Sprints to complete the work. Each sprint will consist of a group of tasks that will be completed, deployed and tested as a group. Sprints are defined to be completed in a fixed time period.
A critical piece for the success of the Agility RPM℠ Process is the Daily stand-up meeting. These meetings are typically 15 minutes in length. Each team member reports what they accomplished yesterday, what they plan to accomplish tomorrow and what problems they have encountered. The Project Owner and Scrum Master are responsible for removing road blocks that are reported by the team.
The Agility RPM℠ process is design to prevent change requests and scope creep from interfering with the Sprint progress. The Project Owner and Scrum Master can adjust the size, scope, duration and frequency of the Sprints during the Sprint planning stage to adjust the time to production to meet changes in the project time frames.