Projects are initiated to improve the Business process and optimize the utilization of the Organization resources. Project Managers or Scrum Masters or Product Owners have challenge in getting the right type of resources (man power, machines & material) who are key in making the Projects success. This session helps in understanding where is the real POWER, how to empower the POWER & get the needed resources.
Topics covered in the session are 1) Organization types (Projectized/Matrix/Functional) 2) Stake holder Analysis (Power/Interest) or (Power /Involvement matrix etc) 3) Project Manager/Product Owner/Scrum Master setting the expectations by drawing (RACI Matrix for getting POWER involvement) 4) Project Manager/Product Owner/Scrum Master Selling his Release Plan to POWER & get the Resources allocated 5) Project Manager/Product Owner/Scrum Master Selling empower the POWER and turn Forbidden POWER in various Scrum Ceremonies.
6. Agile and Traditional Co Exist
Organization
Program 1
Traditional
Traditional
Agile
Traditional
Program 2
Traditional
Traditional
Agile
Agile
Program 3
Traditional
Traditional
Traditional
Traditional
Portfolio 1
Agile Program
Agile Program
Agile and
Traditional
Program
Portfolio 2
Agile Program Agile Program
Traditional
Program
Agile and
Traditional
Program
7. Definition of Program, Portfolio
Portfolio
A collection of projects or programs and other work that are grouped together to
facilitate effective management of that work to meet strategic business objectives
Program
A group of related projects managed in a coordinated way to obtain benefits and
control not available from managing them individually
Source : Project Management Body of Knowledge (PMBOK from PMI)
8. When we are planning for Big Scrum Teams (scaling)
Scrum Projects & Traditional Projects have interdependency.
17. How to win Forbidden Power Players
1. Know your Organization
2. Identify Power Players
3. Acknowledge Power & Plan the Approach
4. Understand Why they resist
5. Communicate them with their Vocabulary
6. Manage Specific Needs Collaboratively
7. Educate on Agile Practices
8. Contribute to PMO & Improve the Success Rate