Sprint Demo Updates BuffET CRM05

Sprint 8 Demo Updates

Erik William Jeffries — Thu, 17 Sep 2026 17:04:15 +0000

Sprint 8 Demo Updates Erik William J… Thu, 09/17/2026 - 11:04

Sprint 8 progress across BuffET CRM05 business capabilities and epics.

Quick Summary

Sprint 8 focused on improving day-to-day student support workflows in Salesforce Education Cloud, including a unified learner profile, faster appointment logging, event management and check-in tools, student portal accessibility updates and new user provisioning processes. The sprint also advanced Marketing Cloud migration work and introduced the new Declaration Tool, which helps students navigate major and minor changes.

Project Update

Sprint 8 testing was completed Sept. 15-17. Sprint 9, the final Cloud for Good build sprint for this phase of the project, runs from Sept. 16 through Oct. 9, with a demo planned for Oct. 13, 2:00 - 3:30 pm.

Project teams are also preparing for end-to-end testing and deployment activities.

Constituent Management

The updated Academic Case Learner Profile brings key student information into a single view, including academic standing, GPA, credit hours, alerts and success team assignments.

The team also demonstrated new ��Ҵ�ý�ƽ�� branding across the advising workspace.

Interaction & Activity Management

Sprint 8 introduced a Quick Log Appointment feature for recording drop-in student meetings. The tool creates both an appointment record and an interaction summary while automatically populating business unit and functional area information. Staff can also attach documents to meeting notes for future reference.

Additional updates planned for Sprint 9 include displaying student IDs in Quick Log search results and simplifying some workflow steps.

Events and Tutoring

The team demonstrated new event management capabilities, including event creation, recurring scheduling and kiosk-based check-in. Students can check in using either an identikey or student ID, and attendance is recorded immediately for reporting.

Future work will include student event registration and additional attendance functionality.

Student Portal

Student portal updates focused on accessibility and communication. Changes included:

A more visible search bar
Updated footer branding and accessibility elements
Displaying support email addresses as text
Improved success team notifications that show assigned staff names and roles

Platform Updates

The LET development and operations team demonstrated three platform updates:

The new Declaration Tool, which guides students through major and minor changes
Just-in-time student provisioning through single sign-on
A new staff provisioning process that eliminates overnight processing delays and allows faster user access to Education Cloud.

Marketing Cloud

Marketing Cloud migration work remains on schedule.

Current progress includes:

Business Unit Creation: 67% complete
Content Migration: 70% complete
Preference Center Development: 50% complete

Work continues on data model development, preference center migration and go-live preparation activities.

Looking Ahead

Sprint 9 will be the final Cloud for Good build sprint for this project phase and will focus on completing remaining functionality before end-to-end testing and deployment preparation. Marketing Cloud work will continue on its separate timeline, and project leaders emphasized that the go-live date has not yet been finalized.

Off

Traditional

White

Sprint 7 Demo Updates

Erik William Jeffries — Mon, 14 Sep 2026 23:01:07 +0000

Sprint 7 Demo Updates Erik William J… Mon, 09/14/2026 - 17:01

Buff Experience Transformation Sprint Demo 7: Significant Progress Across Multiple Business Capabilities

Quick Summary

Sprint 7 marked a major milestone for the Buff Experience Transformation project, with significant progress made across multiple business capabilities and epics. Development work spanned appointment scheduling, interaction and activity management, advisor assignments, advisor availability, constituent management, alerts and outreach, care plans and the student portal. New functionality introduced during the sprint includes group advising sessions, student appointment check-in, peer advisor meeting notes, outreach reporting, advisor assignment notifications and enhanced student records.

Project Update

Following Sprint 7, the project will continue with Sprints 8 and 9 before transitioning into deployment, testing and other end-of-build activities for the Cloud for Good portion of Phase 1. Project teams continue to make progress across Education Cloud, data migration, integrations and supporting workstreams as implementation moves toward the next phase.

There are additional sprints planned with our own Learning Engagement Technology within OIT.

Student Experience

Sprint 7 included development of the Success Team page within the Student Experience. This functionality helps students view and access information about the advisors and support professionals who make up their success network.

The Success Team experience continues to support the project's goal of providing students with a clearer understanding of the people and resources available to help them succeed.

Appointment Scheduling

Appointment scheduling represented one of the largest areas of development during Sprint 7.

The team delivered functionality that allows advisors to:

Create group advising sessions
Manage group advising sessions
Cancel group advising sessions
Prevent overbooking of group sessions

