Bertrand Meyer's article "Making sense of agile methods" (PDF, November 2017)
Russian translation published in "Open systems" magazine N°2-2018 "Об Agile по гамбургскому счету"

Some citations (I completely agree according to my experience).

Everything will look fine until you suddenly discover that the next user story conflicts with previously implemented ones, and you have to go back and rethink everything

SQL Server Profiler has the template "locks" that is intended especially to trace deadlock. Let's try to simulate and catch a deadlock situation.

Suppose the test database is named test. Create two tables and feed them some data.

In the case of linked circular list you need to add some checks to avoid memory corruption.

Full example (compiled OK with GCC 8.x)