# data[].attributes.body
Can the Copy Deck review process be shortened in any way, or adjusted to allow for 1 day for Content Team to review Copy Deck BEFORE it routes to client for final approval? Content team can catch any CMS functionality gaps early.

# data[].attributes.body
The Content Team created a basic Confluence page to track product-correct features

# data[].attributes.body
To eliminate uploading of wrong assets, eating up memory, and breaking old links to assets, is there a window to have Creative and Product Specialists review final exported assets BEFORE they are uploaded in the CMS?

# data[].attributes.headline
Final Storyboard & Copy Deck needs to be aligned and actually "final"

# data[].attributes.subject
Final Storyboard & Copy Deck needs to be aligned and actually "final"

# data[].attributes.body
There should not be any "TBD" info or out-of-sequence images for Content Team to chase down

# data[].attributes.body
15-min daily small group meeting (but open door policy for CE, Creative, etc.) to open up face-to-face time and fewer e-mails

# data[].attributes.body
Content team is recommending that the group QA a finished site in one room, with one person logging tickets, to reduce duplicate tickets and delayed feedback

# data[].attributes.headline
Minimize impact of Legacy code and processes

# data[].attributes.subject
Minimize impact of Legacy code and processes

# data[].attributes.headline
Better way to Track Client Reviews for clients for each sprint/items in each release. 

# data[].attributes.subject
Better way to Track Client Reviews for clients for each sprint/items in each release. 

# data[].attributes.body
Designs, Annotations, Dev Demo

# data[].attributes.headline
Analytics Team not looped in at the right time

# data[].attributes.subject
Analytics Team not looped in at the right time

# data[].attributes.body
We are involving WI team late in the game sometimes. This also applies to MediaVest and Flood Tags. Send Launch Calendar to WI team.

# data[].attributes.body
Dates are being missed by RPA. Need to pressure clients to help ensure schedules are adhered to.

# data[].attributes.body
Every individual needs to be accountable to resolve tickets assigned to them. Make sure people are aware of the timeline and when things need to be done and tickets closed

# data[].attributes.body
We should push back and protect ourselves against the endless rounds of reviews.

# data[].attributes.body
All prev released vehicles are tested prior to releasing a new vehicle - expectation was that vehicles would be handed off to maintenance team. when will this happen? Redesign QA team is not staffed for this regression testing

# data[].attributes.body
We have to improve here and better understand when things are in/out of scope. We have been presenting things and having to go back and tell clients they are out of scope. Clients have also been requesting things and it has not been made clear to them what is in/out of scope.

# data[].attributes.body
Should be one ticket per copy deck

# data[].attributes.body
Stop using the wrong version of the copy deck and ensure updates are captured in one place of truth.

# data[].attributes.headline
Less  Working Session Meetings & Less Meetings

# data[].attributes.subject
Less  Working Session Meetings & Less Meetings

# data[].attributes.body
All meetings should not be working session. Pre-meeting work should be done.
Meetings should be looked at and attendees should be re-evaluated

# data[].attributes.body
Shopping Tools, Honda, and ISD made themselves available to review things whenever we needed them to.

# data[].attributes.body
We got really good at planning and specially for Ridgeline

# data[].attributes.body
Despite late assets the CE team kept at it to provide the team the assets, and although we got them really late, we over delivered, but the client may not be aware of appreciative.

# data[].attributes.body
Team was very flexible and they rocked it as well.
This team also stepped up and did production work at times that saved us.

# data[].attributes.body
ISD Support was great, though sometimes the tone wasn't great, but they supported us..
Client was flexible and accommodated our shifting timeline. This also includes Web Intelligence tags and publishing them

# data[].attributes.body
introduction of a second release track, I don’t think we’re staffed for proper coverage on both

# data[].attributes.body
Getting better and managing our sprints and meeting out commitments.

# data[].attributes.body
They are not helpful. Need to surface this to clients. More hurt than help.

# data[].attributes.body
AHM has no visibility into what we are doing. We need to show our work and show them they are getting something for their $$$