The sprint also introduced a new student check-in experience for in-person appointments. Students can check in through a kiosk, automatically notifying advisors when they arrive for their scheduled appointments.

Together, these features help support both individual and group advising models while making scheduling efficient for students and advisors.

Interaction & Activity Management

Sprint 7 delivered several enhancements that support meeting documentation and student engagement tracking.

New functionality includes meeting notes capabilities for Peer Advisor Levels 1, 2 and 3, allowing peer advisors to document student interactions and perform advising-related activities within the system appropriate for their access level. The sprint also introduced functionality for reviewing student communications.

These features help create a more complete view of student interactions and support continuity across advising and student support services.

Alerts & Outreach

A new report called My Assigned Outreach was developed during Sprint 7. This functionality provides staff with visibility into outreach activities assigned to them and supports more effective management of student engagement efforts.

As outreach programs continue to expand, these reporting tools will help advisors and support staff track follow-up activities and maintain stronger connections with students.

Advisor Assignment

Sprint 7 included several updates designed to improve advisor assignment processes.

New functionality includes:

Advisor assignment weighting
Student notifications when success team assignments occur

These updates help support advisor workload management while ensuring students receive timely communication when they are assigned to a new academic advisor, academic coach or other support professional.

Coaching Availability

The sprint also delivered updates to staff availability through enhancements to Academic Coaching Topics. These improvements help students identify the appropriate coaching services when scheduling appointments and provide academic coaches with flexibility in managing appointment offerings.

Care Plans

Additional functionality was developed to improve care plan visibility and sharing. These updates support collaboration among student-facing teams by helping authorized stakeholders access relevant information needed to support student success.

Looking Ahead

Project leaders emphasized that Sprint 7 represents an intermediate milestone in an iterative development process. The functionality demonstrated during the sprint reflects work completed over the most recent three-week build cycle and will continue to evolve through the remaining implementation sprints.

Feedback from adoption leads, plus additional campus partners that participate in the weekly demos, remains a critical part of the process and continues to inform refinements, prioritization and future updates as the project moves toward completion.

With Sprint 7 complete, testing activities are underway while development on Sprint 8 begins. Two implementation sprints remain before the project transitions into final build activities, testing and deployment preparation.

Each sprint continues to expand the capabilities available to students, advisors and support professionals, bringing the university closer to a more connected and coordinated student success experience.

Sprint 7 marked a major milestone for the Buff Experience Transformation project, with significant progress made across multiple business capabilities and epics.

Off

Traditional

White

Sprint 6 Demo Updates

Erik William Jeffries — Tue, 04 Aug 2026 13:51:19 +0000

Sprint 6 Demo Updates Erik William J… Tue, 08/04/2026 - 07:51

Sprint 6 progress across BuffET platform business capabilities and epics

Quick Summary

Sprint 6 focused on Alerts & Outreach and the student portal within the Buff Experience Transformation (BuffET) project. The sprint introduced new outreach assignment and tracking tools for advisors and provided the first demonstration of the student portal experience for Continuing Education learners. Teams also demonstrated appointment scheduling, student tasks, portal resources, Marketing Cloud migration progress and a new approach to managing course alerts.

Project Update

Sprint 6 testing was scheduled for Aug. 4-6, followed by the Sprint 7 build beginning Aug. 5. Project leaders reported that Marketing Cloud, data migration and integration workstreams remained on schedule. All demonstrations used fictional data in a sandbox environment rather than student records.

Alerts & Outreach

Sprint 6 added new tools for creating and assigning outreach records in Salesforce Education Cloud.

Staff can assign outreach records to:

A student's primary advisor
Another advisor on the student's success team
A coach
The staff member creating the outreach record

The demonstration showed advisors viewing outreach counts from both student records and academic cases. Advisors can also receive email reminders 24 hours before a scheduled follow-up date if no action has been recorded on an outreach record.

Additional Sprint 6 work included:

Outreach counts on student records
Outreach counts on academic cases
Connections between care plans and alerts
Updates to restore extracurricular and student group information on academic cases

Student Portal

Sprint 6 included the first demonstration of the new student portal.

The portal is designed to provide students with access to appointments, tasks, resources and other support services in one location. The demonstration focused on the experience of a Continuing Education learner who does not have an assigned success team.

Sprint 6 work included:

A student portal home page
Navigation menus
��Ҵ�ý�ƽ�� branding
Search functionality
Resource pages
Student task management
New-user registration for Continuing Education learners

