calculated-fields

Calculated Fields

With Calculated Fields, assign values to each item item in your backlog to determine the relative priority, making it easier to decide what to focus on next with data driven decisions.

Calculated fields allows integer and picklist fields in an item to be calculated for addition, multiplication and the average. You can use relationship counts (number of upstream and/or downstream relationships) as a factor in a calculation to evaluate the “social weight,” the number of connected users and comments to provide a weight based on people impacted.

These calculations will allow for negative numbers and up to four decimal places.

Prioritize Items in Your Backlog

When planning work, product teams need to measure the impact that the development of a specific feature will have on your customer experience versus the impact it will have on your development team’s output. If your team works within the Agile SAFe Framework, and you’re familiar with WSJF (“Weighted Shortest Job First”), which helps teams plan work in a continuous flow, then these calculated fields can help with this prioritization.

You can set up calculated fields to determine:

Level of Effort + Customer Impact = Priority
An item with critical severity and a low level of effort would receive the highest priority value in the backlog.

1. Assign Level of Effort
First, assign the level of development team effort to the proposed feature at the item level. Here we’ve assigned a numeric value to three levels of effort: Low, Medium, and High.

Assign the Level of Effort
Assign the Level of Effort

2. Assign Customer Impact
Next assign a level of customer impact — however you define this in your organization — and a value. Here we’ve given values from “not important” to “critical,” with a wide range between “high” and “critical” in order to ensure that true must-have features are given top priority.

Assign customer impact
Assign customer impact

In this model, a critical item with low level of effort receives a score of 15, while an item with high level of effort and low priority receives a score of 2.

central-repository

Central Repository

Within Jama, data is kept, organized and secure in one or many projects. Jama is the single database of your product IP, and it’s always accessible. Permissions can be set at multiple levels, so that data can be shared across projects or kept private and only visible to a single team.

Jama is both an archive of completed work and the system of action for work in progress. Jama is a single repository for all systems documentation and specifications—alongside the work, change, decision tracking, collaboration, communication and coordination across teams.

Sample Project List
Sample Project List
coverage

Coverage

Coverage in Jama helps ensure quality. Specifically, the Coverage Explorer visually represents the coverage of your product, helping you ensure that users are aligned, quality maintained, compliance regulations met and the impact of change is understood. Users can view related items and and understand the status of those items. For example, users can verify that their requirements have downstream test cases and see what percentage of those test cases have passed.

Test Coverage

The Coverage Explorer highlights gaps in test coverage and Suspect Links flag potentially impacted test cases based on upstream changes. Including the QA team in early requirements definition means that test planners can adapt quickly to changes in scope and scenarios that need to be tested. Every test case has a comment and activity stream accessible by all users. This allows testers and contributors to capture decisions, answer questions and resolve issues transparently and responsively.

Jama Coverage Explorer
Jama Coverage Explorer
critical-baseline

Critical Baselines

Baseline an entire project, or any subset of a project, to record its current state.

A baseline is a “snapshot” of Items within a project at a certain point in time. When creating a baseline, Jama stores a baseline label on the current version of each item that you have included. Create a baseline at each significant event or milestone – for example when the requirements are complete, after change requests, or after a release.

The items’ versions within a baseline cannot be changed once created, but users can edit the baseline name and description, view the contained Items, compare their versions and approve a baseline with a digital signature.

decision-tracking

Decision Tracking

Thousands of decisions are made during the product development process. Your team makes decisions every day, so they need to be empowered and have access to the information needed to make high quality decisions. In Jama, you can formally request decisions within the context of items and projects as well as mark decisions made.

Keep track of what decisions are open and need your attention from the home page.
Keep track of what decisions are open and need your attention from the home page.
View the open decisions, issues and questions that require your response right from the homepage.
Activity View from Home Page

From login, you can easily view the decisions, questions and issues awaiting your response. Jama allows you to seek and make those decisions transparently – giving clarity to everyone involved in the product delivery process.

impact-analysis

Impact Analysis

On complex projects with thousands of artifacts, to manually determine what and who is affected by a change is time consuming and error-prone. With Impact Analysis, Jama automatically highlights the items and people that are impacted when a change occurs.

Impact Analysis in Jama helps you manage change. You can review a change’s impact before the change is made.

