As our Titanic series continues, we continue to explore the importance of post-mortems. When projects fail catastrophically, a post-mortem is important to provide a better understanding of the reason behind the failure and prevent future failures. This requires that the IT organization has a post-mortem process in place so little time is wasted in enacting it.
699 items found
Lesson Learned #5: Remember to Resource Level the Project Plan.
What would the post-mortem for the failed Titanic project look like, and how can it help you in today's IT landscape? Read on as our popular series continues.
Before corporations jump into the knowledge management fray, they should understand that the solution to KM problems is not only technical in nature but requires key organizational and policy elements in order to be successful and sustainable.
As our series continues, we continue to examine what the post-mortem for the failed Titanic project would look like, and how can it help you in today's IT landscape.
Many factors will influence an enterprise transformation to self-organized teams, from the willingness of project sponsors to the makeup of the overall portfolio. As such, there is no universal template for success, but here’s a 10-step framework to help design and manage the transition.
As our voyage concludes, we use the Titanic to address your project lifecycle and what you can learn from root causes.
Move over data mining, there's a new mining technique in town. It is time to unleash the knowledge in blogs by beginning to utilize blog mining!
Information overload bogging you down? If you need help determining when sourcing analytical capabilities makes sense and when it does not, read about a framework of factors that are important to consider.
Project managers must learn from past mistakes, or they're doomed to repeat them. Here are 10 of the most common missteps that jeopardize IT projects, with recommendations on how you and your organization can avoid or overcome them.