What goes into a project plan?

Now we need to see what delivering an implementation project requires in more detail. Like any project, we need to have a goal or set of goals in mind, so we know whether we're moving in the right direction. Those are going to vary from one organization's implementation to the next, since sometimes speed is of the essence and other times, getting everything set up just right is more important, even if it takes longer. Once we have goals, we can lay out the path for achieving them, and make sure all parties involved know what will be expected of them. In the software delivery world, setting expectations correctly is probably the most important first thing we do. Many of the problems I've seen happen in large and small projects can be traced back to someone having the wrong idea about what they were supposed to do or what others would do for them. Getting through a NetSuite implementation to a day when the organization decides they're ready...