cadences of kanban are meetings that allow a team to deliver working software at a stable and st

visual presentation of data is a great way to display the progress of a project. burndown chart and burnup chart are the two often applied tools in product development to check the progress. the two both have x-ax isand y-ax isto indicate the work and the time and two lines one is the ideal and the other is the actual to compare with each other and show the differences. what are they not in common? burndown chart image from wikipedia  a burndown chart is often used in scrum to overview the task left to do versus time and to foresee when the work will be done. the vertical axis usually represents the backlog either in hours or story points

the year 2020 goes by in a really fast speed. for the last 7 months people experienced covid-

ss and the sf relationships as shown below.  finish to finish a ff dependency means the dependent task b cannot be completed until task a is completed.  start to start a ss dependency means the dependent task b cannot begin until task a begins.  start to finish a sf dependency means task b cannot be completed until task a begins. nothingis particularly hard if you divide it into small jobs.                                                                                                  

is kanban a board? why are there scrum board and kanban board? how to implement the kanban in yo

the abcs of kanban method kanban is originated from toyota production process tps and means signboard. ka

first doing agile can be achieved over night but being agile is a journey. second doing agile is easy but being agile is difficult. last but not lease doing agile satisfies the management while being agile defines the agile culture. i have attended  arie bennekum s online lecture about agile. one of his points made is that doing agile does not equal to being agile. i can t agree more and would like to touch on a few things here. doing agile can be done in practices including implement stand-up meetings   user stories iterations etc. being agile is more about the mindset understanding the organizational culture such as being self-managing what to value and how to behave. look

it s common that developers make mistakes during design and code. bugs are prevalent but still they ne

comparison of scrum and kanban we all love scrum right? it provides a great framework for providing

if you want more effective programmers you will discover that they should not waste their time debugging