Keeping a positive outlook is important for anyone involved in IT projects – but it’s foolish to only be positive. Planning for failure, while it sounds contradictory, is actually the way that IT organizations can keep themselves pointing towards success. This post by Jagvinder Kang examines two elements of “planning for IT failure”: scope and scope creep. By controlling these two areas, a project can successfully be contained within the original scope of work – while also quickly recognizing when the slippery slope of scope creep begins to take hold. Kang explains how clarity of scope in any project (and one that is consistently reinforced throughout the life of the project) can help avoid trouble down-the-line.