Tag Archive for: webinar

Jama Deminar SeriesWith over 12.5 million active users, organizations around the globe rely on Jama Connect to help bring complex products to life. Innovative companies choose Jama Connect to improve quality, reduce rework, prove compliance, and get to market faster.

That’s why we’re excited to announce a six-part series of deminars (yes, you read that right – it’s a demonstration webinar!) where we’ll be giving you an inside look at the leading platform for requirements, risk, and test management. In this deminar series, we’ll cover key features and capabilities, seamless integrations, best practices, and more.

Below is a snapshot of when each deminar will happen, what will be covered, and how you can save your spot.

Product Essentials: A Quick Tour of Jama Connect for Modern Requirements Management

Thursday, September 10 – 8:00 a.m. PT | 17:00 CEST

Jama Connect enables consistency, collaboration, and alignment across the enterprise by providing a continuous flow of accurate requirements information. This webinar demonstration tour provides an overview of the Jama Connect platform.

In this demonstration session, you’ll learn how to:

    • Establish alignment across people, process, and technology to establish a single source of truth around digital requirements management
    • Collaborate across both internal and external teams using Review Center
    • Use traceability views to provide visibility across the entire product development cycle
    • Utilize our common integrations to extend the solution capabilities — including JIRA
    • Use Jama Connect to support testing, change management and impact analysis

Product Essentials: How to Streamline Reviews and Collaborate with Remote Teams, Customers, and Suppliers with Jama Connect.   

Thursday, September 24 – 8:00 a.m. PT | 17:00 CEST

Through structured collaboration in Jama connect, teams can source feedback from distributed teams and collect side-conversations in an actionable way to gain cross-team visibility.

In this demonstration session, you’ll learn how to:

  • Easily establish communication and document decisions across virtual teams
  • Immediately notify and prioritize critical decisions and pull in required contributors throughout the development process
  • Hold formal reviews and document those decisions in Review Center
  • Exchange requirements with remote teams, customers, and suppliers to extend the development process beyond your core team


Product Essentials: Unpacking Requirements Traceability Capabilities of Jama Connect

Thursday, October 8 – 8:00 a.m. PT | 17:00 CEST

In this session you’ll learn how Jama Connect capabilities provide requirements traceability which improves product development accuracy and/or quality and ensures the ability to provide trace reports for audits. Learn how various options are used to track relationships to/from/between requirements and understand the full impact across the project.

In this demonstration session, you’ll learn how to:

  • Create relationship guardrails to ensure traceability rules will guide users and prevent dependency chaos
  • Right click to build relationship dependencies as you perform everyday work activities
  • Use trace view to:
    • Identify relationship dependencies between data
    • Track progress and identify missing work items
    • Analyze potential impact of changes
    • Gain visibility needed for prioritizing lower level work items against higher level requirements
  • Use item widgets to:
    • View impact analysis to understand the potential impact of change
    • Initiate conversations between connected users
    • Export relationship dependencies to support compliance audits


Product Essentials: Using Jama Connect and JIRA to Manage Requirements for Software Development Teams

Thursday, October 22 – 8:00 a.m. PT | 17:00 CEST

In this session you’ll learn how Jama Connect provides the ability to link JIRA tasks and defects to requirements for full transparency, traceability, and change management throughout the software development process. Product and engineering teams can connect product planning to execution and stay in sync to ensure accuracy and quality of work.

In this demonstration session, you’ll learn how:

  • Link issues and defects from JIRA to Jama Connect
  • Support conversations across the team between the requirements and epics throughout the software development process
  • Analyze—at a dashboard level—the state of the tests, stories, and epics related to a project
  • Use the two-way integration between Jama and JIRA to allow the flow of information back and forth across the teams with synchronization, providing a single source repository and full traceability


Product Essentials: Sharing How Jama Connect Allows for Earlier Testing in the Lifecycle to Increase Quality and Efficiency.

Thursday, November 5 – 8:00 a.m. PT | 17:00 CET

Through testing in Jama connect, teams can achieve value by incorporating the results of the test strategy into the product strategy and identify potential defects earlier in the product development lifecycle, which prevents late stage changes leading to costly rework.  Learn how Jama Connect provides full manual testing capabilities tied into the product development process ensuring that you release a best-quality product that meets customer expectations.

