UTSA CRM   Updates   Sprint Schedule
UTSA CRM

Sprint Schedule

January 18, 2019


Scrum Model


SCRUM Framework

This implementation utilizes an agile methodology and the scrum framework. The framework is based on effective team collaboration on documenting requirements, development, QA and product hand-off within an iterative solution design process. Scrum consists of following the same process throughout the project lifecycle using determined time boxes, sprints.
  • Product Backlog - a list of functionality that should be done within the project
  • Sprint Planning - collaborative meeting facilitated by the ScrumMaster where the Product Owner defines the work to be completed in future sprints. Activities included in those meetings is review of acceptance criteria and approval and prioritization.
  • Sprint Backlog - list of tasks identified by the Scrum Team to be completed during the sprint.
  • Sprint Retrospective - collaborative meeting that occurs at the end of the sprint. Activities include demos, story sign-off, and identifying lessons learned for continual improvement.
  • Sprint – Iteration, or timeframe, in which development and QA of stories identified in the Sprint Planning to be completed 


UTSA Sprint Schedule

Sprint 1 
Data Model, Configure Standard Objects, Create Custom Components, interactions		 Jan 18 - Feb 1
Sprint 2
Interactions Process Flow, DeDup Rules, Opportunity & Case Process		 Feb 1 - Feb 15
Sprint 3
Axiom Integration, Campaigns, FormAssembly, Case Process		 Feb 15 - March 1
Sprint 4
SSO, Inbox, Outlook Sync, Data Migration, Marketing Cloud, Subscription Center		 March 1 - March 15
Sprint 5
Reports & Dashboards, Knowledge Transfer		 March 15 - March 29


Release Management Plan

Huron will use Agile Accelerator to track work requirements (user stories) and tasks associated with each story. The following statuses detail the user story progression in the development process:

  • New - Work item has been created (UTSA/Huron)
  • In Progress - Development in Progress (Huron)
  • Completed - Development is Complete (Huron)
  • Ready for Review - Ready for QA (Huron)
  • QA in Progress - QA Progress (Huron)
  • QA Complete - QA Testing Complete (Huron)
  • Closed - Demoed and accepted by Business (UTSA/Huron)

A work item will not be changed to "in progress" until the development approved checkbox has been checked, which means that all acceptance criteria for a user story has been reviewed and validated by the business. These stories are then added to the sprint backlog for development. 

Sprints are -week intervals that start on Monday and end on Friday. A "Sprint Retro" is scheduled the last Friday of the sprint which reviews/demos the work completed, along with lessons learned. A "Sprint Planning" session is also scheduled on the last Friday of the previous sprint, during the "Sprint Retro" meeting, which will review and prioritize work for the upcoming sprint.

At the completion of sprints, all accepted stories will be packaged to be deployed to UAT environment. During UAT, any defects will be logged, triaged, fixed (if applicable) in Dev sandbox, deployed to QA and UAT sandbox for validation. Changes will be tracked in the changelog. AFter UAT sign-off, the final package will be created for production deployment.