Memory Team - Repeatable process or Documenting use cases
Can we come up with a repeatable process? Is it important to come up with a repeatable process? Often, the Memory team will jump into a new area of code that is non-performant (memory, cpu, undefined). We will help to identify the deficiency, implement some level of improvements and then deliver a set of improvement issues back to the team responsible for that area of the product. Is there a generic template we should create for guidance for other teams to approach performance problems? Should we document the individual use cases instead so that others can pick and choose what methodologies work for them?
Perhaps this is a chicken/egg problem. By documenting the use cases we will likely identify repeatable processes.
Edited by Craig Gomes