Sprint 6 focused on Alerts & Outreach and the student portal within the Buff Experience Transformation (BuffET) CRM05 project.

Off

Traditional

White

Sprint 5 Demo Updates

Erik William Jeffries — Mon, 13 Jul 2026 18:55:21 +0000

Sprint 5 Demo Updates Erik William J… Mon, 07/13/2026 - 12:55

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.

Sprint 5 focused on Alerts & Outreach, Advisor Availability and Appointment Scheduling in Salesforce Education Cloud.

Off

Traditional

White

Sprint 4 Demo Updates | BuffET CRM05

Erik William Jeffries — Mon, 22 Jun 2026 20:02:10 +0000

Sprint 4 Demo Updates | BuffET CRM05 Erik William J… Mon, 06/22/2026 - 14:02

Sprint 4 progress across BuffET CRM05 business capabilities and epics.

Quick Summary

Sprint 4 advanced appointment scheduling, alerts and outreach, advisor availability and interaction management within Salesforce Education Cloud. The demo highlighted new drop-in advising workflows, appointment check-in tools, virtual waitlists, course alerts and advisor availability views. Teams also demonstrated advisor specialties, appointment update notifications and automatic naming conventions for interaction summaries. All demonstrations used fictional data in a sandbox environment.

Project Update

Sprint 4 marked the project's progression toward the midpoint of the nine planned build sprints. Sprint 4 testing was scheduled for June 23-25, followed by Sprint 5 development beginning June 24. Project leaders emphasized that the work remains iterative, with functionality continuing to expand through future sprints and end-to-end testing planned later in the project timeline.

Appointment Scheduling

Sprint 4 introduced several new appointment scheduling and drop-in advising capabilities.

In-Person Appointments and Check-In

The team demonstrated a lobby management workflow that allows support staff to view scheduled appointments, check students in and update appointment status. Advisors can start and end appointments directly from the same interface, allowing appointment statuses to move from scheduled to in progress and then attended.

In-Person Drop-In Advising

Students can now be added to a drop-in advising queue through support staff or by using a self-service check-in terminal. During the demonstration, students selected a topic, provided additional details and joined a queue for advisor support. Advisors can indicate when they are available for drop-ins and accept students from the queue directly from their dashboard.

Virtual Drop-In Advising

Sprint 4 also introduced a virtual waitlist process. Students can join a virtual advising queue through the student portal and are informed of their position in line. Advisors can view incoming virtual appointments, accept appointments and send meeting details through their preferred communication method. Presenters noted that future sprints will include updated portal navigation and branding for these experiences.

Appointment Notifications

The sprint added new notifications when appointments are updated by staff. In the demonstrated scenario, an advisor changed an appointment from in-person to virtual, triggering an email notification to the student. The system supports both generic notifications and advising-office-specific templates.

Additional Sprint 4 appointment scheduling work included:

Group calendar views
In-person appointment check-in
Support-staff drop-in advising workflows
Proxy appointment scheduling for another advisor

Alerts & Outreach

Sprint 4 introduced foundational course-alert functionality within Education Cloud.

In the demonstrated workflow, instructors submit course alerts when a student's performance falls below established thresholds. Advisors can view active alerts, review supporting information and see how many active alerts a student has on their learner record. Students receive notifications using templates configured by their advising school or unit.

Sprint 4 work included:

Course alerts
New alert notifications
Alert follow-up processes

The demonstration also showed advisors reviewing course-alert information alongside advising records and appointments. Presenters noted that the instructor-facing alert-submission experience is still under development and will be demonstrated in a future sprint.

Interaction & Activity Management

Sprint 4 introduced automatic naming conventions for interaction summaries.

During the demonstration, advisors created interaction records after following up with students. The system automatically generated standardized interaction-summary names using appointment information and interaction modality, reducing the need for manual naming. Updates to appointment modality automatically updated the related interaction summary naming convention.

Advisor Availability

The sprint delivered new advisor availability management tools.

Advisors and managers can now view availability using list and calendar views built around Salesforce "shift" records, which represent the times advisors are available to accept appointments. Managers can filter availability views by office, advisor or advising group to better understand appointment coverage.

Sprint 4 also added advisor specialties. Advisors can update specialty areas that are visible to students, helping students identify staff members with relevant expertise. The demonstrated specialties included areas such as academic success, campus affairs and financial management.

Platform Updates

Sprint 4 included a system update related to student success teams.

