# data[].attributes.headline
Julian has to present his work more often because he does things and we need those things to be appreciated.

# data[].attributes.subject
Julian has to present his work more often because he does things and we need those things to be appreciated.

# data[].attributes.headline
Attempt to avoid large pull requests by merging into feature files. Another option is to create WIP pull request so people can see the progress as it is being worked on.

# data[].attributes.subject
Attempt to avoid large pull requests by merging into feature files. Another option is to create WIP pull request so people can see the progress as it is being worked on.

# data[].attributes.headline
If we have leadership attending within the upcoming sprint we should adjust our capacity in response to that.

# data[].attributes.subject
If we have leadership attending within the upcoming sprint we should adjust our capacity in response to that.

# data[].attributes.headline
Prakash is only allowed to look at things that affect the common code. He is no longer a mandatory reviewer, his participation is optional.

# data[].attributes.subject
Prakash is only allowed to look at things that affect the common code. He is no longer a mandatory reviewer, his participation is optional.

# data[].attributes.headline
We need to be informed of when there is system testing/factory testing.

# data[].attributes.subject
We need to be informed of when there is system testing/factory testing.

# data[].attributes.headline
Add value to future sprints by demonstrating the build/dashboard work. If we spend 4+ hours working on dlls and automating builds then we should probably highlight that during the demo.

# data[].attributes.subject
Add value to future sprints by demonstrating the build/dashboard work. If we spend 4+ hours working on dlls and automating builds then we should probably highlight that during the demo.

# data[].attributes.headline
During planning consider the DevOps work involved with each story prior to committing to it.

# data[].attributes.subject
During planning consider the DevOps work involved with each story prior to committing to it.

# data[].attributes.body
BLE Core iOS user story seems completed (it sounded like BIG work beginning of the sprint, worried us cannot be completed)

# data[].attributes.headline
Less WIP - More stories completed before last day

# data[].attributes.subject
Less WIP - More stories completed before last day

# data[].attributes.headline
When Mark and Orion have an interview on the last afternoon of the sprint it causes delay

# data[].attributes.subject
When Mark and Orion have an interview on the last afternoon of the sprint it causes delay

# data[].attributes.body
I would like to see this team focus on positive things that happen during the sprint as opposed to the negative. I feel like we have a gloomy overtone to our team right now and I don't want it to slide in that direction further.

# data[].attributes.headline
Design / end to end enrollment discussion

# data[].attributes.subject
Design / end to end enrollment discussion

# data[].attributes.body
API, Mobile and QA review we did for Enrollment end point was good. we should continue doing that for new end to end implementation we will do doing at start of the sprint

# data[].attributes.headline
Reprioritized midway through the sprint to make one mobile story a stretch goal.

# data[].attributes.subject
Reprioritized midway through the sprint to make one mobile story a stretch goal.

# data[].attributes.headline
The sprint was not like Thursday of this week.

# data[].attributes.subject
The sprint was not like Thursday of this week.

# data[].attributes.body
API POST /accessrights work became available for QA the evening of last day of sprint which did not give QA enough time to start on QA tasks

# data[].attributes.headline
There was an Engage release and I don’t think anyone on our team was involved. I didn’t even know it was happening!

# data[].attributes.subject
There was an Engage release and I don’t think anyone on our team was involved. I didn’t even know it was happening!

# data[].attributes.body
Most of the stories on the board were started on the first day of the sprint. Should we do a better job of working top down and trying to swarm on completion of one story at a time?

# data[].attributes.headline
Overcommitted from the start and moved every story into progress (we actually planned this way too, split up mobile to start on various stories).

# data[].attributes.subject
Overcommitted from the start and moved every story into progress (we actually planned this way too, split up mobile to start on various stories).

# data[].attributes.headline
Spec flow broken, someone overriding the branch policies

# data[].attributes.subject
Spec flow broken, someone overriding the branch policies

# data[].attributes.body
I think we talked about this during one stand up and didn't want to leave it off the retro board

# data[].attributes.body
For free and everything
#nonamefairgame

# data[].attributes.body
#congratsarna #itsaboy

# data[].attributes.headline
Functional test for BLE Core and BLE Credentials

# data[].attributes.subject
Functional test for BLE Core and BLE Credentials

# data[].attributes.body
We did not initially plan for it but as a team we are able to add those functional tests and complete it.

# data[].attributes.body
Perhaps we could have more numbers that are "positive" or "confident" - on a scale of 1-5, I feel 3 should be in the middle.

# data[].attributes.body
So we could focus on work

# data[].attributes.body
Don't have alignment with Bangalore on implementation and testing

# data[].attributes.body
DEVs being available to help QA as always. Thank you :)

# data[].attributes.body
Deployed Key Management 40 days ahead of schedule apparently :O

# data[].attributes.body
Thank you for the baby shower, yummy cake, cookies and goodies and presents!!! Means a lot.... thank you for much!!!

