There are a few artifacts that are core to an effective development process. Here I catalog both my preferred approach for the established ones as well as those that I have created in my own evolution of the practice.
I tell classes that a backlog is to a development team as raw materials are to a manufacturing process. Quality material flows well through the process. Poor materials move roughly, damage the system itself, and produce sub-standard outcomes, like pouring cement mix into a wood chipper.
I have seen many efforts to replace physical boards, and I have yet to see an alternative serve the same purpose.
The up-to-the minute visualization of work flowing through the team provides great value, but it doesn't provide the full picture of the trajectory of the work committed for the cycle.
The schedulable work is just one part of what happens in a cycle. Development Logs are an artifact for capturing a more holistic picture of team cycles.