Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
The Mini Book of Agile

You're reading from   The Mini Book of Agile Everything you really need to know about Agile, Agile Project Management and Agile Delivery

Arrow left icon
Product type Paperback
Published in Mar 2022
Publisher Packt
ISBN-13 9781803238715
Length 50 pages
Edition 1st Edition
Concepts
Arrow right icon
Author (1):
Arrow left icon
YESI EDUCATION YESI EDUCATION
Author Profile Icon YESI EDUCATION
YESI EDUCATION
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

1. Chaper 1: Introduction
2. Chapter 2: What is Agile? FREE CHAPTER
3. Chapter 3: Why go Agile?
4. Chapter 4: How it all began
5. Chapter 5: The Different Agile Methodologies
6. Chapter 6: Agile Principles
7. Chapter 7: The Agile Culture
8. Chapter 8: Agile Roles
9. Chapter 9: Agile Concepts
10. Chapter 10: Agile Artifacts
11. Chapter 11: Agile Rituals
12. Chapter 12: Agile Tools
13. Chapter 13: Agile vs. Waterfall
14. Chapter 14: Agile FAQs
15. Chapter 15: Agile Myths
16. Chapter 16: The Agile Knowledge Base | AgileKB.com

Chapter 10: Agile Artifacts

The Agile Kanban Board

The Agile Kanban Board or simply Kanban Board is probably one of the most important (if not the most important) Agile artifact. It allows Agile teams to easily keep track of project status and next steps. 

An Agile Kanban Board can be physical, digital or both, although I generally recommend the digital version using tools like Trello or Jira. 

When physical, most teams will use a whiteboard, cardboard, paper board or something like that with post it notes. And they will write their user stories in the post it notes.

The Agile Kanban board typically consists of the following columns:

  • To Do
  • Doing
  • QA (Quality Assurance)-an optional column
  • Done

Within those columns the Agile team places the user stories they're working on in a particular Sprint & they move them between the different columns to reflect the current status of a user story. So for example, if the team has completed a user story...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image