Loading
Because a board is a spatial view and space runs out. Ninety cards in four columns is a scrolling exercise, and comparing two tasks means holding one in your head.
The list view shows tasks as rows — name, owner, status, dates, estimate — sortable and groupable, for reading many at once.
Rows sort and group by any field, and edits happen inline. It is the same tasks as the board, so nothing needs syncing between the two.
A backlog review covers ninety items. Grouped by phase and sorted by estimate, the unestimated ones surface immediately and the ordering conversation is about ten items rather than ninety.
It will not visualise flow. Seeing where work is piling up is what the board is for.
It shares its filters with the board and the table, so a view built in one is available in the others.
Yes, including status, owner, dates and estimates.
Yes, personally or shared with the project.
Two levels — phase within owner, for example.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.