Jama displays the project items that may be affected
Jama displays the project items that may be affected

Understanding the impact enables teams to quickly and accurately respond to change requests. The team can be responsive while maintaining control over scope and the customer expectations. Lastly, impact analysis is essential on projects where quality and safety is an issue such as in healthcare, automotive and aerospace projects. In these situations, it’s critical to understand the specific set of requirements and features that need to be retested after a change is implemented.

As requirements management expert Karl Wiegers writes, “Impact analysis is a key aspect of responsible requirements management. It provides accurate understanding of the implications of a proposed change, which helps the team make informed business decisions about which proposals to approve.”

real-time-collaboration

Real-Time Collaboration

Jama facilitates early-and-often collaboration and engagement. Real-time collaboration in Jama shortens milestone phases, reduces development cycles, improves efficiency, and helps your teams identify risks and finds opportunities.

Collaboration in Jama happens across the product. Items are linked to the related conversation and associated questions, reasoning, and decisions, which can be reviewed throughout the and archived after.

Teams lose productivity when they have to focus on tracking down the answer to a question in order to make a critical decision. With Jama, these potential blockers can easily be escalated so the right people see it quickly via email or mobile device and can respond directly to the team, allowing the team to get back to work. Comments can be marked as decision requests and these decision makers are contacted (@mention) in real-time to have decisions made and marked.

The Jama Stream
Screen Shot 2015-12-30 at 3.49.55 PM

The stream gives members of the product development team a way to engage key stakeholders and keep them in sync. You can quickly associate questions, decisions, issues to individual requirements, projects, or organizations. You can even ask questions, make comments and get notifications using mobile web or email.

Without needing to know how to navigate all of Jama, stakeholders can quickly get a pulse on a project. Use the Stream to bring new users into Jama – project team members can pull key stakeholders seamlessly into conversations by name or email address and record conversations as they occur.

Connected Users

See the users that are connected to an item in Jama
See the users that are connected to an item in Jama

With Connected Users, you can quickly see who originally authored, made an edit, or even just commented or were @mentioned on an item. You’re able to not just see who is directly connected, but also those who are indirectly connected through related items, allowing you to illuminate changes to those who may be impacted.

relationship-rules

Relationship Rules

Track relationships across projects to see the impact and reach of information across the organization.

Relationship Rules is a visual diagram in Jama to define and standardize data so users can see how their data fits into the entire product delivery process. This feature prevents users from connecting incorrect data and ensures full traceability.

Create a set of required and optional relationship rules.
Create a set of required and optional relationship rules

Relationship rules maintain the project structure by preventing problems with relationships. The rules help users know when relationships are required and in which directions. In addition, the Relationship Status Indicator on each item allows users to easily see when their relationships do not match the Relationship Rules. Jama allows administrators to create rule sets at the organizational level, which can be applied to one or more projects.

reporting

Reporting

Build custom reports to meet analysis needs for industry compliance. Jama includes system reports for System Requirements Specification documents and other related requirements management tasks. With Jama, custom reports allow you to see your data, your way. Industry compliance or regulatory rules might require a report displaying traceability specific to your company’s process or a quick way to analyze one or more projects.

When documentation is required, you can view the report in Jama, email and publish it as a document or spreadsheet. Reports viewed from within Jama always contain the latest information, and can be viewed by any user.

reuse

Reuse

Create Catalogs of Reusable Requirements

Your next product gets to market faster when you can reuse your requirements. With a centrally managed catalog of reusable product details, reuse keeps requirements synchronized and in context across your organization. Teams have control over what synchronization they need and at any point can branch from the catalog. There are three ways that you can reuse requirements:

Sync a source item to another project
Sync a source item to another project
Sync a source item to another project and maintain relationships
Sync a source item to another project and maintain relationships
Sync a source item to another project, duplicate and sync relationships
Sync a source item to another project, duplicate and sync relationships

Branch Product Lines or Versions

Jama Reuse allows teams to create branches of a product in order to create a variant or new version. Within these branches teams can allocate different sets of permissions, continue work on the branch, and keep items in-sync as needed.

Compare and Sync

Reuse uses Jama Version Compare to show when information is out of sync at the high level and within individual items. Users can quickly see the items side-by-side with highlighted out-of-sync information. Within that view, you can leave items as they are or push the changes from either item to the other to get them back in sync.

