When you join a running project — as a lead, an architect, or part-time — your hands itch to start fixing things right away. There it is, the crooked deploy; the database without indexes; the service nobody has touched since last year. Stop. For the first week you fix nothing at all. This article covers "Track 0" from the project order map : how to take an honest snapshot of a project's state in one week. I'll show it on a real example — a growing gamedev project I joined to bring order to. ...