Definition of Done (aka DOD) is a tool to help your team get aligned on bandwidth availability, so I've always aimed to keep it simple, and universal. DOD = Less than 5% chance you're going to get pulled back into the "Done" task or project the following day. If this isn't the expectation that gets communicated it becomes hard to enable a culture that encourages accountability, and easier to slip into endless progress reports and missed deadlines. How does your Product team define DOD?
When I had support and clear definitions from the client or colleague, the steps to reach DOD were structured well enough. In the final stages of design, there is a sync that is kind of like a handoff meeting for the team, including a product manager, developer, designer, and marketing. In this meeting, if all of the team members have no hard setbacks and the project seems doable within the next sprint, we consider the product work done and prepare an agreement summary with the next preparation for the next phases.
Product Designer @ Stigg 🤘🏻 • Product Design Mentor @ Startup Designers 🎯 • All things Apple • BRING THEM HOME NOW! 🎗️
5mofrom a single-designer point of view - once the initial design is approved by the product, it goes to development, towards the end of the dev cycle we perform an acceptance round to make sure all requirements met, the consistency of the design (and layout) is met and all is functioning as expected before releasing it, and then iterating on what released and observing how customers behave on it.