Kanban Scrum Boards

0 votes

I'm curious as to what other people use for physical Kanban/Scrum boards in their companies. I appreciate that because of sensitive business information you may not be able to provide a photo of the board. I"m looking at to find out what does your board looks like, and how you organize user stories and tasks as they move through a typical sprint/iteration?

Typically I've worked in a places that organize the board as follows with each

User Story   | Todo                   | In Progress  | Ready for QA     | Done   |
UC-001       | Domain Object, Service | DAO(Bob)     |                  |        |
UC-002       | Payment UI Screen      |              | Payment Srv (Don)|        |
UC-003       |                        |              | UC-003           |        |
             |                        |              |                  | UC-004 |
             |                        |              |                  | UC-005 |

So to summarise:

  • A task for UC-001 is in progress by one member of the team (Bob). A list of tasks for other people to pick up are waiting in the Todo column, but this can be picked up by another member of the team who co-ordinate with Bob to get the work done.
  • For UC-002 the payment service task was completed and an automated test harness was completed for QA allowing them to test the service without a UI. If the test fails a bug is raised and moved along with the Payment Service task back into the QA phase
  • All the tasks for UC-003 was completed and moved to Ready for QA.
  • All the tasks for Uc-004 and UC-005 were complete so the user story was moved to Done.

This works as a tangible white board that involves people interacting with each of the tasks/user stories (represented as post it notes). An electronic version is created prior to the sprint/iteration and is only updated at the end of the sprint/iteration corresponding to the current situation. Comments and criticism are welcomed : )

Apr 18, 2022 in PMP by Edureka
• 13,690 points
797 views

No answer to this question. Be the first to respond.

Your answer

Your name to display (optional):
Privacy: Your email address will only be used for sending these notifications.
0 votes
Kanban Board is an agile project management tool designed to  visualize work, limit work in progress, and maximize efficiency (or flow). This helps both agile and DevOps teams bring order to their day-to-day operations. Kanban boards use cards, columns, and continuous improvements to help technology and service teams focus and do the right amount of work.
 Kanban has come a long way from the origin of lean manufacturing, thanks to a group of small but powerful kanban enthusiasts. David Anderson's work in defining Kanban methodologies helped bring Kanban into the field of software and services, and Personal Kanban by Jim Benson and Tonianne De Maria helped expand Kanban applications into incredible areas. The
 Kanban board can be divided into five components: visual signals, columns, work-in-process limits,  commitment points, and  delivery points.
 Visual Signals – The first thing you notice about Kanban boards is visual cards (sticky notes, tickets, etc.). The Kanban team writes all  projects and work items on the card. Usually one for each card. For agile teams, each card can include a user story. When you join the board, these visual clues help teammates and stakeholders quickly understand what the team is working on. Column – Another feature of the Kanban board is the column. Each column represents a particular activity, which together form a "workflow". The card is completed through a workflow. Workflows can be as simple as To Do, In Progress, Completed, or much more complex.  Work in Process (WIP) Limits-WIP limits are the maximum number of cards you can put in a row at any given time. A column with a WIP limit of 3 cannot contain more than 3 cards. If a column is "run out", the team must swarm on those cards  before new cards can enter that stage of the workflow. These WIP limits are important for identifying workflow bottlenecks  and maximizing flow. WIP restrictions give  an early warning of overkill. Commitment Points – Kanban teams often have a backlog of the board of directors. This is where customers and teammates can provide project ideas  that the team can pick up when they're ready. The commitment point is the moment when an idea is picked up by the team and work starts on the project.  Delivery point — The delivery point is the end of a kanban team`s workflow. For most teams, the delivery point is when the product or service is in the hands of the customer. The team`s goal is to take cards from the commitment point to the delivery point as fast as possible. The elapsed time between the two is the called Lead Time. The Kanban team is constantly improving to reduce lead times as much as possible.
answered Apr 20, 2022 by gaurav
• 23,260 points

edited Mar 5

Related Questions In PMP

0 votes
1 answer

What is the difference between a Project Manager and Scrum Master?

Scrum Master is the most misunderstood role ...READ MORE

answered Jul 24, 2020 in PMP by Gitika
• 65,770 points

edited Jun 27, 2023 by Khan Sarfaraz 1,082 views
0 votes
1 answer

Is scrum only for software development?

Scrum is not solely for software development. ...READ MORE

answered Jul 29, 2020 in PMP by Gitika
• 65,770 points

edited Jun 27, 2023 by Khan Sarfaraz 1,079 views
0 votes
1 answer
0 votes
1 answer

How using Scrum methodology it is possible to meet a strategic deadline?

Scrum's iterative framework and associated good practices ...READ MORE

answered Aug 27, 2020 in PMP by Sunandan Thakur

edited Jun 27, 2023 by Khan Sarfaraz 756 views
0 votes
1 answer
0 votes
1 answer
0 votes
0 answers

Scrum Framework/Methodology for Services/Operations too?

Just checking if Scrum Framework/Methodology is good ...READ MORE

Sep 22, 2020 in PMP by Rajiv
• 8,870 points
590 views
0 votes
1 answer
webinar REGISTER FOR FREE WEBINAR X
REGISTER NOW
webinar_success Thank you for registering Join Edureka Meetup community for 100+ Free Webinars each month JOIN MEETUP GROUP