Skip to content

Sprint Logs aka Our Decisions, Reasoning, and Next Steps

Kathleen Lueckeman edited this page May 5, 2022 · 3 revisions

Here's a record of what was accomplished in each sprint.

2022 May Sprint (Virtual)

We focused on updating the architecture/configuration and the UI.

Next Steps

  1. Update sample data: Remove the Registrar Office record to which the Course object's Department field looks up to, so that it looks up directly to the Educational Institution Account.

  2. Create a second version that will work with Student Success Hub objects.

2021 October Sprint (Virtual)

We had two workflows: Dev and Doc

Dev:

  • Created an app
  • Created two screen flows as the start of data intake from a transcript (currently only a 1:1 match)
  • Created Lightning record pages for ???
  • Updated the sample data set

Doc:

  • Updated the wiki pages and also helped create object and field reference documentation.
  • Documented the use cases in more detail.

Next Steps:

  • Update the ERD with Education History (and link Transcript to that instead of Application)
  • Add new fields to Transcript and Transcript Course.

2021 June Sprint (Virtual)

The team analyzed and adopted the vision from previous sprints. It updated the ERD from the Detroit sprint to reflect the new objects added during the Philly sprint.

The team proposed removing the relationship from Course Transfer to Program Plan, since it's related to Course and the Philly sprint introduced an object related to Course to store rules associated with the Course (e.g., program-specific rules). The team also proposed updating the solution to include Affiliations, Application and Education History. We moved Course Transfer to Course in the ERD.

Next Steps:

  • Update the ERD and replace the one in the Resources link.
  • Configure the relationships with the existing EDA objects proposed by this project team.
  • Refresh the data in the repository to include data for these new objects.

2019 Philly Sprint

Decided that in the ERD Course Transfer would move to Course (based on input from Matt B in Philly - then change in the org was made in June.

2019 Detroit Sprint

The project team created a schema, some record types (Course: External and Internal), and an outline of the setup guide. The group tackled these tasks and flows:

  • Define common use cases and parameters
  • Define extensible Data Model to track pre-approved or past credit transfers. Include examples
  • Define search criteria and algorithm to match pre approved credit transfers
  • Define UI to allow end user to search for pre approved credit transfers based on the previous criteria