anchor.diff:  Therefore, your pull requests will have to be handled manually in your Kanban workflow. More below.
   
   === Identify a new feature
  -
  +Your product feature idea can be extremely simple. Some good starter examples would be,
  +
  +* Display the team name
  +* Add two numbers together
  +* Display a given irrational number to 10 places
  +
  +Write the idea down, with appropriate detail. For this lab, keep it simple. You might want to have two attached sticky notes: one identifying the task, and the other to actually carry the idea to the BA.
  +
  +Product owner, your Kanban task is now ready for the business analyst - it meets the definition of done. Do not pull anything more into your queue until this task has been pulled ahead. Instead, if it takes them more than a few minutes to pull your task, go help folks downstream clear their lane.
   
   === Write a new story
  -
  +As BA, you should formalize the story more:
  +
  +"As a user of the website, I want to see two numbers added together."
  +
  +"As a user of website, I want to see a greeting that is meaningful so that I know which team's site I am accessing."
  +
  +"As a user of the website, I want to see the number pi displayed to 10 places so that I may have that knowledge."
  +
  +Business analyst, once it is written in this form, 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 clear their lane.
   
   === Develop the new feature
   
  -
  +Developer, pull the story from the BA into your queue.
   
   Here we will create a new feature development branch by using the `git checkout -b some-feature master` command.
   
  
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: * QA person commits it to master
  * Tools person moves it to production (via cara reprovision)
  
  You are to do this multiple times. Add 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.
  
  Do  5 features manually and 5 features with an automated kanban tool.
  
  The first time you go through this, the entire team should go through each step, with the appropriate team member leading the activity.
  
  After that, you may be able to accelerate things. This is where some self-organization comes in. Do not use the suggested team structure as a cage. You will find the developers likely have the most work work. How can you all work together to deliver more quickly?
  
  == Git feature branch, with Java example.
  
  