Project teams implemented a safeguard to ensure student success team assignments can only be assigned to internal users, preventing students from being assigned advising responsibilities within the system.

Looking Ahead

Sprint 5 development was scheduled to begin June 24, with a Sprint 5 demo planned for July 13 and testing scheduled for July 14-16. Future demonstrations are expected to expand course-alert functionality, advisor workflows and student-facing experiences, including additional portal functionality and instructor-facing course-alert processes. Project teams also indicated that more robust functionality will be introduced as the project progresses beyond these foundational sprints.

Sprint 4 advanced appointment scheduling, alerts and outreach, advisor availability and interaction management within Salesforce Education Cloud.

Off

Traditional

White

Sprint 3 Demo Updates

Erik William Jeffries — Mon, 01 Jun 2026 14:45:43 +0000

Sprint 3 Demo Updates Erik William J… Mon, 06/01/2026 - 08:45

Sprint 3 progress across BuffET CRM05 business capabilities and epics.

Quick Summary

Sprint 3 focused on expanding appointment scheduling and advisor availability in Salesforce Education Cloud while introducing new privacy controls for advising notes. The Buff Experience Transformation (BuffET) team demonstrated student self-service appointment scheduling, appointment updates and cancellations, advisor availability management, appointment notifications and office-specific communications. The sprint also introduced default privacy and sharing settings for advising notes and new tools for managing advisor schedules and virtual meeting links.

Project Update

Sprint 3 marked the third of nine planned Education Cloud build sprints. Sprint 3 testing was scheduled for June 3-5, followed by Sprint 4 development from June 3-19. The project team also reported ongoing work in the Marketing Cloud, data migration and integration workstreams. All demonstrations used fictional data in a sandbox environment rather than student records.

Appointment Scheduling

Sprint 3 introduced a substantial set of appointment scheduling capabilities for both students and advisors.

New appointment scheduling functionality included:

Appointment status tracking
Student appointment scheduling from the student portal
Student appointment updates
Student appointment cancellations
Support-staff appointment scheduling
Advisor appointment views
Student views of upcoming and past appointments
Appointment confirmation, reminder and cancellation notifications

The demo showed students scheduling appointments through the portal by selecting an advisor, choosing an appointment topic and selecting an available time and engagement channel. Available channels included virtual, phone and in-person appointments when configured by the advisor.

Students can also view their appointment history, update existing appointments and cancel appointments directly from the portal. Confirmation, reminder and cancellation emails are automatically generated based on appointment activity.

Sprint 3 also introduced appointment topics that determine appointment length. Demonstrated appointment types included:

Micro appointment (10 minutes)
Standard advising check-in (25 minutes)
Extended advising session (40 minutes)

Advisor Availability

Sprint 3 delivered the first advisor availability management features within Education Cloud.

Advisors can create and manage availability using shift records, which define when students can schedule appointments. The demonstration showed advisors creating recurring availability, modifying future schedules and updating previously created availability blocks.

The sprint included:

Appointment topics
Advisor availability creation
Advisor availability updates
Advisor Zoom meeting links
Availability management for another advisor
Advisor availability cancellation

The system supports multiple availability statuses:

Tentative
Published
Confirmed

Advisors can view availability using both list and calendar-style schedule views. The schedule view provides a visual display of advisor availability and status while helping advisors identify schedule gaps and conflicts.

Project teams also confirmed that Salesforce Scheduler will integrate with Outlook calendars while still requiring advisors to define their available scheduling windows through shift records.

Interaction & Activity Management

Sprint 3 introduced default privacy and sharing controls for advising notes.

The demonstration showed advisors creating interaction summaries and advising notes while managing two separate settings:

Whether a note is visible to the student
Whether a note is visible to other advisors

The "Share With Participant" setting controls student visibility through the portal. The confidentiality setting controls internal visibility among advisors. These settings operate independently, allowing advisors to determine both student access and advisor access to advising notes.

Sprint 3 established default values for both settings while still allowing advisors to adjust privacy settings when documenting sensitive student conversations.

Student Communications

Sprint 3 added new communication tools related to appointments and advising offices.

Advisors can now maintain a personal Zoom meeting link within their advisor profile. When updated, the system automatically updates future virtual appointments unless a specific appointment has been configured with a custom meeting link.

The sprint also introduced office-specific email templates for appointment communications. Authorized users can:

Clone existing templates
Customize appointment confirmations
Customize reminders
Customize cancellation notifications
Associate templates with specific advising offices

