Every large IT project is unique. Each faces a complex array of challenges. When projects get into trouble, they often exhibit similar patterns - succumbing to risks that could have been anticipated, prevented, detected sooner, or managed better. Common early responses to problems - blaming, deferring action, or outright denial - usually make things worse.
In this session, Payson Hall reviews a dozen patterns he has observed on large, troubled IT projects during his forty-year career, including troubles with subcontractors; challenges with project sponsors; friction within the team; the perils of interfacing with adjacent systems; and issues with data cleansing and conversion.
The session shares insights to help identify the symptoms of common risks, reduce the likelihood of risks occurring, facilitate early detection of problems, and establish a foundation for helpful responses when problems arise.
This session is designed for project managers, team leaders, project sponsors, and others with responsibility for successfully building and rolling out large enterprise systems.
If your multi-million-dollar enterprise software project is going to fail, we suggest you find novel reasons for that failure and avoid failing for common reasons.
Presenter Payson Hall has managed software projects, conducted project audits, performed project reviews, and conducted project autopsies during his 40-year career. During this time, he has observed some common causes of project failure that he will share to raise awareness among participants of the risks and possible ways to mitigate them.
This session is particularly focused on project managers, senior project team members, portfolio managers, project office teams, and project sponsors who are responsible for enterprise level systems. It is most useful to those who implement: