Lecture 8

Kanvan us a popular agile software development methodology. It includes real-time communication, full transparency of work and visual representation of the project progress.

Kanban board has 5 components:

1. visual signals: visual cards representing tasks or user stories. These help to understand what the team is working on.
2. columns: they represent the stages of work. For example, each column could be either "to-do", "in progress", "review", "done" ,etc.
3. work in progress(WIP) limits: maximum number of cards that can be added to the column. Once the limit is reached, the team needs to start working on them and when they are done, move those cards to the new stage and add new cards in its place.
4. commitment point: The time point when an item is selected from the backlog and moved into the Kanban board. signifies that work for this item is now started.
5. delivery point: product is delivered to the client.

Simplicity: we will do what is needed and what is asked for and no more. Communication: everyone is part of the team, and we will communicate face to face daily. We will work together on everything from requirements to code together and solve problems together. Feedback: we deliver and demonstrate our software early and often then listen carefully and make any changes needed based on the feedback. Respect: everyone gives and feels the respect they deserve as a valued team member. Courage: we will tell the truth about progress and estimates and won't document excuses for failure because we plan to succeed.

<p>Planning: user stories are written. Plan the releases based on user stories. Prioritize stories and determine which ones will be included in each release (release planning). Break down the release plan into smaller iterations. Each iteration typically lasts one to two weeks (iteration planning). Coding: in test driven development style. Testing: all code must have unit tests. All code must pass all unit tests before it can be released. Acceptance Testing: create automated acceptance tests based on user stories to verify that the software meets business requirements.</p> Signup and view all the answers

<p>There are many similarities between Scrum and XP. A few important differences:  Scrum teams do not allow changes into their sprints. XP teams allow for user stories to be removed or added in an ongoing iteration.  Extreme Programming teams deliver strictly in the order of priority set by customer/product owner. By contrast, the Scrum product owner sets the priorities in the backlog, but the team can determine the order in which they will develop.  Scrum doesn’t prescribe any engineering practices. XP does, e.g. test-driven development, pair programming, etc.</p> Signup and view all the answers