# data[].attributes.body
Can these teams work directly in JIRA - PMs chasing status is not effective

# data[].attributes.body
Need a process around the management of these requests

# data[].attributes.body
These are a must. Cannot have clients seeing things for the first time during UAT

# data[].attributes.headline
Stop loading / using the wrong copy deck 

# data[].attributes.subject
Stop loading / using the wrong copy deck 

# data[].attributes.body
Always make sure we are clear on what version of the copy deck is the APPROVED version and that has been used and if not be clear it is the wrong version

# data[].attributes.headline
Need to know what's not going to make it into the release sooner

# data[].attributes.subject
Need to know what's not going to make it into the release sooner

# data[].attributes.body
If things are falling out of the release we need to know sooner.  Before UAT at the very least.
These need to be communicated via the PMO Dashboard.

# data[].attributes.body
Referring to sprint 9 recap, handing stories off to QA on the last day of the sprint does not mean that those stories are “done”

# data[].attributes.headline
Better Communication Leading in to Launch

# data[].attributes.subject
Better Communication Leading in to Launch

# data[].attributes.body
Need to communicate daily leading to launch on when these items are taking place: code push, content push, regression testing, UAT . As well as what environment to review in. What plans are for weekend work etc.

# data[].attributes.body
Determined yesterday may have been a result of the Sitecore caching problems, also we may have been publishing to the wrong targets

# data[].attributes.body
Need a process for UAT comments making it back into the copy deck

# data[].attributes.body
Product review was a big miss: inaccurate data, lots of errors and inconsistencies which lead me to believe that product is not reviewing pages before launch

# data[].attributes.headline
CE/PM/FA need to be involved in CRUX/Tech Decisions

# data[].attributes.subject
CE/PM/FA need to be involved in CRUX/Tech Decisions

# data[].attributes.body
NO MORE tech/creative decision making without CE/PM/FA knowing and client signoff.

# data[].attributes.body
Handoff, End of week and sprint-end recaps needed to communicate progress and raise any delays in the schedule

# data[].attributes.headline
Need Creative & Product Deliverables on Time and Need them to be correct

# data[].attributes.subject
Need Creative & Product Deliverables on Time and Need them to be correct

# data[].attributes.body
Need more management over creative and product needs/balances - someone has to help police their workload and prioritize.
Who ever is working with John Fallon should meet and understand the AHM process so we don't have disconnects

# data[].attributes.body
Dev has been doing a better job of implementing against the specs, need to keep up this trend to have successful handoffs

# data[].attributes.body
Internal delays on reviews, end up eating into client time.

# data[].attributes.body
Needs a team to get the release out the door,  do we need to provide more visibility to all team members on schedules and what they mean for each discipline, and commitment from all team members....don't leave QA holding the bag

# data[].attributes.body
If you have a ticket assigned to you for a release, address it

# data[].attributes.body
Staging pushes – don’t push the button and run – need someone to be on call to troubleshoot

# data[].attributes.body
No clear direction after each content push to stage as to what was testable, frustrating for authors as things would be fixed on CA

# data[].attributes.body
Issues with code being checked into wrong branch or checked in after code freeze

# data[].attributes.body
Dev quickly addresses bugs and kicks back to QA for re-testing

# data[].attributes.body
BAP specs not accurate - testing not effective

# data[].attributes.body
Way too much overtime worked - lets work smarter. Stop adding people because we're working too long.

# data[].attributes.body
QA never had a good opportunity to do regression test on builds prior to launch

# data[].attributes.body
Dev resources swapped across Acura/Honda tracks

# data[].attributes.body
CE team became the content QA team and rocked it

# data[].attributes.body
Team dug in and got it done – great commitment

# data[].attributes.headline
                                      Opportunities

# data[].attributes.subject
                                      Opportunities

# data[].attributes.headline
                                   Stop Doing

# data[].attributes.subject
                                   Stop Doing

# data[].attributes.headline
                                          Did Well

# data[].attributes.subject
                                          Did Well