Welcome to the CWDS Pivotal Tracker feedback site.
This site contains everything you need to know to use the Pivotal Tracker tool and to provide feedback to the user stories that have been developed by the CWDS teams. If this is your first visit to the site, please begin by reading the Pivotal Tracker general questions and answers presented below.
If you have used this page previously, you can access the feedback form here: Pivotal Tracker User Story Feedback Form
Pivotal Tracker is the online, publicly-accessible tool that CWDS teams currently use to plan, prioritize, and track the completion of their work. CWDS teams characterize their work in the form of “stories.” Depending on the team and its purpose, a “story” can be written either as a task for the team to complete or as a “user story,” in which case it usually follows the following template:
“As a (who needs this?),
I want (what is needed?),
so that I can (what is the value it will provide?).”
All CWDS requirements for new software development will be written as user stories with specific criteria to determine when the goals/benefits/values have been achieved.
How is Pivotal Tracker structured?
Each CWDS team has at least one Pivotal Tracker project site to present the “stories” that the team has identified as its domain to complete. Non Digital Service teams, such as Implementation, Policy, or the Project Management Office, will typically have only one Pivotal Tracker site. All Digital Service teams (such as Intake, CALS, Case Management, etc.) will have at least one “Business” site and one “Development” site.
- A “Business” site presents CWDS staff work to support a digital service’s development team. The Business site is generally the first to be generated because the first tasks of a CWDS digital service team include preparing a procurement document. Once a procurement is underway, the team writes user stories for the development team that present the requirements for the digital service’s features. When development begins, the Business site will reflect CWDS staff research to resolve development vendor issues, track progress of the development, or other tasks necessary to support successful delivery by the development vendor. Most stories in a Business site will be written as tasks to complete.
- A “Development” site presents the development vendors’ work to create, test, and deploy specific features of a digital service. The Development site becomes active once the CWDS team has created user stories for the development vendor to deliver. To understand what features of a specific Digital Service are planned for upcoming delivery, the Development site is the one to view. Most stories in a development site will be written as user stories.
Pivotal Tracker presents the team’s stories in one of four categories.
1. “Current” stories are being actively worked in the current two week work cycle, or sprint.
2. “Backlog” stories have yet to be started, but have been assigned to be worked in an upcoming sprint.
3. “Icebox” stories have not yet been assigned to an upcoming sprint--which does not mean that they won’t be assigned to an upcoming sprint, only that they haven’t been determined to be ready for work.
4. “Done” stories have been completed.
What about services that are not currently listed (e.g., Court Processing)?
Until a Digital Service has a CWDS team seated and operational, there will not be an active Pivotal Tracker site. However, as teams are seated and begin defining their work, their Pivotal Tracker sites will be created and their links will be added to this site.
We have created links that you can use to access the CWDS Pivotal Tracker site of each project team. Click the link presented below each team name to open their Pivotal Tracker project page.
We created a feedback form to collect stakeholder feedback. Navigation is designed to be simple. Click the following link to access the Feedback Form. Instructions on the form will provide you with the steps required to complete the form.
Pivotal Tracker User Story Feedback Form