This is Part 1 in a series on Kanban’s delivery best practices.
Much of a project manager’s job requires a wrangling of tiny details. The more complexity there is in the design, the more details will come out over the entire course of the project. Every touch point adds to our understanding of how the client expects their functionality to work.
Some project managers keep a record of everything that occurs in every meeting. This serves a CYA purpose, but it can create too much documentation to take action on. A comment repository only tracks decisions and remarks about the functionality of what is being built. We use it for creating and updating our functional specs and for refining our QA test scripts.