# data[].attributes.headline
What is the follow-up process for the retro notes after submitted into KB, if action needed?

# data[].attributes.subject
What is the follow-up process for the retro notes after submitted into KB, if action needed?

# data[].attributes.body
Do we create other esm requests right away or no? Who should do this?

# data[].attributes.body
From 2021/11/29 Retro Notes
https://kb.uwm.com/display/SERVICENOW/2021-11-29+Retro+Notes

Stage Based story task creation

Have certain workflow triggers to automate story administrative tasks

As scrumtasks get completed, automatically move the story along statuses.

# data[].attributes.headline
Come up with an exact structure for naming update sets. I don't think we ever truly decided on this?    INITIAL - EPIC - DESCRIPTION?  

# data[].attributes.subject
Come up with an exact structure for naming update sets. I don't think we ever truly decided on this?    INITIAL - EPIC - DESCRIPTION?  

# data[].attributes.headline
Add a step to make it more apparent there are pre-reqs or dependencies for a story or stories 

# data[].attributes.subject
Add a step to make it more apparent there are pre-reqs or dependencies for a story or stories 

# data[].attributes.body
Maybe a banner on the form of any story that meets those conditions, as long as the stories are still open

# data[].attributes.body
Should these be a new task for development instead of a new story? What do we do with the original story? Does it get set to cancelled, does it wait for the other story to be completed or to be tested and set to read for deployment?

This should be another dev task in the same story...

# data[].attributes.headline
Enjoy your trip to India, Fakiha! I'll take good care of your birds.

# data[].attributes.subject
Enjoy your trip to India, Fakiha! I'll take good care of your birds.

# data[].attributes.body
As any good snow pedant will tell you, the ‘white stuff’ isn’t actually white, but rather translucent. It’s the light reflecting off it that makes it appear white with the many sides of the snowflake scattering light in many directions, diffusing the entire colour spectrum.   Dust, pollution or cold-loving (cryophilic) fresh-water algae can colour it black, orange or blue. Pink or ‘watermelon snow’, caused by algae containing astaxanthin, a chemical similar to the one found in carrots, was mentioned in the early writings of Aristotle.

# data[].attributes.headline
Have a fantastic time in India Fakiha!!!!

# data[].attributes.subject
Have a fantastic time in India Fakiha!!!!

# data[].attributes.headline
Stop getting defensive when people disagree with ideas.

# data[].attributes.subject
Stop getting defensive when people disagree with ideas.

# data[].attributes.body
Nobody on the team is personally attacking other people. Sometimes we just disagree on how things should be done, and we need to work together to find the best solution.

# data[].attributes.headline
Making epics and stories for Clone/Upgrade tasks

# data[].attributes.subject
Making epics and stories for Clone/Upgrade tasks

# data[].attributes.headline
Continue thinking of ways to improve our processes.

# data[].attributes.subject
Continue thinking of ways to improve our processes.

# data[].attributes.headline
Using Jira naming convention for our stories

# data[].attributes.subject
Using Jira naming convention for our stories

# data[].attributes.body
If needed, we can put that together in the integration. Currently it adds a lot of noise to lists of stories

# data[].attributes.body
This would mostly help reduce potential double/triple counting points as part of the development and testing process. Developing these variables is typically done all in one go, so having one story reduces clicks/admin overhead when having to reference/close multiple stories/scrum tasks. Similarly, testing all variables as a part of that one story/scrum task would help reduce confusion of where variables that weren't defined in the current story are coming from.

# data[].attributes.body
Attachments create more work for everyone :(

# data[].attributes.headline
Making workflow stories for record producers

# data[].attributes.subject
Making workflow stories for record producers

# data[].attributes.body
Unless some sort of process is needed (i.e. approvals, creating additional records, sending specific notifications), record producers do not leverage workflows/flows

# data[].attributes.headline
Add a "Demo" state on stories. There is no middle ground from Testing>Ready for deployment. 

# data[].attributes.subject
Add a "Demo" state on stories. There is no middle ground from Testing>Ready for deployment. 

# data[].attributes.headline
Epic to track who the QM is. We still have a small disconnect on remembering who is the QM at the start of each week. A story that is pointed as a general workload will help realize the work we bring in during the sprint as well as a documented timeframe of who the QM was. 

# data[].attributes.subject
Epic to track who the QM is. We still have a small disconnect on remembering who is the QM at the start of each week. A story that is pointed as a general workload will help realize the work we bring in during the sprint as well as a documented timeframe of who the QM was. 

# data[].attributes.headline
New catalog items should not be taken at face value. There needs to be some kind of step in place to ensure the request makes sense, that the verbiage is clear and is grammatically correct. Most people have a general idea about what they want to happen but don't know how to think it all the way through. Functionality may be better handled a different way. Do we state *at the developer's discretion?

# data[].attributes.subject
New catalog items should not be taken at face value. There needs to be some kind of step in place to ensure the request makes sense, that the verbiage is clear and is grammatically correct. Most people have a general idea about what they want to happen but don't know how to think it all the way through. Functionality may be better handled a different way. Do we state *at the developer's discretion?

# data[].attributes.headline
Be cognizant of how we are speaking to one another. Snarky, condescending remarks bring down morale and devalue team members.

# data[].attributes.subject
Be cognizant of how we are speaking to one another. Snarky, condescending remarks bring down morale and devalue team members.

# data[].attributes.headline
We should not be discussing and solutioning during refinement. The purpose of refinement is to point the stories.

# data[].attributes.subject
We should not be discussing and solutioning during refinement. The purpose of refinement is to point the stories.

# data[].attributes.headline
When new projects are being spun up, Dev Solutioning needs to happen first. There needs to be a meeting scheduled to discuss all of the details so there is a solid sense of what the request is about and the best way to approach it.

# data[].attributes.subject
When new projects are being spun up, Dev Solutioning needs to happen first. There needs to be a meeting scheduled to discuss all of the details so there is a solid sense of what the request is about and the best way to approach it.

# data[].attributes.body
Do we (devs/admins) create additional test cases if needed? Ex. STSK0011437 / STRY0010073.
Test cases created before ticket was worked  (excel) and more test cases were added in the scrum view. We need to keep this in one place if we are adding test cases.

# data[].attributes.headline
How are we going to handle a story that ends up not needing to be done?  Just cancel it or what? For reference - STRY0010056 - Resolved in a SN Patch.  No work needed to be done.

# data[].attributes.subject
How are we going to handle a story that ends up not needing to be done?  Just cancel it or what? For reference - STRY0010056 - Resolved in a SN Patch.  No work needed to be done.