Design feedback update #106
Conversation
Added a TOC Added additional content to clarify goals.
Added a TOC Added clarification that Design Reviews are an opportunity to get feedback.
Cross-posted to design review guide.
Replaced content with the content from confluence. https://labzero.atlassian.net/wiki/spaces/PDE/pages/1967259693/Epics+and+User+Stories
Added new page on ticket structure, updated title for writing user stories.
Added new page for ticket specifics
Added images from confluence for structuring tickets
deleting so I can re-add with dash in the title
fix typo in file name
adding links to the structure guide
Removed Steve Bockman article. It's a 404. and I can't find a replacement article to link to.
|
|
||
| ## What is needed before we write user stories? | ||
| - Epics describe the vision and the outcomes we are striving to achieve and how we intend to measure success. | ||
| - User stories generate empathy and alignment around a discrete effort and how that work will benefit the user. Writing user stories helps us come to an agreement on what needs to be done and what criteria we will use to tell when the work is complete. |
There was a problem hiding this comment.
Should we mention that Epics are composed of a set of stories? Epics are high level visions or large slices of functionality? And stories are individual discrete pieces of work in the epic? (need better word smithing here)
There was a problem hiding this comment.
@katebennet would you be able to address @Shiun's content questions?
There was a problem hiding this comment.
Contenders in this context == candidates? It seems like these two terms are interchanged in the pngs.
Maybe clarification isn't necessary since this is just an example of the structure of the speclet, not the content itself.
| Initiatives are a collection of epics that drive towards a common goal (for example: “expand in to Australia” or “launch a new product that decreases costs by 7% this year”). An initiative is broader than a single epic, and may span multiple teams and multiple quarters. | ||
|
|
||
| ## Epics | ||
| Epics convey the overall big picture priorities. They contain a group of stories (on a particular theme) that are too big to be described by a single user story. Epics are written concisely and in a way that is simple to understand. |
There was a problem hiding this comment.
"They contain a group of stories (on a particular theme) that are too big to be described by a single user story. Epics are written concisely and in a way that is simple to understand."
OK it looks like we mention it here. (re: Epics = group of stories) Maybe same reiteration can be placed to my earlier comment above? (https://github.com/labzero/guides/pull/106/files#r1520446023)
There was a problem hiding this comment.
This looks good. The content of the speclet png probably don't need to be address since it's not relevant to the guide. Especially since the example speclets are referenced for their structure, not content.
Maybe a re-interation of Epics being composed of stories would be a good edition in the definition of Epics/Stories.
Otherwise, looks great!
Updated The Design Review Best Practices and Giving + Receiving feedback guides.
Added a TOC to each and small content changes for clarity.
Also added a cross-link from G+R Feedback to Design Review