# data[].attributes.headline
Read stories carefully before starting and gather as much resources to have the story completely finished prior to putting into Ready for Testing 

# data[].attributes.subject
Read stories carefully before starting and gather as much resources to have the story completely finished prior to putting into Ready for Testing 

# data[].attributes.body
If any action items are needed coming out of a retro, whoever lead it needs to submit the requests. I also think it should follow the naming standard of: Retro AI: TEXT
so we know right away the value behind it in the backlog.

# data[].attributes.body
I keep hearing a lot of questioning around testing. "I think so-and-so meant this or that." Reach out directly to the person that tested and ask them what they meant. This will alleviate possible confusion and re-work.

# data[].attributes.body
Waffles for sure.

# data[].attributes.headline
Making stories for instance upgrade/patch testing/review

# data[].attributes.subject
Making stories for instance upgrade/patch testing/review

# data[].attributes.headline
Waffles are the powerhouse of breakfast! Good luck building a pancake house! #waffleHouseForTheWin

# data[].attributes.subject
Waffles are the powerhouse of breakfast! Good luck building a pancake house! #waffleHouseForTheWin

# data[].attributes.body
WAFFELSSSSSSSSSSSSSSSSSSSSSSSSS

# data[].attributes.body
We need to have better communication across the team when our work processes change or get updated. I've heard casual conversation about something that was added (text, notification, etc.). Everyone needs to know how/what is affected in our work process. We all need to be on the same page.

# data[].attributes.body
AC and test cases need to be written accurately and match. In some scenarios, testing passes or fails based on the testing steps but is then sent back for additional work or questions because it doesn't match what is in the AC.

In other scenarios, the AC is correct and the test case is wrong. The tester fails the story because they are testing the incorrect catalog item.

# data[].attributes.body
I've noticed that a client will comment on an existing request asking a question and it will be ignored for weeks/months. Everyone needs to pay attention to their emails for those types of comments. It looks bad on our team and we need to improve on that.

# data[].attributes.body
Things change. Testing fails. 🤬 happens. We need to stop getting so worked up with these kinds of things happen. It's part of life. These things happening are never a personal attack against people. We need to stop getting so worked up about these things happening.

# data[].attributes.body
Mostly for the Queue Manager type of tickets.  We seem to be having some Skipped Approval tickets taking longer to resolve than they should be.  I know that our hands are a little tied at the moment as we cannot update the groups ourselves, but we need to stay on top of these tickets to ensure everything is resolved asap.