Sprint 5 Demo Updates
ÌýSprint 5 progress across BuffET platform business capabilities and epics.
Quick Summary
Sprint 5 focused on Alerts & Outreach, Advisor Availability and Appointment Scheduling in Salesforce Education Cloud. The sprint introduced new course-alert workflows, outreach assignment and follow-up functionality, advisor notifications and appointment-related communications. Teams also shared progress on the new Marketing Cloud environment that will support CRM05 communications. Demonstrations showed how advisors can respond to course alerts, track outreach activities and receive notifications about appointment changes, while students receive updates about missed appointments.Ìý
Ìý
Ìý
Project Update
Sprint 5 marked the completion of the fifth of nine planned build sprints. Sprint 5 testing was scheduled for July 14-16, followed by Sprint 6 development from July 15-31. Project leaders noted that all demonstrations were conducted in a sandbox environment using fictional data rather than student records.Ìý
Ìý
Sprint 5 work centered on three business capabilities:
- Alerts & Outreach
- Advisor Availability
- Appointment SchedulingÌý
Alerts & Outreach
Sprint 5 introduced several features to support course alerts and outreach workflows.
The team demonstrated how advisors receive notifications when a new course alert is created for a student. In the example, a student received a course alert after falling below a grade of C in a course. When the student later dropped the course, the alert status automatically updated and closed, ensuring advisors see current information.Ìý
Ìý
Additional Sprint 5 functionality included:
- Manual alert creation
- New alert notifications
- Alert follow-up tracking
- Course alert status updates
- Course alerts for grades below C
- Reporting on course alerts during the current term
- Student outreach assignment
- Automatic outreach status updates
The demo also showed how advisors can create outreach records when students receive multiple course alerts. Advisors can document outreach attempts, record notes and track outcomes within the outreach record. Future work is expected to automate additional portions of the outreach process, including assignment and record creation.Ìý
Ìý
Ìý
Advisor Availability
Sprint 5 added support for advisor drop-in availability. This functionality allows advisors to designate time for drop-in appointments as part of their availability management process. The feature was highlighted as completed Sprint 5 work, with additional advisor-availability development planned in later sprints.Ìý
Ìý
Ìý
Appointment Scheduling
Sprint 5 continued development of appointment scheduling and related notifications.
A key change introduced a limit on the number of future appointments a student can schedule. During the demonstration, a student who had already reached the maximum number of upcoming appointments received a message preventing additional bookings until an existing appointment was canceled.Ìý
Ìý
The team demonstrated several new notification workflows:
Ìý
Ìý
Appointment Cancellation Notifications
When a student cancels an appointment within a defined notification window, the staff member receives a notification that includes:
- Student name
- Appointment date and time
- Cancellation reason
- A link to the appointment recordÌý
Presenters noted that notification templates can support unit-specific messaging in addition to default messages.
Ìý
Ìý
Same-Day Appointment Notifications
Sprint 5 added notifications for same-day appointments. When a student schedules an appointment within 24 hours of the meeting time, staff members receive immediate notification so they can prepare for the appointment.Ìý
Ìý
Ìý
Missed Appointment Notifications
The team also demonstrated notifications sent to students when a staff member marks an appointment as a no-show.
Ìý
The notification informs the student that the appointment was missed and encourages the student to schedule a new appointment when appropriate. Sprint 5 included both generic and office-specific versions of these notifications.Ìý
Ìý
Ìý
Appointment Limits
During the discussion, presenters explained that the current requirement limits students to seven upcoming appointments at one time. The limit applies only to future appointments and does not prevent advisors from scheduling appointments on behalf of students.Ìý
Ìý
Ìý
Marketing Cloud
The Marketing Cloud team provided an update on foundational work underway for the new CRM05-connected Marketing Cloud environment.
Ìý
The new environment will connect to Education Cloud through the Marketing Cloud Connector, allowing data to move between the systems for communication and engagement activities.
Ìý
Sprint 5 work focused on establishing the underlying account structure, including:
- Parent and child business units
- User roles and permissions
- Shared-data architecture
- Business-unit configuration and planning
Project leaders described the work as foundational setup that will support future communication and marketing functionality.
Ìý
Ìý
Looking Ahead
Sprint 6 development was scheduled to begin July 15, with a Sprint 6 demo planned for Aug. 3 and testing scheduled for Aug. 4-6. Future work will continue expanding Alerts & Outreach functionality, advisor availability tools, appointment scheduling workflows and Marketing Cloud configuration. Project teams also indicated that additional automation for course alerts and outreach assignments will be demonstrated in future sprints.