Difference between Scrum Board and Kanban Board
I thought a basic board that consisted of columns of "To Do", "Doing" and "Done" was a basic Kanban board and in the same context used complementarily in Scrum as well.
Is there really a difference? What is it?
There is no mention of a board in the Scrum Guide. The only Scrum Artifacts are the Product Backlog, the Sprint Backlog, and the Increment. A board is simply one way to represent a Sprint Backlog, and in some cases, the Product Backlog as well.
Personally, I don't see a huge difference between a "Scrum Board" and a "Kanban Board". However, I would expect that a Kanban Board to make some of the principles of Kanban more explicit. The biggest thing I'd expect to see on a Kanban Board would be work-in-progress limits, but I may also see other methods of visualizing the workflow. Calling it a Scrum Board may imply that the focus may be more on state/status rather than workflow visualization and work-in-progress limiting.
I thought a basic board that consisted of columns of "To Do", "Doing" and "Done" was a basic Kanban board and in the same context used complementarily in Scrum as well.
That sounds more like an elaborate To Do list.
A Kanban board should represent a model of production which is subject to conservation of flow. Its policies ought to be explicit, the enumeration of states is not enough. A strategy of this nature may then be implemented in Scrum so predictability can be improved.
Kanban Board and Scrum Board are pretty much the same thing in reality. Both visualize the work, both typically have To Do, In Progress, and Done, and both are managed by the development team. The primary difference is that Scrum doesn't prescribe a "Scrum Board", instead it states there must be a Sprint Backlog, but doesn't advise how it should be configured. In Functionality, a big difference between these boards is the fact that Scrum follows a time box Sprint so the Sprint Backlog (Scrum Board) is short lived as it changes each sprint. A Kanban board is long lived with the project/product and can be cleaned up as needed or never; just depends on what the team wants for that.
In practice the only difference I have seen between Scrum and Kanban boards are that Kanban boards will include columns in the workflow that extend beyond just the Development Team. Since Scrum Boards are typically used for visualizing the Sprint Backlog, the workflow is usually just what is needed for the development team to deliver. In Kanban you will visualize the workflow that takes an item from idea to money so it will include columns for the Product group to do their due diligence of identifying opportunities and will also include columns for work done post "deployment" to get the features into the hands and in use by the intended audience such as Marketing Campaigns, User Training, etc.
BTW, I also agree with everything said above my comment.
I used a popular product management software for visualizing the Sprint. One of the board configuration options was Kanban. The only difference between this board and the non-Kanban board was the WIP (Work In Progress) limit. If the team limited the Sprint Kanban board to 34 (Fibonacci) the board would not allow you to pull more stories in until something was moved out or Done. The non-Kanban board allowed any number of stories.
Personally, I don't advocate for one tool over another. They are not what make Scrum successful. I've done just fine with Excel and super-sticky post-its on super-sticky flip chart papers on the wall.
Does that mean that "Scrum Board" term is OK to be used in Scrum ?