1. Project Management Project Reviews

2. Session Objectives
Take some time to consider what are the key guidelines for a good project and how that matches current projects at {Your Organization}.

3. 10 Golden Rules
1. Ensure appropriate organizational representation and buy-in
Owner
Sponsor
Project Review Board
Project Management team
Appropriate resources representing cross-functional scope
2. Define clear objectives and business benefits
Define precise scope
Agree on objectives
Define business outcomes & target business benefits

4. 10 Golden Rules (cont.)
3. Develop project plan with milestones and deliverables
Have a clear starting point, milestones and end-point
Set short-term deliverables a with clear business benefit
End the project by relieving and rewarding the team
Organize follow-up / maintenance and document results and experiences
4. “Think from the right”
Clear picture of the end-result early
This requires a “solution architect” role clearly defined

5. 10 Golden Rules (cont.)
5. Efficiently monitor the project progress - project office
Set clear priorities within the project and check them regularly
Reports in place
Communicate deviations early with decision-makers
6. Foster good team-dynamics
Open environment, where mistakes are allowed
Set explicit expectations for each member in writing
Clearly review individual performance in writing

6. 10 Golden Rules (cont.)
7. Communicate, communicate, communicate (expectations, milestones, and results)
Internal Team (formal at least weekly; informal ongoing)
External Team (ongoing; articles, meeting-minutes, etc.)
User Review Board (at least quarterly)
Steering Committee (at least monthly)

7. 10 Golden Rules (cont.) 8. Ensure user acceptance and buy-in
Create Champions in the business
Manage the political and emotional curves
Prepare acceptance in production, support and Customer Relationship Management
Engage audit and risk management early
Perform progressive acceptance (no surprise at the end)

8. 10 Golden Rules (continued)
9. Control “R&D” risk in feasibility study
Technology risk clearly identified
Feasibility study is clearly distinguished from project by a decision milestone
Perform stress / performance tests
Freeze on technology
10. Manage vendor & consultant relationships carefully
Obtain offers from at least vendors / service providers from a long list (to weigh up choice)
Try to evaluate at least 2 (but not more than 2) vendors / service providers (competition raises performance and cuts costs)

9. Workshop Select a critical project Review against 10 golden rules
Next steps on this project

10. Summary Be honest about a project
Don’t try to change everything in one go
Use checklist for all existing projects