anchor.diff:  
   Look at your Jenkins console. Why didn't the build run? Investigate the hijoInit configuration. Don't move on until you see why.
   
  -Developer, take your Kanban task and move it to QA.
  +Developer, 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.
   
   === Test the new feature
  +
  +NOTE: In this section, we will create an additional repository for the QA person, who becomes the collaborative development partner (like Bill in the Atlassian writeup.
  +
   QA, once you have received the task from the developer:
   
   Starting as your public ID, log into manos:
  
positive.code: = Lab 05 Work Management: Kanban and advanced git.
  In this lab, you will extend the pipeline to support Kanban work management coupled with further git techniques.
  
  Lab objectives:
  
negative.code: 
  Finally, once you have moved features through the automated tool, discuss: how do you like the manual vs automated kanban approach?
  
  Good job on finishing yet another lab. Next week: operations & monitoring.
  