The Agile Daily Stand-Up

A 59 Seconds Agile Training Video

This is an ‘Agile Daily Stand-Up’ training video.

The Agile Daily Stand-Up Part 9 of 12

Continue to Part 10

The Agile Daily Stand-Up

A 59 Seconds Agile Article

This article provides an ‘Introduction to The Agile Daily Stand-Up‘ and looks to discuss what the Daily Stand-Up is, the format of the meeting and the benefits of the Daily Scrum.

Kanban or Scrum Board?

So how do you choose between the scrum board and the Kanban? There are several differences that can help you decide which one will fit your team’s structure better.

In scrum boards, the entire team is responsible for every task on the board. With Kanban, each person is responsible for a particular step on the task flow, for example testing, or development. If they finish their task, they may help other team members with their tasks or take on a new task from the board.

The product owner can’t change a scrum board, but the product owner can change a Kanban board. Kanban also doesn’t have a time frame for making updates to its board because the limits are on the quantity of tasks in the in-progress column.

There isn’t one clear choice about which type of board will work better for your company, it’s more of a personal preference of what works best for your team and your company.

Continue Reading —> Next

User Stories Applied

A 59 Seconds Agile Book Review

User Stories Applied by Mike Cohn is one of our favourite books on Agile User Stories. The book starts with an overview into user stories, and details what a user story is and the different aspects of them. He then discusses how to go about writing a user story, and provides details of the INVEST criteria that can be used to determine if the story is meeting all of its objectives. Next Mike gives an in depth discussion of who user stories are written for and where to begin when gathering the details for them. The book then discusses acceptance testing user stories, including how to go about specifying these criteria and the responsibilities of the development team and customers during this process.