Learn how our super users get the most out of their teams using Rally
The best thing about our users is that they have insights into how to use Rally. Everyone has their own approach to managing their project and these insights can help everyone, not just those on their teams.
That’s why we love Rally user groups. They give our users a chance to do a deep dive into the features they use, how they use them, and why it’s important for their teams to focus on them.
In our most recent user group sessions, Rally users talked about how they use OKRs and Timelines, taking the time to explore how they applied them directly in Rally.
OKRs
OKRs - also known as objectives and key results - are a powerful way to create focus and alignment (both vertical and horizontal) among teams, according to Doug Wilson of T. Rowe Price.
To Wilson, OKRs are a way to describe where you want to go, not where you are. They’re a way to describe broadly what you hope to achieve during a sprint or project. They break OKRs down into two types: committed (i.e., they must be achieved no matter what) and aspirational (i.e., “wouldn’t it be nice if we could do this”).
Creating good OKRs means looking at what you need, why you need it, and what you hope to achieve by doing it. The objective is a statement of a broad, qualitative goal. The key result is a quantitative statement that measures the achievement of the objective.
The diagram below helps you break down what an OKR should look like, or better yet, how to put it together.
One of the ways that Wilson uses OKRs is to better manage dependencies. These are always going to exist within a project, but you can use your OKRs to limit their impact and better ensure alignment within teams.
OKRs work best when you constantly evaluate and manage them. Breaking your objectives down on at least a quarterly basis can help you create a cycle of attempting, measuring, and adapting. And, by constantly checking in, you can make sure things are heading in the right direction.
In this user group session, Wilson covers how to apply this practice directly within Rally.
Timelines
At Sabre, Elaine McNaughton and her teams use Timelines to perform high-level planning, sequence work in a way that reduces handoffs, and reduce dependencies.
As a planning tool, Timelines give McNaughton a way to visualize large volumes of work. It provides leadership with an easy way to check the status of projects. Program managers and release train engineers can see a project’s status and proactively recognize any potential scheduling risks, reducing the number of dependencies.
Timelines are also useful as a coaching tool for new teams who may not understand how the various pieces of a project fit together. By putting together timelines and giving these new teams a way to see dependencies that might exist, teams can learn how to better plan and organize future projects.
McNaughton also likes the way timelines can be used to determine an idea’s feasibility when brainstorming, helping you understand and plan the journey from idea to marketplace.
To see how McNaughton uses Rally to manage Timelines, check out her user session here.
Don’t miss out on Rally activities
You might find this summary of different engagement opportunities with the Rally team a helpful resource. Whether you need 1:1 support or have product questions, there are many different forums you can leverage such as office hours, communities, and more!
Michelle Kerby
Michelle brings more than 20 years of experience in marketing and sales leadership for Fortune 500 companies. She is passionate about solving customer challenges and creating loyal evangelists. Michelle is based in Silicon Valley.
Other resources you might be interested in
AAI: Monitoring Global Shift Operations with Jobstream Runs Views
Focuses on live operational triage, teaching operators to track real-time executions, identify "Red-Zone" failures, and drill down to resolve bottlenecks.
AAI: Triaging Incidents via the Gantt View
See how to use the Gantt Command Center to isolate failures and restore pipelines. Trace dependency paths, evaluate delays, and inspect job properties.
AAI: Tracking Trends & Runtimes with Jobstream Run Details
Learn how to analyze multi-week historical performance using Actual, Relative to SLA, and SLA Graph views. See how to spot and prove performance issues.
Rally Office Hours: August 13, 2026
This Rally Office Hours session covers upcoming product deprecations, custom view migrations, high-level reporting solutions, and workspace field updates.
AppNeta: Getting Started
Learn how AppNeta delivers end-to-end visibility into the performance of networks and applications across modern, distributed environments.
AppNeta: Support Triage Playbook
Learn the steps to triage and investigate issues with AppNeta. See how to resolve issues or gather initial information to hand off to next-level support.
Rally Office Hours: August 7, 2026
Reveals how API queries can be used for non-static values, sharing examples from templates. Looks at risk burndown charts and iteration dropdown limits.
Rally Office Hours: July 30, 2026
View this session to find out about the new query counter widget, custom list print card updates, dynamic Rally-to-Clarity mapping, and Q3 events.
What’s New in DX NetOps Topology: Summer 2026
See what’s new in DX NetOps topology. Leverage capabilities for expanded multi-vendor discovery, faster triage, custom views, and seamless data exports.