Once assigned to an advising office, the customized template is automatically used for students scheduling appointments with advisors in that office.

Looking Ahead

Sprint 4 development was scheduled to begin June 3, with a Sprint 4 demo planned for June 22 and testing scheduled for June 23-25. Project leaders emphasized that Sprint 3 represents an early stage of appointment scheduling development and that additional scheduling functionality, refinements and configuration work remain planned for future sprints. Future work will continue building on appointment scheduling, advisor availability and student-support workflows while the broader Education Cloud, Marketing Cloud, data migration and integration workstreams continue in parallel.

Sprint 3 focused on expanding appointment scheduling and advisor availability in Salesforce Education Cloud while introducing new privacy controls for advising notes.

Off

Traditional

White

Sprint 2 Demo Updates

Erik William Jeffries — Mon, 11 May 2026 15:25:36 +0000

Sprint 2 Demo Updates Erik William J… Mon, 05/11/2026 - 09:25

Sprint 2 progress across BuffET CRM05 business capabilities and epics.

Quick Summary

Sprint 2 focused on two foundational areas of the Buff Experience Transformation (BuffET) CRM05 project: Care Plans and Advisor Assignment. The sprint introduced tools for creating and assigning care plans, managing student success teams and assigning advisors at both the individual and bulk levels. The team also demonstrated how students will view care plans, tasks and success team members through the student portal. Additional work included permissions for deleting advising notes and new notification workflows tied to care plan activity.

Project Update

Sprint 2 marked the second of nine planned Salesforce Education Cloud build sprints. Sprint 2 testing was scheduled for May 12-14, followed by Sprint 3 development beginning May 13. Project teams also continued work on Marketing Cloud, data migration and integrations alongside Education Cloud development. All demonstrations used fictional data in a sandbox environment rather than student records.

Care Plans

Sprint 2 introduced the first care plan functionality in Education Cloud.

Care plans are designed to help advisors, student success professionals and support teams create structured plans that help students achieve academic and student-success goals.

Sprint 2 functionality included:

Creating and assigning care plans
Care plan assignment notifications
Student access to care plans
Care plan completion notifications
Care plan templates for reuse across multiple students

The demonstration showed advisors creating a care plan from a published template, assigning goals and adding tasks with due dates. Advisors can customize goals, task priorities and timelines before activating the plan.

Once activated, students receive a notification and can access the care plan through the student portal. Students can review assigned goals, monitor progress and complete eligible tasks. Some tasks can be configured so that only advisors are allowed to mark them complete.

The sprint also introduced activity tracking and status history for care plans, allowing advisors to monitor plan progress and receive updates when changes occur.

Advisor Assignment

Sprint 2 added several advisor assignment capabilities designed to support student success teams and case management.

New advisor assignment functionality included:

Manual individual advisor assignment
Manual individual advisor reassignment
Manual bulk advisor assignment
Manual bulk advisor reassignment
Student success teams in the student portal
Student success team roles in the student portal

The demonstration showed an advisor administrator assigning support professionals to individual students based on academic needs and case requirements. Each assignment can include advisor roles, dates and additional contextual information related to the student's support needs.

Sprint 2 also introduced bulk assignment tools that allow administrators to assign multiple students to advisors at once. The demo scenario used a group of students requiring additional support in biology and demonstrated assigning both academic advisors and student support professionals in a single workflow.

Additional bulk reassignment functionality supports situations such as staff leave or caseload rebalancing. Administrators can reassign groups of students to another advisor without updating each student record individually. Existing assignments can remain active while temporary assignments are added for a defined period.

Student Portal

Sprint 2 expanded the student portal experience with early support for care plans and success team visibility.

Students can:

Receive care plan notifications
View assigned care plans
Review goals and open activities
Complete eligible tasks
View assigned advisors and success team members
See success team roles associated with their support network

Project leaders noted that the portal experience demonstrated during Sprint 2 was an early implementation and that significant branding, design and usability work remained planned for future sprints.

Interaction & Activity Management

Sprint 2 added new permissions related to advising notes.

The demonstration showed that only advisor administrators and designated advising managers can delete advising notes. Advisors without those permissions are prevented from deleting notes, helping preserve advising documentation and supporting governance requirements.

Looking Ahead

Sprint 3 development was scheduled to begin May 13, with a Sprint 3 demo planned for June 1 and Sprint 3 testing scheduled for June 2-4. Future work will continue expanding student portal functionality, advisor assignment workflows and care plan capabilities. Project teams also noted that automation, bulk processes and additional integrations will continue to evolve as later sprints and data-governance reviews progress.