# data[].attributes.body
What are the real dates/deadlines for Sapphire? Does anyone know?

# data[].attributes.headline
Integrating at the SDK layer without full functionality causes confusion and unnecessary work

# data[].attributes.subject
Integrating at the SDK layer without full functionality causes confusion and unnecessary work

# data[].attributes.headline
Chris and Sarah learned vital first aid.

# data[].attributes.subject
Chris and Sarah learned vital first aid.

# data[].attributes.headline
Lots of commitments outside of the sprint. Full day commitments and partial day commitments.

# data[].attributes.subject
Lots of commitments outside of the sprint. Full day commitments and partial day commitments.

# data[].attributes.body
Commitments not met on API. Definitely impacted by interviews.

# data[].attributes.headline
Orion coordinated another successful Engage release

# data[].attributes.subject
Orion coordinated another successful Engage release

# data[].attributes.body
Lots of interviews

# data[].attributes.body
Being available and helping with functional test!!!

# data[].attributes.body
No more 30 min standup please

# data[].attributes.body
API team working well together

# data[].attributes.body
Karthik helped out with after hours release, performed

# data[].attributes.body
Going to hire someone soon

# data[].attributes.body
last minute help directing me why UUID was not working. Otherwise, i probably have spent hrs to figure it out :):):)

# data[].attributes.headline
Coordinated to deliver for Integration and system test

# data[].attributes.subject
Coordinated to deliver for Integration and system test

# data[].attributes.headline
Chris left the room, so he doesn't feel bad when we talk about him in retro

# data[].attributes.subject
Chris left the room, so he doesn't feel bad when we talk about him in retro

# data[].attributes.body
Took too long to write scripts for provisioning key vaults

# data[].attributes.body
Provisioning key vaults is fully automated for Sapphire

# data[].attributes.headline
This list is really long, and takes too long to read. Consider removing unnecessary items.

# data[].attributes.subject
This list is really long, and takes too long to read. Consider removing unnecessary items.

# data[].attributes.body
Why do we have sensitive production keys floating around everywhere?

# data[].attributes.body
Thinking about monitoring, alerting, production hardening "later"

# data[].attributes.body
Vindication change: feels like empty... some furnitures seem removed but it got bigger space for some of us to stand up

# data[].attributes.body
Cat pic during demo was blurry, less quality :)

# data[].attributes.headline
Kate posted the correct article about self sabatoge

# data[].attributes.subject
Kate posted the correct article about self sabatoge

# data[].attributes.body
It felt like we committed for more story points this sprint and we completed most of them

# data[].attributes.body
ENGAGE pre-production environments are very difficult to troubleshoot; wasted a lot of time trying to figure out how things were working

# data[].attributes.body
It was a short and successful release.

# data[].attributes.headline
Good balance of sprint focus and scope creep

# data[].attributes.subject
Good balance of sprint focus and scope creep

# data[].attributes.body
Something to try

# data[].attributes.body
Use scheduling assistant! This mostly applies to people outside this team, but thanks for the reminder Sarah.

# data[].attributes.headline
We should swarm on the first story of the board.

# data[].attributes.subject
We should swarm on the first story of the board.

# data[].attributes.body
(Mark disagrees for some reason)

# data[].attributes.headline
Break stories up horizontally so there aren't PR layers.

# data[].attributes.subject
Break stories up horizontally so there aren't PR layers.

# data[].attributes.headline
Not create stories for public endpoints until all private methods are complete

# data[].attributes.subject
Not create stories for public endpoints until all private methods are complete

# data[].attributes.headline
API team being supportive giving feedback on the tool we could use instead of CMS for AP stuff

# data[].attributes.subject
API team being supportive giving feedback on the tool we could use instead of CMS for AP stuff

# data[].attributes.headline
Find out Sapphire dates and share the location with the team.

# data[].attributes.subject
Find out Sapphire dates and share the location with the team.

# data[].attributes.headline
Don't integrate to SDK layer until we have full functionality.

# data[].attributes.subject
Don't integrate to SDK layer until we have full functionality.

# data[].attributes.headline
Pay better attention to points in relation to capacity

# data[].attributes.subject
Pay better attention to points in relation to capacity

# data[].attributes.headline
Communicate to leadership that releases should be done with zero downtime.

# data[].attributes.subject
Communicate to leadership that releases should be done with zero downtime.

# data[].attributes.headline
Talk to Firmware about their poor production key storage process. 

# data[].attributes.subject
Talk to Firmware about their poor production key storage process. 

# data[].attributes.headline
We need to be more optimistic during standups

# data[].attributes.subject
We need to be more optimistic during standups

# data[].attributes.headline
Not create stories for public endpoints until all private methods are complete

# data[].attributes.subject
Not create stories for public endpoints until all private methods are complete