anchor.diff:  
   Notice we did a "git pull," that resulted in "Already up-to-date." In a busy development environment, that might easily not be the case.
   
  +****
  +*Developers note:*
  +
  +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.
  +
  +You should continue using test-driven development however.
  +
  +Also feel free to visit the other teams and borrow anything interesting they have done.
  +****
  +
  +IMPORTANT: At this writing, I would appreciate a basic Javascript approach that would allow the web site consumer to enter simple data (integers and strings), in a manner consumable by the supporting Java code.
  +
  +QA, your Kanban task is now ready for QA - it meets the definition of done. Do not pull anything more into your queue until this task has been pulled ahead. Instead, go help folks downstream clear their lane.
  +
   === Deploy to production
  -The QA person now moves the feature to the tools team. Their job is easy. As publicXX, go:
  -
  -~/Calavera$ vagrant reload --provision caraxx
  +The tools team now pulls the task into their queue. Their job is easy. As publicXX, go:
  +
  +`~/Calavera$ vagrant reload --provision caraxx`
   
   and after a few minutes the new production website should appear, identical to the QA screenshot above.
   
   Time to define some of your own features! Do 4 more manually and move to the next section.
  +
  +As you move forward with more features, consider that you have all the skills not just for separate dev & QA, but for two different developers as well. You can certainly set up a third directory, e.g/ home/hijo2, in the same was as the QA directory. It's up to you as you self-organize. 
   
   == 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 textbook, http://dm-academy.github.io/aitm/#_the_shared_mental_model_of_the_work_to_be_done"[Time and Space Shifting."])
  
positive.code: * Develop a manual Kanban board and convert it to an automated system.
  * Learn the basics of git feature branching workflow.
  * Add at least 10 small features to your product, using your team's agreed end to end workflow.
  
  
  == Manual Kanban
  
  
negative.code: For the Fall 2015 lab, Teams 1 and 2 will use https://trello.com/[Trello].
  Teams 3 and 4 will use https://tree.taiga.io[Taiga].
  
  The Cloud-based SaaS sites have extensive instructions and do their best to make it easy. Therefore, this lab does not provide step by step instructions. For both Taiga and Trello, your team lead should sign up first and create the team, and then invite the other members. I have tested that this works for both systems.
  
  Part of the learning in this lab is climbing the learning curve for these applications. We will work through any issues in class and I will update the lab with more details if required.
  
  Once you are provisioned with the online tool, you should use your manual Kanban board as a basis and adapt the online system for your team.
  
  