We get asked this a lot – “Is the methodology for the playbook Agile?”
- We value an iterative and incremental framework for developing products and deploying software
- We very often utilize sprints to manage work
- The toolkit we utilize to manage tasks and report status are commonly used for managing Agile projects
The Scrum Master or Agile Coach may not agree that what we do purely aligns with the methodologies most commonly utilized to deliver the Agile framework. This may sound like splicing details – but we want to be very clear.
The P2A playbook is a methodology that supports an Agile framework and aligns with the Agile manifesto but does not strictly adhere to all the tenets of Scrum, Safe, Kanban or any other agile methodology.
The reasons why we don’t strictly adopt one of those methodologies is based on an assessment of the needs of our clients.
- The learning curve and change management required to adopt a playbook is less complex than a particular Agile methodology
- We believe that the methodology should be a tool to easily utilize and that developing project management skills which can be leveraged easily beyond IT is the most useful approach for our client base
- With a shift toward the “gig economy” documentation is crucial to keep budgets and team members in alignment, ensure clear communication with disparately located team members, and transition projects successfully to future teams. This belief deviates slightly from the Agile Manifesto tenets.
- Team members that are familiar with specific Agile methodologies will be very comfortable that the 80/20 rule enables us to achieve success with agility. The majority of Agile methodologies are not strictly implemented in the corporate world due to organizational, budget and training constraints. Similar to a waterfall methodology, the culture of the organization drives variances in methodology adoption. The playbook editions allow for cultural variation.