Added Definitions of Done, first version.

[michaelkleinhenz]

Added a first version of the DoD.

[michaelkleinhenz]

To kickoff the discussion, one of the suggestions is that UX implementation is not part of the DoD. That makes sense where UX is not available yet but we are ready to implement the functional reqs. In such a case, a later story would add the UX design. Sounds like a practical thing to do.

The problem with the approach is, that at the time of the story estimation and acceptance at the start of the sprint, it might not be clear if the UX is available or not. This is a problem for the estimation and popped up yesterday already. In some cases we don't know if we can implement the UX in the current sprint or not.

My suggestion for this situation would be:

1. we define in the story if the UX is part of the story or not explicitly based on the then-available information. Both ways are explicitly noted in the story description (UX required/not required).
2. if the UX becomes available for a "no UX required" story while the sprint is running, we consider the implementation like all "added values" of an implementation as a stretch goal that we fit in as time allows.

The real change here would be, that we now state explicitly on every story if UX implementation is required. That would prevent confusion and would make estimation more reliable

[Mgranfie]

@michaelkleinhenz Not sure if I am following. UX marks our stories in GIT, "Ready for Dev" and notify Joshua and or the active dev. This would signal that the story is ready to go and that the UX Design is done. The links to all the designs and UX stories in JIRA are provided in the GIT story. Anyone can join our JIRA with a RedHat account.

It sounds like we have two cases to consider for Dev:

1. When Dev is ready to implement functionality and there is no UX design ready:

• It would be great to avoid this situation by planning with UX so that we can vet any implementation issues around the design, early on, before implementation, rather than having to go back and make changes.
• Vetting features down to MVP and phased roll outs will help to minimize the chances of design and dev moving out of step. Fast and focused : )
• We can continue to work on coordinating our efforts, and communicating around our story maps.

1. There is a UX design ready:

• UX marks the story in GIT as "Ready for Dev" and tags Joshua and or the Dev on the feature.
• UX places the links to the JIRA story, as well as, the InVision designs.

If the issue of when is the UX marked done for the product, after development, there had been some discussion around this being a verification criteria, that dev and UX meets to review the build and works through any outstanding issues to agreement.