anchor.diff:  |Jan-Feb |Vision, charter, and requirements
   |March-June|Core technical platform
   |March-Sep|Business configuration
  -|Oct-Dec|Global deployment
  +|May-Dec|Global deployment
   |===
   
   Notice that there is overlap between the "Core technical platform" and the "Business configuration" activities. It is assumed that research and requirements gathering can be accomplished before the platform is physically acquired and installed.
  
positive.code: 
  Note that for a variety of reasons, your company has opted to host the ERP system internally. This means that your technical team needs to handle asset acquisition, data center capacity, network capacity, SAN sizing, and so forth. The ERP vendor will be able to provide guidance on much of this, based on the anticipated workload.
  
  
  
  == Approach
  
  The objective is not to get a perfect project plan. For a system of this scale, that would require days or weeks of effort by experienced professionals.
  
  
  
  At least at first, breadth is better than depth. That is, it is better to have a high level plan for all of the project, than a detailed plan for one section with the rest left completely undone.
  
  You should develop your project with a top-down approach, and make liberal use of "TBD" placeholders. It is perfectly acceptable to have tasks such as "Further develop project plan to detailed task level"  HOWEVER, that placeholder task SHOULD have a "done by" date you are managing to!
  
  
  == other tools considered
  http://www.aha.io/
  
negative.code: 
  *Within each class team*, the roles will be structured in the following way:
  
  * *PMO Lead* represents the the Project Management Office, responsible for the overall program vision,  integration of the sub-team plans, and reporting status to leadership.
  * *Technical Lead* represents the Technical Architecture team, responsible for the core system: hardware, software, configuration, and deployment
  * *Process Lead* represents the Process team, responsible for understanding business requirements
  * The *Change Lead* represents the Organizational Change Management team, responsible for rollout, training, organizational communication.
  
  There are only four roles, so you will be able to have one or two people float in response to demand.
  
  