Child pages (Children Display) |
---|
...
Potential further discussions / steps
reviewing the Kanban board: are we able to make it more “user friendly” less cluttered.
guidelines for acceptance criteria / educating the clients on guidelines for acceptance criteriareview and revise content of the intake form →example mandatory repro steps and acceptance criteria fields.
writing a good bug issue report / templates / educating the clients on how to write a good bug report, log issues.review and revise content of the intake form →example mandatory repro steps and acceptance criteria fields. This is an example of one that was created for the RPAS team:
/wiki/spaces/DDMP/pages/1690763265
Ongoing discussions around best testing practices.
(TDD = writing failing unit tests, then writing the code to make those tests pass).
Whole team approach to quality: /wiki/spaces/DDMP/pages/2413101059Techniques how to best test fixes.
Templates?
Pairing → commonly used in agile/scrum to solve issues.
Possible topics for a later date.
guidelines for acceptance criteria / educating the clients on guidelines for acceptance criteria.
agreement on a definition of ready.“Definition of ready”: An example, from RPAS: /wiki/spaces/DDMP/pages/2404876328
agreement on a definition of done.“Definition of done”: /wiki/spaces/DDMP/pages/2404679736
the process for dealing with requests arising on short notice.
having the other CIVAV teams on the same page with respect to development process.