Tracker now offers three of our favorite templates for story descriptions: Bug Report, User Story, and Example Mapping. You can select from a list by clicking on the description icon when adding or editing a description. Read more...
Among its other bells, whistles, and doo-dads, Tracker provides powerful search capability to quickly find what you need. Welcome to Discovering Tracker, a new series that will spotlight various features in Tracker to help you get the most out of using it. Read more...
It takes a village to deliver a great software project. Tracker’s workflow accommodates a developer’s perspective well, but there can be many actors involved in delivering a feature. You’ll use Tracker differently and get different benefits depending on your role and competencies. Read more...
The Tracker team as a whole takes responsibility for building in quality and making sure that necessary testing activities are done along with other development tasks. But we testers bring our own special value to the party, and we’re seeking another great tester to help us as we work to deliver the best possible product to our customers. Let’s walk you through a typical day of testing on the Tracker team. Read more...
Pivotal Tracker was originally created in the days when agile teams and their products tended to be small. All these years later, those teams have grown, and larger companies have adopted agile values, principles, and practices. Managing multiple projects, often among multiple teams, brings a new set of challenges. Read more...
Tracker’s API can provide information that’s not currently available through the Tracker web application. Read on to learn how to use the API to compute cycle time. Read more...
Visibility is a wonderful thing. Making your team’s work transparent lets every stakeholder judge current status and progress at a glance. This transparency also reveals impediments—is one story blocked by another? Is something holding up progress? Are some activities turning into bottlenecks? Seeing a snapshot of a team’s current status and progress is also a conversation starter: “I have a question about this story—oh, I see that Joe, Debbie, and Mary are all working on it, I will ask them.” Read more...
Most of us prefer to spend our time developing new features for our customers. But we usually have some overhead in the form of bugs and chores that takes some of our time. Since Tracker started out life on greenfield projects, it has a default setting that bugs and chores don’t get point estimates. The idea is that bugs and chores emerge over time, and while they do take time to address, they’re an ongoing and fairly consistent cost. Read more...
Tracker’s mission in life is to give teams an up-to-date snapshot of where they are and where they are headed. When we look at our project(s) in Tracker, we know for sure what we’ve done and what’s currently in progress. Tracker uses that information to help us visualize what we’re likely to be able to do for the next few weeks. Read more...
As a feature story progresses through the Tracker workflow, a lot of testing activities are also underway. Team members are collaborating to turn examples of desired behaviors into business-facing tests that guide development. Testers are performing manual exploratory testing on stories as they are delivered. Performance or security testing may be underway at some point in the development process. Read more...
Use Tracker on-the-go!
