Scrum - Board

Giriş
Board'un okuması kolay olmalı. Açıklaması şöyle. Kanban yazısına bakabilirsiniz

Transparency is one of three essential pillars of the empirical process. Without it, you will be blind. So regardless of whether you apply Scrum or Kanban, the Scrum Board or Kanban Board needs to be easy to see and update, as well as provides the same understanding for all stakeholders.

Genellikle şu sütunlar yeterli

Todo, Development, Review, Acceptance, Done

Örnek
Bazen sütunlar şöyle oluyor

New | Consultation | Working | Waiting | Test & Review | Done

Açıklaması şöyle

Consultation = We need Feedback from someone outside
Waiting = Waiting for someone or something

Örnek
Bazıları biraz daha detaylandırıyor. Şöyle yapıyorlar

Open
Development
Ready for QA
QA
Ready for UAT
UAT
Done

Kanban'daki sütunlar da benzer. Open, In Progress, Development Done Scrum sütunları ile aynı gibi. Açıklaması şöyle.

We have a board with tasks in columns. A developer picks a task in "OPEN" and starts working on it. As he does that he moves the task to "IN PROGRESS". When he is finished the task goes to "DEVELOPMENT DONE" (later into testing). But if something goes wrong the task should be moved into "FEEDBACK" where something needs to be resolved. Maybe design is missing or some description is unclear...

İçe Dönük Kişilik - Introvert
Board'un içe dönük kişiliklerde faydalı olduğu söyleniyor. Açıklaması şöyle.

Because Agile makes it possible for teams to rely on visual communication and tracking more than on in-person data presentation and direct engagement in face-to-face communication, all team members can easily stay informed and engaged in the work, no matter each individual's comfort level with in-person interaction.