anchor.diff:  NOTE: We do not have a capability for automated git pull requests within Calavera. (We do not use Github *within* Calavera. We just use plain git.)
   
   Therefore, your pull requests will have to be handled manually in your Kanban workflow. More below.
  -
   
   * create an additional repository for the QA person, who becomes the collaborative development partner (like Bill in the web page writeup).
   
  
positive.code: 
  When you are satisfied, you can push to master:
  
  
  
  == Automated Kanban
  Once you have developed at least 5 features with your manual Kanban board, switch to an online SaaS tool. (Consider the section in the AITM test, http://dm-academy.github.io/aitm/#_the_shared_mental_model_of_the_work_to_be_done"[Time and Space Shifting."])
  
negative.code: 
  You should be using test-driven development however. Here is an example of doing that:
  
  Doing anything more ambitious with the Java (generating Javascript, adding classes, etc) is strictly extra credit. Don't distract yourself with getting too technical. But have fun. At the simplest, you should consider adding AT LEAST 10 additional features (each at least some words and an object result - see example below) to the generated web page, considering each one as a feature.
  
  Also feel free to visit the other teams and borrow anything interesting they have done.
  
  