# data[].attributes.headline
SM look into dev points with Kendall and dev only, dev task only issue not working with our pointing system

# data[].attributes.subject
SM look into dev points with Kendall and dev only, dev task only issue not working with our pointing system

# data[].attributes.body
Dev ahead of QA due to being great at their work, already working off the backlog. If they work on issues outside of the sprint without any dev task only issues, their work still gets taken into account. We are also wrapping up Vault, so they are working on clean up issues and recently started working on mailing address. They don't have any other issues to pull from. ----Maybe look into having a bonus board similar to ATS - SM suggestion

# data[].attributes.headline
Great leadership and support from Kendall with dependencies and dev plan of action

# data[].attributes.subject
Great leadership and support from Kendall with dependencies and dev plan of action

# data[].attributes.body
If outstanding issues are not a part of our A/C, we'll create a separate issue to handle it. However, if we can handle the OI within the current sprint, under the same issue, we can do that. As long us we are able to complete our commitment.

# data[].attributes.headline
Kendall's plan of container and branches were great last sprint with all the dependencies

# data[].attributes.subject
Kendall's plan of container and branches were great last sprint with all the dependencies

# data[].attributes.headline
Reverted issue due to Kendall being able identify the dependency on Rise's issue

# data[].attributes.subject
Reverted issue due to Kendall being able identify the dependency on Rise's issue

# data[].attributes.body
The Sprint and the CAT too

# data[].attributes.headline
Frequent PayCard API issues (their end) 

# data[].attributes.subject
Frequent PayCard API issues (their end) 

# data[].attributes.body
We averted disaster regarding to the dependency to Rise's issues.

# data[].attributes.headline
Great meeting and discussion with DB Team on the data fix issue.

# data[].attributes.subject
Great meeting and discussion with DB Team on the data fix issue.

# data[].attributes.body
Got to learn the big picture. Good communication there, across the team module. Having that meeting was a good idea.

# data[].attributes.body
Everything got done... yet again!

# data[].attributes.body
We should have been told about the new marketing page needing approval from 'higher authorities' a lot sooner.

# data[].attributes.body
QA/Dev collaboration on mailing address OI's

# data[].attributes.body
15

# data[].attributes.body
-Resources Points of Contact Page, what all do we want on this page?
-Request from product
-Tag  Cissy on the issue and SM
-Notify us via Teams channel
-Notify us verbally
**Tag leadership as necessary

# data[].attributes.headline
Do we have a clear understanding of how to handle issues out of scope/outstanding issues outside of our A/C? ex. UI outstanding issues

# data[].attributes.subject
Do we have a clear understanding of how to handle issues out of scope/outstanding issues outside of our A/C? ex. UI outstanding issues

# data[].attributes.headline
How do  you feel about dependencies? Are we doing okay at identifying them? How could we improve?

# data[].attributes.subject
How do  you feel about dependencies? Are we doing okay at identifying them? How could we improve?

# data[].attributes.headline
How would you rate sprint 15 on a scale of 1-10?

# data[].attributes.subject
How would you rate sprint 15 on a scale of 1-10?

# data[].attributes.body
Please discuss any trouble with rollover issues, dependencies, impediments, etc., if applicable.