Avoiding the 10 Worst Practices of SAP Development Projects

  • by Amy Stapleton, Founder, Hutch.AI
  • September 15, 2001
/Project Management
It is a common misconception that unsuccessful SAP projects, regardless of purpose or scale, fail due to a lack of time, money, and/or people. Research shows that this is rarely the case. Projects typically fail for other reasons, like faulty business practices. While there are obviously an infinite number of things that can go wrong, this article zeroes in on the 10 worst — the ones that are the most common, potentially detrimental, and above all avoidable. And although some of these observations may seem obvious at first glance, as an intertwined whole, they will provide a strong safety net for your next project.

Amy Stapleton

Amy Stapleton has several decades of experience managing software development projects. She began her career at SAP in Walldorf, Germany. After returning to the US, Amy gained hands-on project management experience in ERP implementations at major corporations across many industries. Amy joined the National Aeronautics and Space Administration (NASA) in 2001 where she served as an IT Manager. She assisted in the Space Agency’s implementation of an enterprise core financial system using SAP. Amy retired from NASA in 2015 and is now founder of Hutch.AI and an analyst at Opus Research, working in the area of artificial intelligence

See more by this author


Comments

No comments have been submitted on this article. 


Please log in to post a comment.

To learn more about subscription access to premium content, click here.