After a few brainstorm->plan->work->compound cycles, there's bound to be bugs and slight errors that are caught. I've found that running postmortems on bug fixes (and committing documents) helps in future work, but I haven't figured out exactly what shape the skill or documentation written should have.
Thoughts on official support for something like that?
After a few brainstorm->plan->work->compound cycles, there's bound to be bugs and slight errors that are caught. I've found that running postmortems on bug fixes (and committing documents) helps in future work, but I haven't figured out exactly what shape the skill or documentation written should have.
Thoughts on official support for something like that?