In this demonstration session, you’ll learn how to:

  • Create a test case and configure filters to quickly access requirements that have no test coverage
  • View test cases, the tests associated, and test run results to analyze test coverage and easily view any gaps
  • Log defects from the testing interface and view automatic trace relationships
  • Export reports to support compliance activities


Product Essentials: Working with baselines in Jama Connect to Facilitate Compliance and Reuse in Product Development.

Thursday, November 19 – 8:00 a.m. PT | 17:00 CET

Learn how to view and create a baseline to capture and preserve the project at a single point in time. This supports compliance and enables reuse in product development projects.

In this demonstration session, you’ll learn how to:

  • Coordinate product releases across teams and projects
  • Easily create a baseline release and track it effectively throughout the development of the product
  • Navigate the workflow across teams to support release schedules
  • Use baselines to fulfill regulatory requirements (with respect to record keeping) by producing a clear and readable audit trail.


To view the full series, watch recordings of the deminars after they happen, or register for individual deminars, visit our Product Essentials page.


Medical device companies are on the cutting-edge of advancing health care. Along with facing relentless pressures to innovate and release quality products, they also must comply with regulations and standards to remain competitive.

On Tuesday, August 4th, we’ll be hosting a webinar specifically designed for product and engineering teams building medical devices. We’ll be covering how to move beyond the frustrations of disconnected, document-based requirement systems, streamlining your design and development and risk management processes while maintaining compliance with applicable regulations and standards.

Date:        Tuesday, August 4th, 2020
Time:        8:00 – 9:00am PST

In this webinar, we’ll examine how Jama Connect for Medical Device Development helps free your teams from document-based requirements management, streamline your processes, and spend more time on innovation. Register now to learn more about:

  • Bringing systems thinking into design control and risk management activities using Jama Connect for Medical Device Development
  • Aligning how you work with the development of the artifacts needed for compliance, the Design History File (DHF) and the Risk Management file (RMF)
  • Defining products and risk controls through the lens of tracing
  • Using Jama Connect to align your design control and risk management processes with relevant parts of governing regulations and standards ISO 13485:2016, 21 CFR 820.30, and ISO 14971:2018
Presented by:

Zeb Geary Principal Consultant, Jama Software

Zeb brings more than 10 years of experience in software consulting and business analysis to Jama’s enterprise customers and helps them deploy and optimize their use of the platform. Over the past 3.5 years, he’s worked closely with many regulated customers, especially within the Medical Device industry, to provide best practices and deployment assistance to better align Jama Connect to regulated activities pertaining to design control and verification.

Watch the recording now!



On May 20th, BeanStock Ventures brought together a panel of medical device software experts, including Jama Software VP of Customer Success, Clay Moore, to bridge the gaps between modern software development and regulatory requirements.

The topic: Agile development. The panel explored if Agile could maintain its adaptive nature and still being complaint under guidance provided by TIR45, a recognized consensus standard by the FDA. 

During the webinar, the panel de-mystifies the idea that Agile development lacks the proper controls for producing safe and effective software and that the regulation is burdensome. They cover a range of exciting topics along the way.

The panel explores key issues about Agile and TIR45, including:

  • How the Agile Manifesto is trying to encourage us to find the proper balance – not get rid of the discipline and documentation that we need, but to find a better balance between that and developing useful working products. 
  • How the development of a foundation of requirements is the single most important design control activity because requirements which form the design input establish the basis for performing tasks and validation of design.
  • How TIR45 helps address common misconceptions about applying Agile at scale with multiple teams, and the need for documentation. 

The panel also offers insights to topical Agile questions like:


How does one balance employing Agile methodology alongside predicting project timing accuracy?
“Perhaps predictability isn’t the right word. A better word might be adaptability, that we can  respond to changes in a healthy way that still meets the business needs to be predictable.”

-Kelly Weyrauch, Owner, Agile Quality Systems

Does Agile help you tame change?
“Don’t try to tame change. Embrace it as a natural thing of doing product development in today’s rapidly changing world. And Agile provides mechanisms to be in control of those changes.”

– Kelly Weyrauch, Owner, Agile Quality Systems

