Talk:Abstract Wikipedia team/Definition of Done

Great work driving the DoD, but how will we make sure to follow through with it?

Thanks.

To follow through with it I believe we need to:

• Have a DoD that is helpful and covers our needs, without adding more friction to our process: It's been a long period of DoD drafting, getting feedback from the team, creating phab templates and modifying the templates and checklists according to the feedback, so hopefully I've managed to do that.
• Understand this document as a team-owned effort, even if I was the one to start it, templates and checklists should be co-owned, alive and dynamic, and always adapt to changes of the team and their needs. For example, as soon as we launch, the Completion Checklists will have to change, or now that we are onboarding a QT engineer the templates might have to adapt to their own process.
• Task assignee and reviewer need to know of the existence of completion checklists and use them as a tool to: 1) mark a task as ready for review and 2) mark a task as done.
• Anyone that creates a task should be able to give sufficient information in the description so that the reviewer can easily check its completion, and the templates are designed to capture that. This requires the active involvement from everyone in the team.

I see the note that the tests should pass, but I don't see a note describing what kind of test coverage should be written alongside the project