Compare all synched items with Version Compare
Compare all synched items with Version Compare

With Jama Reuse, your team can maintain structure (hierarchy), all custom attributes and traceability.

Maintain existing hierarchy, traceability and all custom attributes
Maintain existing hierarchy, traceability and all custom attributes
review-and-approval

Reviews and Approvals

Review Center is a module within Jama to share product requirements among multiple teams for review and confirmation, confirm acceptance criteria, negotiate engineering responses, iterate on specifications and confirm mutually agreed-upon requirements. Review Center simplifies the review and approval process by capturing feedback from stakeholders, including voting for priority and electronic signatures for formal approval.

Initiate a Review

Select the requirements that require feedback or approval, set a deadline and invite the people you want to participate in the review. When applicable, give authority to team members you’d like to approve and electronically sign-off on the requirements.

Start a Review in Review Center
Start a Review in Review Center

Gather Feedback

Reviewers and approvers receive an email invitation, log into the review and provide feedback. Reviewers can see the conversation that’s taking place and respond with questions, propose changes and raise issues about requirements, as well as leave general comments. In addition to feedback, approvers will mark items as ‘approved’ or flag ones that ‘need more work.’

Approvers mark each requirement ‘approved’ or ‘needs more work’
Approvers mark each requirement ‘approved’ or ‘needs more work’
Reviewers and approvers vote for priority
Reviewers and approvers vote for priority

Monitor Progress

All participants can track the overall progress of the review and view the team’s statistics to help determine which requirements have the most feedback, questions and issues to address.

View real-time progress and feedback on items within a review
View real-time progress and feedback on items within a review

Incorporate Feedback

Moderators can make changes to individual requirements. Changes to requirements are automatically updated in Jama within the version history. The review participants will be notified once you publish a new revision. Multiple revisions may be needed to gain final approval and The Review Center keeps track of it all.

Publish a new revision to update the review
Publish a new revision to update the review

Complete Review

When your team approves all the requirements, you can update the status in Jama and notify your team that the requirements are ready for development. Now, everything is captured in one place. Everyone is in sync. And, your requirements approval process is collaborative, fast and agile.

Approvals

Electronic signatures can be added to content within Jama as a baseline, used for compliance with FDA 21 CFR Part 11. This content can be created via a baseline or review of a document.

Once an Approver completes the review of a document they will be required to enter in their Jama password. The system will then capture the date/time for auditing and ties the signature to the individual user along with a document.

Attach your electronic signature
Attach your electronic signature
test-management

Test Management

Jama Test Management enables quality assurance (QA) teams to easily create and organize test plans, test cases, dashboards and reports to manage testing in real-time. Testers can view and run their test cases, and instantly log connected defects when tests fail.

When your team engages in real-time conversations about the impact and prioritization of defects they can quickly make adjustments to ensure timely delivery without sacrificing quality. With Test Management, your QA teams execute test plans that directly associate with requirements and features.

Create a test plan and organize it into groups
Create a test plan and organize it into groups
Execute, open or assign a test
Execute, open or assign a test
version-comparison

Version Comparison

With Jama Version Comparison, you can compare two versions of a requirement side-by-side and highlight what has changed. On projects with thousands of requirements, the team is able to quickly find and work on a specific subset of items. The quicker the team finds information and answers, the less likely they are to make assumptions or guesses.

Compare Versions of an Item
Compare Versions of an Item

It can be difficult to use Word or Excel to manage requirements as the entire file needs to be versioned and redistributed or re-posted each time a change is made. It can add to overhead when each team member needs to find a specific section within a lengthy document. This is compounded when changes are made and the team only needs to know what was updated. With Version Comparison, a user can see where a change occurred without pouring through a new document.

workflow-mapping

Workflow Mapping

A workflow is a set of transitions from one status to another over the course of an item’s lifespan. A workflow in Jama is typically used to reflect a business process – and they’re highly configurable and flexible.

Jama can adapt to all sorts of business types, from requirements management to defect tracking to project task management, which means that workflow mapping can be set up in a number of different ways and on more than just the status of an item.

Manage your team’s workflow process in Jama
Manage your team’s workflow process in Jama