Lviv PM Club Тетяна Голубєва - "Ongoing project reformation: no magic, just management"
This document discusses ongoing project reformation and crisis management. It notes that reformation often starts due to customer, company, or team dissatisfaction. The key steps are to audit the current project, establish new goals and a plan, and launch the revised project. Successful reformation takes 1-2 years and requires transforming existing projects into a coordinated program, strong team support internally and externally, thorough information gathering, written agreements, close monitoring of personnel, and accounting for code legacy, skills, teamwork, stakeholder management, and risk management. The overall message is that project reformation involves management rather than "magic" to address challenges and transform projects for long-term success.
Lviv PM Club Тетяна Голубєва - "Ongoing project reformation: no magic, just management"
- 1. Ongoing Project Reformation no magic, just Management (c)Tetyana Holubyeva Apr 2016
- 2. How it starts? Please do something!
- 3. How it starts? Please do something!
- 4. Challenge + Crisis Management
- 5. Why? Somebody isn't happy at all: - Customer or main stakeholder - Company - Team
- 7. Why? Something is wrong Budget Resources Tim e Quality Scope Risks
- 8. What to do? 1 project + 1 project + ??? Program
- 9. What to do? Audit New Project − Goals − Plan − ... and GO
- 10. Do we need it? Budget Resources Tim e Quality Scope Risks
- 12. How We did it? Like this…
- 13. Seriously Customer value Company value Team members value
- 14. Take into account 2 focuses: • Long term goals • Short term goals • Turbulence
- 15. Take into account You Must be supported inside Inside company should be single vision about this program
- 16. Take into account Historical background influence project flow significantly and do project restart more complex Collect Information from all sources
- 17. Take into account All agreements should be in written. Linked mails.
- 18. Take into account For quick project transformation strong team should be created (that have high delivery cost) For projects that are under transformation close monitoring of key people state should be done
- 19. Take into account Code legacy leads to significant deviations in estimates
- 20. Take into account Skills, skills, skills life and work experience
- 21. Take into account Team work
- 22. Take into account Stakeholder Management Visibility Risk Management
- 23. Where are processes? Somewhere in between
- 24. and Yes, that's You