The document discusses ongoing project reformation and crisis management. It recommends auditing projects, creating new project plans with goals and budgets, and ensuring projects create value for customers, companies, and team members. It also stresses the importance of collecting information, having all agreements in writing, creating strong project teams, monitoring transformed projects closely, accounting for code legacy and estimating deviations, prioritizing skills, teamwork, stakeholder management, and balancing long and short-term goals during turbulence. Historical context and processes are noted to significantly influence project flows and restarts.

1. Ongoing Project Reformation
no magic, just Management
(c)Tetyana Golubyeva
Apr, May 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

6. Why?
Something is wrong

7. Why?
Something is wrong Budget
Scope

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
Scope

11. How long?
~1-2
Years

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 monitor

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

25. Thank You!
Questions?
http://compdev.com.ua