Designing, implementing and integrating major IT systems has numerous pitfalls. An IT project manager needs to know what to do when he sees the signs of possible failure.
Topics
Control scope creep
Review of the 10 signs of failure
Correct the definition of "done"
Shorten iterations
Look at your own behavior
Be sure everyone understands the objectives
Get more depth in the team
Find more support
Measure and plot a few key indicators
Force automation through shorter iterations
Lead with honesty and candor
Listen and assess the team
Reduce interfaces
Reduce scope
How to assess a team and its management
Iterate faster on smaller pieces
What to put on the action list, and what to leave off
How to create a super-team and what they should do
How to follow up without over-controlling
Who should Attend
VP-Operations, COO and Director of Operations
Program Manager, Project Manager and Program Director
CFO; VP-Finance; Corporate Controller
VP-Information Systems, CIO and Director of IT
President of Division, CEO and GM of Division
Director of HR and VP-HR
Past Events
How to Save a Failing IT Project 2012 - 09 Oct 2012, Webinar (33026)
Important
Please, check "How to Save a Failing IT Project" official website for possible changes, before making any traveling arrangements