Search Help

Contact Us

About Pypelyne


Getting Started

Accessing Pypelyne

Logging in

Creating an Account

Role Of Organization

Forgotten Password

The Roadmap View

Adding an Item

Name and Description


Scope and Expenses

Strategic Alignment




Filtering Items

Ranking Items

Other Views

The Calendar View

Selecting Milestones

Viewing Project Details

The Insights View

Portfolio Insight

Pipeline Insight

Grid View

Exporting Your Roadmap

Printing Your Roadmap

Settings and Controls

Changing Account Info

Adding Users

Managing Users

Changing Organization Info

Legal and Informational

Terms of Use

Privacy Policy

Adding an Item

To add an item to the roadmap, click the "Add New Item" in the Roadmap View.

Add Item Button

This will open an window in which you can enter information about the new item.

Add Item Button

While you can enter a lot of information about an item, only the name is required. However, the more information you enter the richer and more insightful your roadmap will be.

Name and Description

In the Product Overview section, you can enter a name for the product / feature / roadmap as well as a short description.


In the Product Overview section, you can select the current status of the item from the status drop down menu. Over the lifecycle of the item, you will update the status of the item and this status information drives a number of views and insights.

Although you can use an arbitrary interpretation for each status to suits your needs, if you are able to map your products and features to the following model, the views and insights built into the application will be most useful and will make sense immediately.

Item States

Scope and Expenses

The scope of an item is a measure of the effort expended on the item -- typically development time. The units are arbitrary and can represent what's commonly used in your organization such as days, or hours, or some other metric.

You can also capture addtional expenses that the item might have incurred.

Between the explicit expeneses and the scope (which could be converted into a monetary value) you can determine the main costs of a project or feature.

Strategic Alignment

Most organizations pursue multiple strategic objectives in parallel. For instance, your organization might have three or four key priorities. Consequently, you might want to know how your roadmap aligns against these strategic goals.

You can tag each item with two levels of strategic alignment. The auto-complete feature on these fields helps eliminate duplicates and ensures consistency.

One of the key insights in the application -- the Portfolio View -- uses these alignments to show you how your roadmap aligns against key strategies.


A product, feature, or project has a number of milestones that you can track. You can chose to track as many or as few as you'd like. These milestones are then reflected in the Calendar view of your roadmap.

The milestones that can be tracked are:

While you can enter specific calendar dates for these milestones (or select one from the calendar), one of the key features of the application is it's support for "flexible business dates." Flexible business dates allow you to express dates in common formats (such as 3 Jun 2009) or in an inexact fashion, which is common in business (such as Q1 2009 or Mar 2009.) These dates are interpreted intelligently so that your roadmap insights make sense. For example, while looking at a calendar, items launching in "Q2 2009" will appear on June 30, 2009.

The application understand the following types of date structures:


You can track a number of contacts for each item. These include business, product, engineering, and QA contacts.


You can add one or measures to an item.

A measure is a way to quantify the expected and actual impact of a product or feature -- a success metric. To define a measure you will need to provide:

This is a way to track what the expected and actual benefits of a project are. A graph is automatically created when the information is provided.

Item Measures