Once the implementation of a feature is done (including code review and testing), the next step in the process is a Demo. How a demo looks could vary depending on what precisely was developed. From a QA perspective there are a few reasons why the demo is important:
- Understanding the implementation down to the code level - this helps make informed decisions about the risks and testing associated with it.
- Getting another set of eyes of the feature now that it’s part of the product - this helps observe potential improvements (whether in UI, logs output, etc.);
- Hearing about what was tested, how that testing took place, and any relevant findings or troubles which took place along the way - this helps establish confidence in the quality, and may provide pointers as to further testing or test coverage that needs to take place.
The result of a Demo is a joint decision as to what should happen next - whether this gets merged and set to Done, whether further testing is needed, further adjustments are required, etc.
Note that in a truly Agile environment, anyone can slip in to the role of the QA engineer for the demo and take part in the discussion (whether it is another developer, a game designer, or an artist). For some areas (example UI/UX changes) it even makes more sense to include a different team members who has more experience in that area (such as game design or art). It’s up to the team to decide who should be present, depending on the contents of the implementation.