What’s the right level of regulatory burden?
“It is generally not the regulations that bring the burden. It’s an organization’s interpretation of them. And nearly every case when I see an organization saying they have a burdensome process, it’s because they did it to themselves. They defined their process, they defined the documentation requirements, they defined the sequencing of things and the rules behind it, in a way that’s burdensome.”

– Kelly Weyrauch, Owner, Agile Quality Systems

o much more was covered in this informative session. To see what you missed, head over and watch the on-demand webinar now.




How do you create responsive teams that deliver better products faster? This organizational shift is hard – and requires change across people, process and technology. Last week, during Jama’s webinar: The Agile, Customer-focused Organization: How to Evolve, Forrester Research guest presenter Kurt Bittner walked  through actionable steps that lead to this evolution. In this webinar, questions about enabling organizational collaboration surfaced.

Kurt Bittner answers them today.

Webinar Participant: Does technology affect the people and process dimensions? Some people in my organization say we should focus first on the cultural and process changes and then look for technologies that support them.

Kurt Bittner: All three dimensions need to change in unison. The reason for this is that the processes that people perform are affected by the technologies that they use, and therefore people work differently depending on the process and tools they use. As a simple example, smart phones have changed our culture in important ways. With technology at our fingertips, we now expect to be connected all the time. Older technologies like email are giving way to newer technologies like chat and video. As digital technologies make new things possible that were unimaginable before, people adapt to interacting in new ways that change the culture.

In the business context, widespread adoption of social media technologies has changed the way that people interact as well. Circulating lengthy and complex documents for review has declined as people expect more interactive conversations using chat-like interfaces. None of these behavioral changes would have been possible without changes to technology that lead to cultural and process changes.

WP: Our company is in the process of adopting Agile for some teams. How does what you’ve talked about related to Agile?

KB: One of the defining characteristics of Agile is the dedicated cross-functional team. There are several reasons why this is one of the most important Agile practices, but they include improving collaboration and reducing time spent waiting for resources to become available to work on a task. Reducing wait time and improving collaboration improves delivery velocity.

In the broader context I presented, organizations expand the membership of the cross-functional team (which I have referred to as an integrated product team) to include other skills, including User Experience (Ux), Customer Experience (CX), operations, security, and architecture, among others. The goal is the same, however: To eliminate waste and improve throughput by improving collaboration and reducing unproductive wait time.

Beyond that, the second major aspect of Agile is that delivering working software in small increments increases cross-role collaboration and reduces waste by improve the speed at which teams obtain feedback on the quality and suitability of their work. Doing so tends to break down organizational silos and change both the behavior of team members and the culture of the organization.

WP: My organization hasn’t had very good luck with large-scale change initiatives. Everything we hear about Agile is that it’s a huge cultural change. How should we get started, and what pitfalls should we know about so we can avoid them?

KB: We have observed that organizations who are successful in their adoption of these practices get started by changing a team at a time. They choose a product area that is experiencing pressure from customers and competitors to improve delivery speed and product quality, and they use this pressure to motivate change. They let team members “opt-in” to avoid the negative effects of coercive pressure, and they support the change with training, coaching, and hiring/acquiring resources with the new skills, where necessary. Leaders support the change by removing obstacles and impediments, and they promote and celebrate successes when they occur. When there are setbacks, leaders encourage the team to learn from the experience rather than punishing mistakes. As teams become successful, they expand the adoption by sharing what they have learned with other teams also on the journey. Peer pressure tends to drive the adoption over time, as other product leaders and potential team members see the results of the new way of working and want to achieve similar results for their own products or teams. Leaders also change the measures of success to reinforce customer-driven goals. In short, culture tends to change bottom-up, supported by leaders who encourage and support the change.

WP: How do I take this information back to leaders in my organization to get them to help with the changes we need to make?

KB: First, help them understand that there is a better way to organize for better customer results. Help them to understand that the change proceeds product-by-product, team-by-team. Help them understand how cross-functional teams break down barriers between functional roles and enable better collaboration that results in less waste and less time spent waiting. And help them to find a product where your organization can experiment and learn – one where customers are demanding better experiences, faster, and where competitors are threatening to take those customers away. Finding such a product makes the change less risky – everyone knows that the old way of working is sure to fail so they are open to working in a new way.

Learn more on how product organizations enable collaboration that results in efficient integration of customer feedback, less meetings, faster real-time reviews and decisions: