Introduction to an Agile Project Management Policy
0 likes84 views
This document introduces an agile project management policy. It discusses why such a policy is needed, how to create it, and what content it should include. The objectives are to understand the context, know best practices, and learn the creation process and useful policy content. It recommends building on industry standards, defining lifecycles and decision points, and tailoring the policy to support agile approaches. The content section describes including roles, processes, definitions, lifecycles, project classification, considerations, and documentation guidelines. Stakeholder alignment is key in policy development.
Introduction to an Agile Project Management Policy
- 2. Introduction to an Agile Project Management Policy Andreas Madjari, PMP
- 3. Content Topics Why A PM Policy? Why Agile? How to Create an Agile PM Policy? What are the Policy Contents? Conclusion
- 4. • Understand the context in which the Agile PM Policy was created • Know the industry best practice sources to build on • Understand the creation process of a PM Policy supporting Agile • Know what content makes the PM Policy usable and helpful Objectives
- 5. Topic 1 Why a PM Policy? Why Agile?
- 7. Organization Transformation started IT Implementations using Agile methods Need to reduce Time to Market Why go Agile in Project Management?
- 8. Internal – Effectiveness and Efficiency: External – Regulatory Compliance Internal vs. External Motivation
- 9. Topic 2 How to Create an Agile PM Policy?
- 10. Project Management is a Support Function! • Serves a purpose • Interaction with other support functions for success • Interfacing processes need to be ready • Involved people need to be educated Content Creation: Stakeholder Alignment is Key!
- 11. Build on Industry Best Practice 49 18
- 12. Define Project Lifecycle Models Allow different approaches that are not strictly waterfall. Ensure common and clear decision points for Management!
- 13. Support the Lifecycle Model Choice Tailoring for each Project Supported by “Adaptive Suitability Assessment”
- 14. Change cannot be legislated. It needs to be managed! Policy • is only a means to an end • needs to represent culture & conditions as they are lived Deployment: Keep the PM in Mind Communicate & Educate!
- 15. Topic 3 What are the Policy Contents?
- 16. Erste’s governance framework is called “Group Policy Framework” (GPF) Policy: What Procedure: How Check your Governance Framework (if exists)! The Policy on “How to Write Policies” - GPF
- 17. • Mapping of Roles & Processes – RACI • Definitions • Detailed Role Descriptions • Project Lifecycle Model & Tailoring • Project Classification Contents - The Policy
- 18. • Considerations for Applying Lifecycle Models • Collaboration with Key Roles • Tailoring Execution • Project Documentation Explanation • Process Descriptions (“the meat”) • Traffic Light Status Definitions • Handover to Operations Checklist Contents - The Procedure
- 19. Change cannot be legislated in! • Understand your culture, your governance structure, the interfacing processes and the organizational need • Inform and educate your stakeholders • Align with stakeholders before writing! Policy writing is a project. Run it like one. Conclusion
- 20. Agradecemos su atención. Andreas Madjari +43 (664) 8183662 andreas.madjari@erstegroup.com Erste Group Bank AG – www.erstegroup.com Am Belvedere 1, 1100 Vienna, AUSTRIA https://www.linkedin.com/in/andreasmadjari/