Sprint 2 focused on two foundational areas of the Buff Experience Transformation (BuffET) CRM05 project: Care Plans and Advisor Assignment.

Off

Traditional

White

Sprint 1 Demo Updates

Erik William Jeffries — Mon, 20 Apr 2026 15:54:30 +0000

Sprint 1 Demo Updates Erik William J… Mon, 04/20/2026 - 09:54

Sprint 1 progress across BuffET CRM05 business capabilities and foundational platform

Quick Summary

The first Buff Experience Transformation (BuffET) CRM05 sprint focused on establishing the Salesforce Education Cloud foundation that future development will build upon. Sprint 0 and Sprint 1 delivered core platform configuration, the CU Student Success application, student advising case records and the first advisor-facing functionality. The demo highlighted advising notes, student detail views, task management, collaboration tools and email capabilities, providing an early look at how advisors and student support professionals will work within the new CRM05 environment.

Project Update

Sprint 0 served as a one-week setup sprint focused on establishing the technical foundation for the project. Sprint 1 completed the first development sprint and introduced the initial advisor-facing functionality. Project teams also continued work on Marketing Cloud, data migration and integration workstreams in parallel with Education Cloud development. All demonstrations used fictional data in a sandbox environment rather than student records.

Sprint 1 testing was scheduled for April 21-23, followed by Sprint 2 development beginning April 22.

Platform Updates

Much of Sprint 0 and Sprint 1 focused on foundational configuration work required before broader functionality could be developed.

Completed work included:

Enabling Salesforce Education Cloud
Configuring Education Cloud dependent features
Creating baseline profiles
Creating the CU Student Success application
Creating permission-set groups for project personas
Creating the student portal site
Creating the primary student advising case record
Enabling access to the Student Success application
Enabling Salesforce Lightning and required object access

Presenters noted that much of this work occurred behind the scenes and was necessary to support future sprint development.

Interaction & Activity Management

Sprint 1 introduced the first advising workflow functionality in CRM05.

New capabilities included:

Logging advising notes
Viewing advising notes
Sharing advising notes with students
Marking advising notes as private
Tracking interaction-summary history
Collaborating with other users
Creating tasks
Sending individual emails

During the demonstration, advisors created advising notes directly from a completed appointment record. Notes can include meeting details, next steps, confidentiality settings and business-unit information. Advisors can also update notes after creation and view a history of changes made to each interaction summary.

The system supports both public and confidential advising notes, allowing advisors to control student visibility based on the nature of the information being documented.

Collaboration

Sprint 1 also introduced Salesforce Chatter as a collaboration tool.

Advisors can mention other users directly on a record, share information and notify colleagues when additional review or action is needed. Team members can respond directly within the record, creating a centralized communication history tied to the student interaction.

Tasks

The team demonstrated the ability to create follow-up tasks tied to advising interactions and student records.

Tasks can be assigned to the advisor who created them or to another Salesforce user. Advisors can view open tasks through dedicated task views and update completion status as work is completed.

Student Communications

Sprint 1 introduced the ability to compose individual emails directly from student records.

The demonstration showed email drafts automatically populating sender and recipient information based on the advisor and student records. At the time of the demo, outbound email functionality was still being configured in the sandbox environment and was not yet active.

Project teams said future work would continue refining how emails interact with Outlook and how communication histories are presented within CRM05.

Student Detail View

Sprint 1 also introduced the first version of the student academic advising case.

The advising case serves as a central location where advisors can access student information, advising records, appointments and future student-support functionality.

During the demo, advisors were able to:

Review student details
Access advising notes
View appointments
Navigate between related student records
Create new advising interactions directly from student records

Project leaders emphasized that the student view demonstrated during Sprint 1 represented an early implementation and that additional data, functionality and design updates would be added in future sprints.

Looking Ahead

Sprint 2 development was scheduled to begin April 22, with a Sprint 2 demo planned for May 11 and Sprint 2 testing scheduled for May 12-14. Future demonstrations will continue expanding advisor workflows, student records and portal functionality while additional workstreams advance Marketing Cloud, data migration and integrations. Project teams emphasized that Sprint 1 focused primarily on foundational functionality and that more student-facing and advisor-facing capabilities will be introduced throughout the remaining build sprints.

The first Buff Experience Transformation (BuffET) CRM05 sprint focused on establishing the Salesforce Education Cloud foundation that future development will build upon.

Off

Traditional

White