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 criteria.
writing a good bug report / 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.
agreement on a definition of ready.
agreement on a definition of done.
the process for dealing with requests arising on short notice.
having the other CIVAV teams on the same page with respect to development process.
Add Comment