MicrosoftCostas Constantinou this is because they, as programmers, are developing a solution to their problem as programmers and not for the general workplace. The 500 limit is because they are running a SCRUM for programmers, not a Kanban (yes, she incorrectly referred to it as a Kanban, and mispronounced it.)
A Kanban is like a job board and every "Task" is a "Project/Plan". The actual terminology they use is antithetical to how a Kanban works and entirely in the SCRUM Agile method.
"Tasks" in a Kanban board ARE the projects, and the check lists on the "Tasks" are the tasks for the individual project. The "bucket" for the "Tasks" (Re: Projects) are the stage in the workflow from start to end. "Tasks" (Again, RE: projects) don't typically last more than a few hours to two weeks in a Kanban.
The project board in an SCRUM is the project, and the "tasks" are the checklist for the project. The bucket for the tasks are the stages of development the tasks are in for the project. Most tasks within a project in a SCRUM don't typically get finished sooner than a week, and can take up to a month. Watch the video again. Her Gantt charts span weeks for projects, whith each having their own board.
This is a fundamental difference in use case for Planner vs Project. Planner is more Kanban based (but they keep trying to make it SCRUM), while Project is SCRUM oriented.
