Manage Sprints is where a project manager or release manager plans and tracks Salesforce work. A sprint is a time-boxed container of user stories, and each user story holds the metadata assets and manual tasks for one piece of work. From Manage Sprints you create sprints, assign stories to team members, and follow progress on a Kanban Board, a Gantt Chart, and a Burndown Graph. Contributors then complete their stories in Update User Story, and a release manager deploys them with Deploy User Stories.
Video
Opening Manage Sprints
Right-click a deployment arrow on the desktop and choose Manage Sprints, or open the dialog from the Options Menu. User stories require Snapshot managed package version 3.5 or later.
Select Sprint tab
The sprint list at left shows active sprints, archived sprints, or both. Select a sprint to see the sprint's user stories in the middle. The buttons at right manage sprints and stories:
- Create Sprint, Manage Sprint, Delete Sprint: Deleting a sprint also deletes all related user stories.
- Duplicate Sprint: Copies the sprint along with all related user stories.
- Deployment History: Reviews the past deployments of the selected sprint.
- Create Story, Manage Story, Delete Story: Work with the stories in the selected sprint.
- Duplicate Story: Copies the story; the related tasks and assets are not duplicated.
Sprint settings
On the Main Fields tab, give the sprint a name, planned start and finish dates, and an owner, such as the admin responsible for the deployment. Options include:
- Broadcast Sprint Changes and Broadcast Sprint Deployments: Email the sprint owner when the sprint is created, deleted, or deployed.
- Broadcast Story Changes and Broadcast Stage Changes: Email the story owner when a story is created or deleted, or when the story's Kanban stage changes.
- Allow Partial Deployments: Allow the sprint to be deployed without including all merged user stories.
- Archive Sprint: Lock the sprint and the sprint's stories as a record for compliance. Archived sprints cannot be changed but can still be deployed.
The Extra Information tab holds detailed comments, the burndown data (dates and total work in hours, calculated automatically but editable), and the work days and vacation days used for scheduling. Monday through Friday are work days by default.
Story settings
Each story has a short title, an owner, a Kanban stage, and an optional parent story that must be completed first. The Extra Information tab holds story documentation and the technical and functional specifications.
Kanban Board
Stages run across the top and team members down the side: To Do, Requested, In Progress, Deployment, and Is Done. Drag cards to move stories, or double-click a card to set the percent complete, stage, or owner. Choose small, medium, or large cards, hide empty rows or columns, and turn on color coding.
Gantt Chart
Use the Gantt Chart for longer projects. Create stories before or after existing stories, set dependencies, and edit the percent complete. The schedule recalculates when a story slips.
Burndown Graph
The Burndown Graph compares expected progress with actual progress over time. A line heading toward the upper right means the sprint is behind schedule; a line heading toward the lower left means the sprint is ahead of schedule.
Display Report and Schedule Report tabs
Select sprints to build a status report with all of the sprint and story information in a table. Right-click the table to export the report, or schedule the report to keep stakeholders informed.
Links
Snapshot Best Practices: Sprints and User Stories
Metazoa Webinar: Sprints and User Stories