# data[].attributes.body
1. Sprint Process

2. Building and deploying PMP, ALM, ALB

3. Building SSP, PC, Scholarships, HILR

4. Testing process

5. Application review training with Stakeholders

6. post go live support process

# data[].attributes.body
The amount of tickets / applications that got completed is truly amazing.

# data[].attributes.headline
Created some very well designed applications!

# data[].attributes.subject
Created some very well designed applications!

# data[].attributes.body
Good team work makes a good product.

# data[].attributes.headline
The fact that we are now in two production orgs and there has been no disruption to the user.

# data[].attributes.subject
The fact that we are now in two production orgs and there has been no disruption to the user.

# data[].attributes.body
Have only heard praise (with phase 2 requests) from our Users

# data[].attributes.body
shareable components across applications possible bc we got POs to understand the benefits of having applications work similarly. less complexity across our code base.

# data[].attributes.body
Being able to refresh and get the orgs up and running faster each time!

# data[].attributes.body
Used standard EdCloud Admissions and Recruitment data architecture and features, with less custom objects.

# data[].attributes.headline
We were able to detach from TargetX and think outside the box.  Leveraged Ed cloud

# data[].attributes.subject
We were able to detach from TargetX and think outside the box.  Leveraged Ed cloud

# data[].attributes.body
Collaboration between team members has been amazing.

# data[].attributes.body
Learned so much from the current legacy Org, and applied what were working and did different ways from what were not working. Thank you for the "legacy" Salesforce team.

# data[].attributes.headline
Consultant tickets should also be reviewed to see if they will affect QA scripts and thus need QA labels

# data[].attributes.subject
Consultant tickets should also be reviewed to see if they will affect QA scripts and thus need QA labels

# data[].attributes.body
Gathering test case requirements and defining the process for when and how they will be collected. Ideally, during UAT testing, testers should consider what scenarios and use cases need to be covered for automation test coverage.

# data[].attributes.body
Ability to limit the number of concurrent projects and leave room for the inevitably forced upon us Auth0, SF, Security patches.

# data[].attributes.headline
We need more granular project milestones.  There should be a deadline when portal instructions are finished and frozen vs a different deadline when new fields are requested, etc.

# data[].attributes.subject
We need more granular project milestones.  There should be a deadline when portal instructions are finished and frozen vs a different deadline when new fields are requested, etc.

# data[].attributes.body
To know what exactly needs to be tested once we deploy new Task. From Data Input to Application render Method.

# data[].attributes.body
QA automation scripts are now running in ed cloud. Please note that environment refreshes and developer changes can affect script execution. Changes in FullSB that are not reflected in SIT may require script updates.

# data[].attributes.headline
Better testing needed.  We need to write out testing scenarios for end users so they know what they are testing.  They also waited too long before they tested.

# data[].attributes.subject
Better testing needed.  We need to write out testing scenarios for end users so they know what they are testing.  They also waited too long before they tested.

# data[].attributes.body
UAT on feature changes shipping from devteam to fullsb, before available for actual UAT on fullsb by stakeholders and PMs.

# data[].attributes.body
We need to be able to stick to code freeze and not make changes at that point.

# data[].attributes.headline
Clear distinction about when to use omni vs flow

# data[].attributes.subject
Clear distinction about when to use omni vs flow

# data[].attributes.body
Follow a consistent deployment strategy and branching process to avoid deployment conflicts and rework.

# data[].attributes.body
Testing and QA- making sure we have a process for Dev, QA team, and users to follow.

# data[].attributes.headline
We've tried to stay standard but my concern is that users will continue to try to branch out and make a case for custom development.  We need to get better at saying no sometimes (with good reasons)

# data[].attributes.subject
We've tried to stay standard but my concern is that users will continue to try to branch out and make a case for custom development.  We need to get better at saying no sometimes (with good reasons)

# data[].attributes.body
I have major concerns that we have been "Sprinting" and will continue to while we finish the application project, migration project, and soon coming name change project. All this and we need to think about Phase 2 tickets.

# data[].attributes.body
The need for more resources for testing, and clarity around QA process.

# data[].attributes.headline
Stakeholders changing requirements on the fly

# data[].attributes.subject
Stakeholders changing requirements on the fly

# data[].attributes.body
Need to manage their requests better and evaluate change requests as things are being developed. Those last minute changes at hinder us and our work.

# data[].attributes.headline
I really hope Attain can help us deliver new functionality.  I'm not seeing a ton of signals yet.  Case Advising seems like we are taking a step backwards.

# data[].attributes.subject
I really hope Attain can help us deliver new functionality.  I'm not seeing a ton of signals yet.  Case Advising seems like we are taking a step backwards.

# data[].attributes.body
No Scott Hughes

# data[].attributes.body
Scott is leaving and so his expertise and knowledge. Scott has been helping the consultants to test and spending a significant amount of time to test the integrations per the frontend change. He know what should work and how should work on the current integrations in EdCloud with a deep understanding. I don't know what to do without him.