# data[].attributes.headline
I think it would be beneficial to schedule ceremonies and other critical project meetings ahead of time so everyone can plan towards those events. 

# data[].attributes.subject
I think it would be beneficial to schedule ceremonies and other critical project meetings ahead of time so everyone can plan towards those events. 

# data[].attributes.headline
The desk checks were well run and informative. They made it easy to understand what work had been completed and answer open questions. They also made the demo run smooth. 

# data[].attributes.subject
The desk checks were well run and informative. They made it easy to understand what work had been completed and answer open questions. They also made the demo run smooth. 

# data[].attributes.headline
Coming out of the desk checks if we are accepting work lets update Rally so we know what is already complete in the sprint. 

# data[].attributes.subject
Coming out of the desk checks if we are accepting work lets update Rally so we know what is already complete in the sprint. 

# data[].attributes.body
Arran: We were missing sprint 0 :(

# data[].attributes.headline
Sprint 0 task such as ENV setup and low level code took away from velocity

# data[].attributes.subject
Sprint 0 task such as ENV setup and low level code took away from velocity

# data[].attributes.body
It went very well. Good team collaboration

# data[].attributes.body
Arran: It's good that we're not waiting for retro to tackle issues

# data[].attributes.body
Starting sprint 3 and so on, we will have sprint review and retro on every other Tuesday afternoon, and Planning on every other Wednesday morning. It will be important that everyone make themselves available for theses dates.

# data[].attributes.body
A lot of the Agile ceremonies are scheduled only hours before they occur.  We should have a set schedule so that attendance is better.

# data[].attributes.headline
Mobile testing started late in the sprint because of lack of Dev / QA environment

# data[].attributes.subject
Mobile testing started late in the sprint because of lack of Dev / QA environment

# data[].attributes.body
We don't cover shared components yet

# data[].attributes.headline
great demo, & use of time--even working around technical issue

# data[].attributes.subject
great demo, & use of time--even working around technical issue

# data[].attributes.headline
Bugs/issues found during the sprint could be recorded/traced somewhere  

# data[].attributes.subject
Bugs/issues found during the sprint could be recorded/traced somewhere  

# data[].attributes.headline
Front-end DEV should be 100% dedicated to project

# data[].attributes.subject
Front-end DEV should be 100% dedicated to project

# data[].attributes.body
Arran: The `npm install` builds a number of node_modules that have the relative density greater than a black hole

# data[].attributes.headline
Sprint 2 standups flowed more smoothly - we are now able to get through all updates in 15 min (and handle issues during "meet-after")

# data[].attributes.subject
Sprint 2 standups flowed more smoothly - we are now able to get through all updates in 15 min (and handle issues during "meet-after")

# data[].attributes.headline
Schedule meetings with more notice:  Review and Planning Ceremonies, Desk checks

# data[].attributes.subject
Schedule meetings with more notice:  Review and Planning Ceremonies, Desk checks

# data[].attributes.headline
Thanks to Arran for getting the Dev env into working condition

# data[].attributes.subject
Thanks to Arran for getting the Dev env into working condition

# data[].attributes.headline
Simple UI design, stable automation scripts.

# data[].attributes.subject
Simple UI design, stable automation scripts.

# data[].attributes.body
Arran: while we have columns, it's a bit weird

# data[].attributes.body
Create a plan to tackle refactoring, after backend is integrated as many placeholder href, text etc will change

# data[].attributes.body
Evan: I have run into a lot of roadblocks in my VM setup to get it working with the Front-End projects.

# data[].attributes.headline
UX takeover from Red seems to be a success

# data[].attributes.subject
UX takeover from Red seems to be a success

# data[].attributes.body
Good momentum between TRP and TEK on UX improvements

# data[].attributes.body
Arran: http://www.ideaboardz.com is not bad
Arran: Any tool that supports either/both +1 with voting

# data[].attributes.body
Decisions are made on the fly which makes sprinting easier

# data[].attributes.headline
Did not have enough time to write test cases. 

# data[].attributes.subject
Did not have enough time to write test cases. 

# data[].attributes.body
Without S0, set up activities are more impactful

# data[].attributes.body
Readyness of stories. Notices very little changes in AC's during the sprint

# data[].attributes.body
Everyone was available to help each other and discuss issues/ideas

# data[].attributes.body
To avoid overlapping

# data[].attributes.body
We may be repeating effort when all who are needed for a discussion are not present

# data[].attributes.headline
TEK Dev team is very responsive and helpful.

# data[].attributes.subject
TEK Dev team is very responsive and helpful.

# data[].attributes.body
Thanks to Team lead for Version Control help

# data[].attributes.body
Should be done at the end and devs should confirm changes after with UX

# data[].attributes.body
Arran: Speed now means slow later and we can't afford that
Kent Beck: It's not more features now vs cleanup now. It's features now vs features later. Don't act shocked when it's later and you chose "fewer".

# data[].attributes.headline
Testing locally on IE - have to switch to http

# data[].attributes.subject
Testing locally on IE - have to switch to http

# data[].attributes.headline
Bugs were fixed very quickly, thanks to all the dev's. This helps 

# data[].attributes.subject
Bugs were fixed very quickly, thanks to all the dev's. This helps 

# data[].attributes.body
Some design mock links are outdated, some acceptance criteria don't match the story

# data[].attributes.body
Arran: a 50/50 or fractional doesn't work

# data[].attributes.headline
Excellent support from TEK when issues in Design arise requiring changes in UI or even changes to AC. 

# data[].attributes.subject
Excellent support from TEK when issues in Design arise requiring changes in UI or even changes to AC. 

# data[].attributes.body
Perhaps I'm old school, but I think the team should make more use of the Agile room we have at our disposal.

# data[].attributes.headline
Good communication about how best to remedy changes/issue i.e. new story, defect, updated AC, etc...

# data[].attributes.subject
Good communication about how best to remedy changes/issue i.e. new story, defect, updated AC, etc...

# data[].attributes.body
We need someone to validate the versions and keep them up to date

# data[].attributes.headline
We are holding our retrospective (and doing it as one team)

# data[].attributes.subject
We are holding our retrospective (and doing it as one team)

# data[].attributes.body
Arran: Between vm's docker's, IDE's, and builds. 4 cores + 8 GB RAM is nothing

# data[].attributes.body
8 core + 32 GB would be ideal.

# data[].attributes.headline
Git merging related problems were resolved fast thanks to Arran 

# data[].attributes.subject
Git merging related problems were resolved fast thanks to Arran 

# data[].attributes.headline
TRP team collecting in the agile room when possible. If you are on site in RR lets get in the room especially for ceremonies.

# data[].attributes.subject
TRP team collecting in the agile room when possible. If you are on site in RR lets get in the room especially for ceremonies.

# data[].attributes.headline
Make an effort to use the Agile room when possible 

# data[].attributes.subject
Make an effort to use the Agile room when possible 

# data[].attributes.body
During many ceremonies, the TRP group seems split among the room and their desks - can we agree to use the room (schedule conflicts aside ?)

# data[].attributes.headline
Clarifying what backend work is being completed and where it does or does not align to the Front End work being completed. We can mock data but when will we see the two sides come together?

# data[].attributes.subject
Clarifying what backend work is being completed and where it does or does not align to the Front End work being completed. We can mock data but when will we see the two sides come together?

# data[].attributes.headline
Discussion from the TRP team when we are making decisions. TEK frequently chimes in with ideas and input the TRP side should mirror

# data[].attributes.subject
Discussion from the TRP team when we are making decisions. TEK frequently chimes in with ideas and input the TRP side should mirror

# data[].attributes.body
Arran: yes this is me making a +1

# data[].attributes.body
Sian to put in calendar

# data[].attributes.headline
Qa sub task to track dev issues.  Will continue for one sprint.  We might create tasks if we do not get proper tracking

# data[].attributes.subject
Qa sub task to track dev issues.  Will continue for one sprint.  We might create tasks if we do not get proper tracking

# data[].attributes.body
Dan to takeover scheduling of grooming sessions with Licia.

# data[].attributes.headline
Webstorm and Wallaby (Gabriel to take it up)

# data[].attributes.subject
Webstorm and Wallaby (Gabriel to take it up)