anchor.diff:  * the intersection of product management and project management, and the influence of Agile
   
   == The premise
  -
   
   The lab is based on a "project" of four "sub-projects" that will have some interdependencies.
   
  
positive.code: |Jan-Feb |Vision, charter, and requirements
  |March-June|Core technical platform
  |March-Sep|Business configuration
  |Oct-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.
  
negative.code: Assume your startup has been acquired by a larger company, and through a series of re-organizations they've made you an "offer you can't refuse" to help implement an ERP system. The project is a new kind of work for you; it is waterfall, not Agile, primarily because you don't need to develop new software, but rather configure a vendor supplied package. At least, that is the theory.
  
  
  IMPORTANT: This is a highly experimental, first generation lab. It's not clear how much it is reasonable to expect in an 3 hour lab intended to introduce project management. I don't know how detailed/prescriptive to be, either.
  
  I look forward to having class discussion on how the lab can be improved.
  
  == Learning objectives
  
  