Tag Archive for: Jama Connect Platform

How to Overcome Development Challenges: Optimizing Review Cycles for Regulated Industries

The nature of regulated industries poses specific hurdles that demand strict procedures and careful consideration. Teams must navigate various difficulties, such as adhering to strict regulations and managing complicated relationships with stakeholders, to deliver top-notch products, software, and systems. Improving the review process is a critical approach for overcoming these challenges, promoting teamwork, enhancing decision-making, and expediting time to market. In this blog post, we delve into how streamlined review processes can help teams conquer development obstacles in regulated sectors.


RELATED: Traceable Agile™ – Speed AND Quality Are Possible for Software Factories in Safety-critical Industries


The Critical Role of Enhanced Review Cycle Processes

  • Ensuring Compliance with Regulations: In industries such as medical device & life sciences, aerospace & defense, and automotive, adherence to regulatory standards is of utmost importance. Through improved review procedures, all requirements and deliverables are thoroughly evaluated, reducing the possibility of non-compliance and associated penalties. Regular and thorough reviews also aid in the early detection and resolution of any issues during the development process
  • Fostering Efficient Collaboration: Development projects often involve the collaboration of diverse teams and external partners. Enhanced review processes establish a structured framework for effective collaboration, ensuring that all stakeholders can contribute and provide feedback efficiently. This cooperative approach leads to the creation of comprehensive and well-rounded solutions.
  • Expediting Development Timelines: Timeliness is crucial in regulated industries. Streamlined review processes can significantly reduce development timelines by swiftly identifying and addressing any issues that may arise. This minimizes the need for rework and helps teams stay on track, ultimately accelerating the time-to-market.
  • Enhancing Decision-Making: Enhanced review processes offer a holistic view of project progress and potential challenges, facilitating well-informed decision-making. By providing all relevant information to stakeholders, teams can make timely and well-founded decisions, aligning everyone towards a common goal.

“The review process is a lot quicker than it was before, it’s very efficient in Jama Connect. If we compare it to reviewing the spreadsheets and Word documents versus doing a review in Jama Connect Review Center, it’s about an 80% reduction in time, for sure.”
– Kurt Shuler, Vice President, Marketing – Arteris IP, “See How Arteris IP is Leveraging Jama Connect for Autonomous Vehicle Development”

Strategies for Enhancing Review Processes

  • Simplifying Review Processes: It is crucial to have well-defined and streamlined protocols in place for reviews to optimize the process. This includes setting specific review deadlines, using standardized templates, and clearly outlining the roles and responsibilities of all parties involved.
  • Utilizing Modern Technology: Innovative review tools like Jama Connect’s Review Center offer the ability for real-time collaboration and feedback. These tools allow for reviews to take place at different times, preventing delays and keeping the process moving forward.
  • Centralizing Documentation and Feedback: Having a centralized location for all review documents and feedback ensures that team members have access to the most up-to-date information. This promotes transparency and ensures that feedback and approvals are properly recorded and easily traceable, which is crucial for compliance audits.
  • Identifying and Removing Obstacles: Regularly evaluating review cycles to pinpoint any issues and implementing solutions such as automated notifications and reminders can help keep the review process on track. This proactive approach helps maintain progress and ensures timely completion of reviews.

“If working in Aerospace / Avionics engineering, Jama Connect is a solid option to handle requirements, elements of detailed design and Test artifacts. It also enhances cross-team collaboration through the Review Center, the Stream feature.”

– Process Engineer, Aerospace & Defense  

The Benefits of Jama Connect®’s Review Center

Jama Connect®‘s Review Center provides an iterative, collaborative approach to reviewing requirements and tests in real-time. With Jama Connect’s Review Center, teams can:

  • Enable efficient and scalable reviews and shorten review cycles by up to 50%
  • Prioritize critical decisions and align stakeholders to improve response times, minimize meetings, and eliminate communication bottlenecks
  • Facilitate compliant reviews and approvals by creating a standardized review process, gaining formal approvals, and exporting to an auditable system of record
  • Engage unlimited stakeholders: Drive participation from buyers, suppliers, and partners across organizational boundaries for centralized definitions, input, and decisions
“Jama Connect allows us to centrally collect project documentation (requirements, product risks, test cases, etc) and efficiently review, release, and reuse the contents of these documents.”
– Vice President of Engineering, Medical Device & Life Sciences

RELATED: Buyer’s Guide: Selecting a Requirements Management and Traceability Solution


Conclusion

Improving review procedures is a vital approach to overcoming challenges in regulated industries. When reviews are optimized, they not only ensure adherence to regulations, but also promote efficient teamwork, accelerate development timelines, and enhance decision-making. Jama Connect’s Review Center provides a robust solution for enhancing review processes, allowing for efficient and scalable reviews, aligning stakeholders, promoting compliant reviews, and engaging an unlimited number of participants. With Jama Connect’s Review Center capabilities, teams can streamline their review processes, resulting in the timely delivery of high-quality, compliant products that meet the stringent requirements of regulated sectors.

“We have achieved a significant ROI with Jama Connect in risk reduction and productivity gains: reuse is up 100%, rework is down 50%, requirements review cycle time is cut by 30% and audit preparation time is down 75%.”
Kurt Shuler, Vice President, Marketing – Arteris IP, “See How Arteris IP is Leveraging Jama Connect for Autonomous Vehicle Development”

Note: This article was drafted with the aid of AI. Additional content, edits for accuracy, and industry expertise by McKenzie Jonsson, and Decoteau Wilkerson.

Jama Connect® Features in Five: TestRail Integration

Learn how you can supercharge your systems development process! In this blog series, we’re pulling back the curtains to give you a look at a few of the powerful features in Jama Connect®… in about five minutes.

In this Features in Five Integration Series video, Steven Pink – Senior Solutions Architect at Jama Software® – demonstrates integrating test results from TestRail with Jama Connect®.

VIDEO TRANSCRIPT

Steven Pink: Hello and welcome to the Features in Five Integration Series. My name is Steven Pink and I’m a senior solutions architect at Jama Software. Today we’re going to be walking through a live demonstration of integrating test results from TestRail with Jama Connect.

We make it possible for you to integrate Jama Connect with preferred best-of-breed software to achieve live traceability across the end-to-end development cycle. Live requirements traceability is the ability for any engineer at any time to see the most up-to-date and complete upstream and downstream information for any requirement no matter the stage of systems development or how many siloed tools and teams it spans. This enables significant productivity and quality improvements and dramatically reduces the risk of product delays, cost overruns, defects, rework, and recalls, and ultimately results in faster time to market.

The goal of integrating with a testing tool like TestRail is to better visualize test coverage for our requirements. Jama Connect can help in identifying and calling out gaps in test coverage, while also visualizing and reporting on the test results, utilizing the filters, dashboards, and exportable reports.

Integration with TestRail starts by mirroring TestRail’s hierarchy of test suites, test sections, test cases, and test results in Jama Connect. We use sets of test cases to mirror the test suites and folders to mirror the test sections within those suites.

As we transition into Jama Connect, I want to point out how we’re relating our test results and test cases from TestRail to the requirements being authored and captured in Jama Connect. As we look at this relationship diagram, we see our software requirements and our user stories relate to the custom test cases being managed over in TestRail. This is a very common scenario for many of our customers where certain teams might be utilizing a different tool for testing, and we need to integrate those results back with the requirements managed in Jama Connect. We can author a test case directly within Jama Connect or within TestRail.


RELATED: Jama Connect® Integrations for Live Traceability™


Pink: So we’re going to start out by authoring a test case in Jama Connect. This demo suite would mirror a suite in TestRail, and this folder would mirror a section in TestRail. I’m going to author a new test case within this folder. We’ll call this example test case. Once I’ve saved this test case, we’ll trace it to the requirement that it covers within this project. I’m going to choose one of my example software requirements.

So now I’ve created a test case with a relationship to the software requirement that it covers. We’ll notice this integration URL is populated automatically and allows us to jump to the mirror of that test case that’s been created in TestRail. Once I’ve signed into TestRail, we’ll be able to see that that test case is mirrored into TestRail.

It is in that demo suite and in section A. If we want to run this test case, I’m going to go to my test runs and results and create a new test run. It’s going to be based on that demo suite, and we’re going to include all test cases, which is just one in this example. This example test case is now showing untested. And if I were to look back in Jama Connect, we’ll see for my example test case under the relationships tying back to that software requirement. As soon as we come in here and run our test execution, let’s say we update this to past or failed, this result is going to get sent back to Jama Connect automatically.


RELATED: Traceable Agile™ – Speed AND Quality Are Possible for Software Factories in Safety-critical Industries


Pink: We can also see on the test case itself, there’s an easy link back into Jama Connect. So if our test runners working in TestRail would like to see requirement coverage and traceability, they’re able to easily click the link from TestRail and go back into Jama Connect and explore that traceability and coverage. I’ll use that link right now to go back to our test case in Jama Connect. And now we’ll see because we’ve executed that test case, there’s an associated test run, and that test run is showing the result of past. We can visualize all of this through our trace views, our dashboards, and our custom export templates within Jama Connect. So this is a great reason to be syncing and integrating these results so that we can visualize through the trace view which of these requirements have test cases in place, which requirements might have gaps in testing, as well as being able to drill down and see those test results, even being able to show status of those test results and the status of the defects associated.

Thank you for watching this Features in Five session on integrating test results between Jama Connect and TestRail. If you’re an existing customer and want to learn more, please reach out to your customer success manager or consultant. If you’re not yet a client, please visit our website at jamasoftware.com to learn more about the platform and how we can help optimize your development process.


To view more Jama Connect Features in Five topics, visit:
Jama Connect Features in Five Video Series


Jama Connect® Recognized as a Top Rated Requirements Management Solution on TrustRadius!

Jama Connect® has achieved notable recognition on TrustRadius, solidifying its position as a leading platform for requirements, risk, and test management. With an intuitive user interface, robust features, and exceptional customer support, Jama Connect has been honored with a “Top Rated” distinction by TrustRadius in 2024.

Visit the full report to discover why customers love using Jama Connect for product, systems, and software development. This recognition highlights Jama Software’s unwavering commitment to providing a reliable and efficient requirements management solution that empowers teams to drive innovation and attain exceptional outcomes.


RELATED: The Essential Guide to Requirements Management and Traceability


Jama Software values the feedback from our clients who have used Jama Connect and are committed to providing them with the best support, resources, and expertise to help them succeed. As the leading provider of requirements management software, Jama Software is proud to receive recognition for our commitment to enabling multidisciplinary engineering organizations to develop products, systems, and software to maximize their success.

I’m VERY likely to recommend Jama Connect to a colleague because they’d struggle to get anything done without using it! That’s the tool we’re using for Requirements Management now, so I recommend to my colleagues that they get amongst it!”

-From a review collected and hosted on TrustRadius – Ian Webb, Systems Engineering Technical Writer – Enphase EnergyElectrical & Electronic Manufacturing

“For our company, it was imperative that we streamline all our processes and have a solution that is well controlled for audit purposes. Jama Connect has been able to satisfy these needs easily with its intuitive design which shortened the user learning curve. Furthermore, the configuration management of artifacts is built in from the start which is incredibly powerful for auditors of our products.”

-From a review collected and hosted on TrustRadius – Eric Zaremski, Lead Program Manager – FORT Robotics

From all of us at Jama Software® to all of you, thank you!

 

Jama Connect® Features in Five: Git Repository Integration

Learn how you can supercharge your systems development process! In this blog series, we’re pulling back the curtains to give you a look at a few of the powerful features in Jama Connect®… in about five minutes.

In this Features in Five Integration Series video, Atef Ghribi, Senior Solutions Architect at Jama Software® – demonstrates a Git repository integration with Jama Connect® using a repository in GitLab.

VIDEO TRANSCRIPT

Atef Ghribi: Hello and welcome to the Features in Five Integration series. My name is Atef Ghribi and I am a senior solution architect at Jama Software. Today, we’ll be looking at the Git repositories integration using an example of a repository in GitLab. We make it possible for you to integrate Jama Connect with the preferred best-of-breed software to achieve Live Traceability™ across the end-to-end development cycle. Live requirements traceability is the ability for any engineer at any time to see the most up-to-date and complete upstream and downstream information for any requirement, no matter the stage of systems development or how many siloed tools and teams it spans.

This enables significant productivity and quality improvements, dramatically reduces the risk of product delays, cost overruns, defects, rework, and recalls, and ultimately results in faster time to market. Jama Connect being the central space repository for holistic overview across the traceability chain will be able to store the source code change track published by the integration hub from the source code repository management tools such as GitHub or GitLab. This allows software developers to work in their environments without adding additional steps to ensure traceability.


RELATED: Buyer’s Guide: Selecting a Requirements Management and Traceability Solution


Ghribi: The integration hub will take care of publishing the source code, and commit information to Jama Connect as soon as they are available in the Git repository. Additionally, software developers can provide traceability information in their source code commits, which will allow Jama Connect to create the trace links to other items, making sure that source code change sets are embedded into the traceability chain. By providing this seamless integration, Jama Connect will ensure better accessibility beyond tool boundaries to source code traceability for stakeholders who are not necessarily familiar with Git repositories.

This holistic traceability enables better efficiency in conducting impact analysis and controlling the change management process as well as facilitating reporting and tracking of metrics across tools to assess and achieve compliance with less effort. Here is a simple flow between GitLab and Jama Connect. I will start by adding a simple implementation task to my Jama Connect project. This is the input for the software developer to start working on the implementation. Now this is just an example. We can here use any other item type based on the process defined and configured within Jama Connect.

Going to my implementation issues set and here I will start by creating a new task and then I will just save and close and this will create a new implementation task inside of my Jama Connect project. I will take the ID provided by Jama Connect as information that I will use later for the traceability. Now in GitLab I will make some changes to my source code and will make sure to mention the implementation task ID and my source code commit. I’m of course just using the UI of GitLab here to edit the file, but this would be the same process if I’m working on a different environment development machine and submitting the changes sets from my own local repository.

We are just keeping things simple for the time being. So going into my file and then I’m going to edit the file as a single file just here adding some changes and I will make sure to mention in the commit message the message for the change. And then I will just put the ID as I got it from Jama Connect and now I will just commit the changes and we will see what will happen inside of Jama Connect. The integration will take care of the rest and we will go back to Jama and see how the source code change commit was published and how the traceability will be defined inside of Jama Connect.


RELATED: The Benefits of Jama Connect®: Supercharge Your Systems Development and Engineering Process


Ghribi: Within a few seconds based on the integration configured, we can refresh our project inside of Jama Connect and see how the source code change set will be published to the spot in the project tree that we defined in the integration hub. We will just refresh and now we will see that we now have one item representing our change commit with the name that was provided. So if we look closer here, we’ll be able to see that we have that same message. If we look at the traceability on the right-hand side of the screen and our relationship switch it, we will be able to see that there is one upstream link to the task implementation task that we used in the comment.

So as software developers we don’t need to redundantly create any items inside of Jama Connect or create any links after we submit our traceability. If I go also to the task that is inside of Jama Connect and look at the traceability chain, and refresh, we’ll be able to see here that source code traceability that is managed. So we have bidirectional traceability already inside of Jama Connect, which will now allow us to have and embed our code or change sets traceability source code to the traceability chain of our project.

Thank you for watching this Feature in Five session on the Git repositories integration for Jama Connect. If you are an existing customer and want to learn more, please reach out to your customer success manager or consultant. If you are not yet a client, please visit our website at jamasoftware.com to learn more about the platform and how we can help optimize your development processes.


To view more Jama Connect Features in Five topics, visit:
Jama Connect Features in Five Video Series


G2® Once Again Names Jama Connect® the Overall Leader for Requirements Management Software for Spring 2024

In the competitive landscape of requirements management solutions, Jama Connect® has once again emerged as the overall leader in the Spring 2024 G2 Grid® Report for Requirements Management Software.

G2 rates products and sellers based on reviews gathered from our user community, as well as data aggregated from online sources and social networks. They apply a unique algorithm (v3.0) to this data to calculate the Satisfaction and Market Presence scores in real-time. The Grid® Report for Requirements Management | Spring 2024 is based on scores calculated using the G2 algorithm v3.0 from reviews collected through March 05, 2024

In addition to the honor of being named the leader in requirements management software, we are proud to showcase that we were awarded several additional medals for Spring 2024 in requirements management, including:

  • Enterprise Leader
  • EMEA Leader
  • Europe Leader
  • Small-Business Leader
  • Mid-Market Leader

Download the full report to see why customers love using Jama Connect for product, systems, and software development. 


Learn More About the Spring 2024 G2 Grid for the top Requirements Management Software products HERE!


Jama Software® is honored to be recognized as the leading requirements management solution. We are grateful to our customers for providing valuable feedback on their experiences with our product, services, and customer support. This recognition is a testament to the value our industry-leading software brings to our customers, particularly those who have transitioned from a document-based approach to complex product, systems, or software development.

“Jama Connect effectively resolved our requirements management issues” -From review collected and hosted on G2.com, Stephan T. — Mid-Market

Our goal is to provide our customers with the best possible experience when using our platform. Being named the overall Leader demonstrates how much our users enjoy working with Jama Connect.

“Product Design teams need a requirements management tool like Jama [Connect.] Using Jama Connect allows our software development team to have a well-organized and well-written set of requirements. It allows us to more easily maintain a baseline of features in our continuously evolving software.” -From review collected and hosted on G2.com, Verified User — Mid-Market

Read Jama Connect for Requirements Management reviews on G2

From all of us at Jama Software to all of you, thank you!

Jama Connect® Features in Five: Automated Testing

Learn how you can supercharge your systems development process! In this blog series, we’re pulling back the curtains to give you a look at a few of the powerful features in Jama Connect®… in about five minutes.

In this Features in Five Integration Series video, Steven Pink – Senior Solutions Architect at Jama Software® – demonstrates an integration of automated test results with Jama Connect® through a Python Script and our open REST API.

VIDEO TRANSCRIPT

Steven Pink: Hello and welcome to the Features in Five Integration series. My name is Steven Pink, and I’m a Senior Solutions Architect here at Jama Software. Today we’ll be walking through a live demo of integrating some existing automated test results with Jama Connect through a Python script using our open REST API.

We make it possible for you to integrate Jama Connect with your preferred best-of-breed software to achieve Live Traceability™ across the end-to-end development cycle. Live Requirements Traceability is the ability for any engineer, at any time, to see the most up-to-date and complete upstream and downstream information or any requirement, no matter the stage of systems development or how many siloed tools and teams it spans.

This enables significant productivity and quality improvements and dramatically reduces the risk of product delays, cost overruns, defects, rework, and recalls, and ultimately results in faster time to market.


RELATED: Requirements Traceability Benchmark


Pink: The goal of integrating automated test results is typically to better visualize test coverage for requirements. Jama Connect can identify and call out gaps in test coverage, as we see here, while also visualizing and reporting on the test results using filters, dashboards, and exportable reports.

Automated testing can be performed in a variety of ways, including the usage of automation servers and different frameworks. But regardless of the approach, all we need to integrate is to add requirement identifiers to our automated test results, so that they can be traced back to the requirements they cover and then make a call to the Jama Connect REST API to submit the latest results and traceability.

All right, now I want to talk about automated testing in Jama Connect. In this example project that we’re looking at, it’s a simple software development project where we’re gathering requirements, breaking those down into epics and stories, and then performing manual and automated tests.

In this example, our manual tests are being performed in Jama’s testing environment, but we have automated tests, that are actually automated test scripts, that we’re populating results into Jama with traceability, as a part of the automated test script, so that we have end-to-end traceability through our automated test results.

If I look at my manual test cases in the project hierarchy, we can see these manual tests have been created, some of them have been run, and results have been recorded. But if I switch over and look at my automated test cases, we’ll see there aren’t any yet. That’s because I haven’t run any automated test scripts.


RELATED: The Benefits of Jama Connect®: Supercharge Your Systems Development and Engineering Process


Pink: Now what I’m going to do is I’m going to execute an automated test script that will record some results for a few different tests. I’m going to run this module, and it’s going to start executing. And if we give it just another minute now.

If I go to my automated test cases, I’ll refresh this and you’ll see it’ll populate. We now have four automated test results that have been populated into Jama. We can populate these items with any kind of information from those automated test results, whether that be issues that arose during the execution or execution data. We can also keep track of whether they passed or failed, if we have a specific pass or fail parameter we can track through them.

The benefit of integrating automated testing with Jama Connect is that we can keep track of our traceability proactively as we run our automated tests. If I look at any one of these automated tests, you’ll see under the relationships, because in our test script we associated the test with a user story, that traceability has been built into this proactively. So when we execute our automated test, the results populate into Jama Connect with traceability.

Thank you for watching this Features in Five session on integrating automated test results to show requirement test coverage in Jama Connect. If you are an existing customer and want to learn more, please reach out to your customer success manager or consultant. If you’re not yet a client, please visit our website at jamasoftware.com to learn more about the platform and how we can help optimize your development process. Thanks for watching.


To view more Jama Connect Features in Five topics, visit:
Jama Connect Features in Five Video Series


In this blog, we recap our webinar, “Best Practices for Writing Requirements” – Click HERE for the full version.

Best Practices for Writing Requirements

“Needs.” “Features.” “Requirements.”

Regardless of what terminology your teams use to identify and define requirements, the purpose of good requirements is to create a shared understanding of the promise, functionality, appearance, and value for the products you develop across all stakeholders.

In this insightful session, our industry experts will guide participants through the different ways teams can write better requirements to remove ambiguity and improve development outcomes. In this webinar you will learn how to:

  • Create a simple, systematic, and standardized process that your teams can follow
  • Separate requirements from design and establish hierarchy
  • Ensure traceability of requirements during development

Below is an abbreviated transcript of our webinar.

Best Practices for Writing Requirements

Patrick Garman: Hello everyone, let me introduce myself and my co-host. I am Patrick Garman, I’m a Principal Solutions Consultant here at Jama Software, and I work with customers across multiple industries to optimize requirements management practices to help innovators succeed. Before coming to Jama Software, I had 10 years of product development experience and I’ve led teams to successful product launches in soft tech, consumer electronics, logistics, healthcare, government and public sector, and the financial services industries. And now I serve as the services lead for improving requirements quality at Jama Software. Joining me today as well is Danny.

Danny Beerens: Hi. Thank you, Patrick, for introducing me. I’m Danny Beerens, Senior Solution Consultant here at Jama Software, and I will be assisting Patrick today. I have nearly two decades of experience in system engineering, and I have successfully implemented, trained, maintained, and supported application lifecycle management application, specifically requirements management application. Throughout my career, I have worked on projects and collaborated with customers in the medical device, aerospace and defense, automotive, and semiconductor industries.


RELATED: Buyer’s Guide: Selecting a Requirements Management and Traceability Solution


Beerens: So let’s start off today. Jama Software’s purpose is to help innovators succeed, as Patrick already mentioned. And the key to successful innovation is writing high-quality requirements for your products. We want you to walk away from this session with an understanding of why requirements are important and give you a useful framework from which to build your requirements-authoring skills. Basically, we are setting the groundwork here. We’ll expose you to the challenges in product development as they relate to requirements, and we will talk about how requirements help to bridge communication challenges. We’ll also provide you with important information and tools for authoring better requirements. So helping you write better requirements is why we are here, but what does that matter, why are we really here?

What we want and what I suspect you want too is to build safe and high-quality products, and requirements are an essential element in defining, designing, and developing great products. So yes, we want you to write better requirements, but writing better requirements is a means to a better end, a high-quality safe product, and good requirements also mean getting that great product with hopefully less communication friction, reduced rework, and building a work environment that encourages collaboration, transparency, and focuses on quality.


RELATED: The Essential Guide to Requirements Management and Traceability


Beerens: So, let’s start with talking about why requirements are important. Requirements are the building blocks of product development and strong requirements lead to better products. Conversely, vague and unclear requirements cannot only lead to product issues but also to safety concerns. These quotes you see here from the US Food and Drug Administration Design Control Guidelines for Medical Device Manufacturers, and highlight the importance of quality requirement management in delivering safe products to the market. But these justifications for requirements can be applied to any industry or product. Keep in mind, that design control activities are intended to drive quality and safety into the product development process. And here, they are stating that requirements are the foundation to those safety activities.

Of course not all benefits of proper requirements management are related to safety, these also call out the impact to later product development lifecycle activities, finding that missing requirements or even ill-defined requirements can cause expensive redesign and rework, which makes sense considering the later issues are found in the product lifecycle, the more expensive the issue is to resolve, as you’ll need to circle back to previous phases to identify and address the issue at the root, and their impacts along the way. Requirements management activities are a way to avoid these issues from the start, thus reducing rework and redesign, and improving your quality. It also ensures you make the time to market. While the specific regulations and standards may vary, the same requirement management practices and principles are applicable to any industry.


CLICK HERE TO WATCH THIS WEBINAR IN ITS ENTIRETY:
Best Practices for Writing Requirements


Ready, Set, Launch: Welcoming the New Jama Software® User Community

We are excited to announce the launch of our new Jama Software® User Community! Hosted on Higher Logic’s Vanilla platform, this community will be based on their successful framework model and will serve as an improved hub for collaboration, discussion, and support. To learn more about the history of Jama Software®’s user community, which was first created in 2015, visit Empowering Customer Success: The Vital Role of Support and User Communities.

In preparation for the launch of this exciting new space, we interviewed Amanda Jennewein – Senior Manager of Customer Support at Jama Software, to find out what existing and new user community members can expect from this transition.

What were the main reasons or goals for relaunching the Jama Software Customer Community?

Amanda Jennewein: Launching the new Jama Software® User Community is a strategic initiative aimed at improving customer engagement and satisfaction, driving innovation, and strengthening the company’s brand presence in the digital space.

  • Enhanced Customer Engagement: Our goal is to strengthen customer relationships and create a supportive ecosystem by fostering a sense of belonging and collaboration. Building a vibrant online community allows customers to engage with each other, share experiences, and exchange best practices.
  • Knowledge Sharing and Support: As we recently shared, a community is valuable for users to access documentation, tutorials, and troubleshooting guides. By centralizing knowledge and expertise, Jama Software empowers customers to find solutions independently and receive support from peers and experts within the community.
  • Feedback Collection and Product Improvement: The community provides a channel for customers to provide feedback, suggest enhancements, and vote on feature requests. By soliciting input directly from users, we gain valuable insights into customer needs, preferences, and pain points, which can inform product development and roadmap prioritization.
  • Customer Success and Adoption: A thriving community contributes to customer success by facilitating collaboration, learning, and adopting Jama Software products and solutions. We aim to drive user satisfaction, retention, and advocacy by promoting engagement and self-service support options.
  • Brand Building and Thought Leadership: Hosting a vibrant community reinforces our position as a software development and requirements management leader. By curating valuable content, facilitating discussions, and showcasing customer success stories, we strengthen our brand reputation and thought leadership within the industry.

When will the new community be available for users to see?

Jennewein: The new community was officially launched on March 18, 2024. Users can now join the new community and explore its features.


RELATED: Jama Software® Discovery Center


What improvements can users anticipate from our new community?

Jennewein: The migration to Higher Logic Vanilla represents a significant upgrade for the Jama Software Customer Community, offering improved usability, performance, collaboration tools, and integration possibilities. These enhancements allow users to anticipate a more engaging and productive community experience.

  • Enhanced User Experience: Vanilla offers a modern and intuitive user interface, making it easier for community members to navigate, discover content, and engage with others. The platform’s clean design and user-friendly features create a more enjoyable and efficient user experience.
  • Improved Performance and Reliability: Vanilla’s infrastructure is designed to deliver better performance and reliability than the previous platform. Users can expect faster page loading times, smoother browsing experiences, and minimal downtime, ensuring uninterrupted access to community resources and discussions.
  • Streamlined Content Discovery: Vanilla provides robust search functionality and content categorization tools, enabling users to find relevant discussions, articles, and resources quickly. Advanced search filters and tags make locating specific topics of interest easier, facilitating knowledge sharing and collaboration within the community.
  • Federated search: Vallina connects to other tools to surface relevant content, regardless of where it lives.
  • Enhanced Customer Support Integration: Further integration of the community with customer support processes and systems to streamline issue resolution, facilitate peer-to-peer support, and provide faster access to assistance. Automation and self-service options will empower users to find solutions independently and reduce their dependency on traditional support channels.

Will users from our previous community notice any significant changes? Will they still be able to find the same information as before?

Jennewein: Overall, the structure and organization of the new customer community will prioritize usability, accessibility, and engagement, aiming to provide a valuable and enriching experience for users seeking support, knowledge sharing, and collaboration within the Jama Software community.

You can see the Vanilla Success Community here, https://success.vanillaforums.com/

  • Homepage: The homepage serves as the central hub of the community, featuring essential announcements, latest discussions, and popular topics. It provides a snapshot of community activity and directs users to relevant sections and resources.
  • Discussion Categories: Discussions are typically organized into categories or topics based on themes, product features, or user needs. Precise categorization helps users find discussions relevant to their interests and expertise, promoting participation and knowledge sharing.
  • Digital Onboarding Guide: A dedicated section for articles, guides, tutorials, and other resources.
  • Q&A: Users can ask and answer questions within a community to facilitate self-service support and develop brand advocated.
  • Ideation: Provide feature requests while collaborating with peers by voting and commenting on ideas.
  • Events and Announcements: Information about upcoming events, webinars, product updates, and community announcements may be featured prominently to keep users informed and engaged.
  • User Profiles and Recognition: User profiles allow community members to personalize their experience, showcase their expertise, and connect with peers.
  • Search Functionality: Robust search functionality lets users quickly find relevant discussions, articles, and resources. Advanced search filters and tagging systems improve the discoverability and accessibility of content.
  • Community Guidelines and Support: Clear guidelines and rules for community participation help maintain a positive and respectful environment. Support resources, FAQs, and help documentation should be readily available to assist users and address any issues they encounter.
  • Verticalized Resources: Solution spaces for Automotive, Medical Devices & Life Sciences, Robotics, and Airborne Systems will be available to customers who have purchased additional licenses. These spaces offer industry resources, downloadable materials, and specific discussion areas.
  • Additional Downloadable Resources: Customers may purchase additional licenses to access downloadable content for:
    • Data Exchange
    • Jama Validation Kit (JVK) – Test cases and coverage reports
    • Functional Safety Kit (FSK) – ISO certifications, defects, and safety manuals.
    • Jama Connect Interchange™

How will the new community be moderated and managed to ensure a positive experience for members?

Jennewein: To ensure a positive experience for members, the new community will be moderated and managed through a combination of proactive measures, clear guidelines, and responsive support.

  • Clear Community Guidelines: Clear guidelines and rules for community participation help maintain a positive and respectful environment.
  • Designated Moderators: The community will have moderators responsible for overseeing discussions, enforcing community guidelines, and addressing any issues or concerns members raise. These moderators will be experienced and knowledgeable individuals who can maintain a respectful and inclusive environment within the community.
  • Prompt Response to Concerns: Our community encourages its members to report any concerns or violations of community guidelines to the moderators. Upon receiving such reports, the moderators will promptly investigate the issue thoroughly and take appropriate action to address the concern. This may involve removing inappropriate content, issuing warnings, or taking other necessary steps to ensure that our community remains a safe and welcoming place for all.
  • Transparent Communication: Moderators will communicate openly and transparently with community members, explaining decisions and actions. Transparent communication helps build trust and confidence among members and demonstrates a commitment to fairness and accountability.
  • Educational Initiatives: Besides taking enforcement actions, moderators will also undertake educational initiatives to encourage positive behavior and cultivate a culture of respect and collaboration among community members. This may include providing guidance on best practices for constructive communication, conflict resolution, and effective participation.

RELATED: Carnegie Mellon University Software Engineering Program Teaches Modern Software Engineering Using Jama Connect®


How will we address and resolve issues or concerns raised within the customer community?

Jennewein: Support resources, FAQs, and help documentation will be available to assist users and address any issues they encounter in partnership with moderators and the Online Community manager.

What plans does the company have for any additional future growth and evolution of the customer community?

Jennewein: The company’s plans for future growth and evolution of the customer community are focused on creating a vibrant, inclusive, and value-driven ecosystem that empowers users, fosters collaboration, and drives customer success with Jama Software products.

  • Expansion of Community Features: Continuously evaluate and introduce new features and functionalities to enrich the community experience.
  • Community Advocacy and Ambassador Programs: Identify and cultivate community advocates and ambassadors passionate about Jama Software products and actively contribute to the community. Recognize and reward these advocates for their contributions and empower them to champion the community, share their experiences, and advocate for the brand.
  • Feedback-driven Iterative Improvements: Continuously solicit feedback from community members through surveys, polls, and feedback forums to identify areas for improvement and prioritize future enhancements. Use this feedback to inform iterative updates and enhancements to the community platform, ensuring that it evolves in alignment with user needs and expectations.
  • Content Expansion and Diversification: Invest in expanding and diversifying the content available within the community, tailoring content to address community members’ evolving needs and interests, covering a broad range of topics related to Jama Software products and industry trends.

Conclusion

We are always working to improve and refine our customer experience, aiming to provide excellence in every interaction. If you are a current customer and would like to learn more, please contact your customer success manager or consultant. If you are not yet a client, please visit our website at jamasoftware.com to learn more about our platform and how we can help optimize your development process.

Important: Password Change Required for returning members to access the New Community Site

With the new site launch, returning members must update their password to access the new community site. This is an important step that needs to be taken for security reasons. We appreciate your cooperation. To change your password and gain access to the new Community site, please visit: community.jamasoftware.com

 

Jama Connect® Features in Five: Jira Integration

Learn how you can supercharge your systems development process! In this blog series, we’re pulling back the curtains to give you a look at a few of the powerful features in Jama Connect®… in about five minutes.

In this Features in Five Integration Series video, Mario Maldari – Director, Solutions Architecture at Jama Software® – will demonstrate the Jama Connect® to Jira® integration.


VIDEO TRANSCRIPT

Mario Maldari: Hello and welcome to the Features in Five Integration Series. My name is Mario Maldari and I’m the Director of Solution Architecture here at Jama Software. Today, we’ll be walking through the Jama Connect to Jira integration. We make it possible for you to integrate Jama Connect with preferred best-of-breed software to achieve Live Traceability™ across the end-to-end development cycle. Live requirements traceability is the ability for any engineer at any time to see the most up-to-date and complete upstream and downstream information for any requirement, no matter the stage of systems development or how many siloed tools and teams it spans. This enables significant productivity and quality improvements, dramatically reduces the risk of product delays, cost overruns, defects, rework, and recalls, and ultimately results in faster time to market. Let’s get started.

The Jama Connect to Jira integration allows for bidirectional synchronization of data between requirements and tasks. This allows for teams such as software developers to stay in their tool of choice and enjoy the benefit of real-time updates between the two applications. Today, we’ll be covering two core use cases for the integration. We’ll be creating a defect in Jama Connect that will synchronize to Jira, and then we’ll be creating an epic in Jira that’ll synchronize over to Jama Connect. Let’s start by executing a test case at Jama Connect’s Test Center. Let’s start our test run here and we can go through and pass or fail steps accordingly. We get to an issue, we can log a defect right from the test, and we can set things like priority. Go ahead and save that defect. And we can go ahead and save and close this test.


RELATED: How to Achieve Live Traceability™ with Jira® for Software Development Teams


Maldari: Then we can open up the test record here and we can take a look at the relationships. And as expected, we will see a link to a downstream defect that we just created. Let’s take a look and open up that defect. And we can see there’s an integration URL to the corresponding defect over in Jira that was just created. And as a developer, I can see a new defect came in and I can start to work on this defect. I can also change things like priority. I can also add a comment. Any field that’s set up to participate in the integration, such as name, description, comments, priority, all of these things can be modified from Jira and that will be synchronized over into Jama Connect. And now you’ll see that there’s a Jama Connect URL here, and this will take us back to the defect that we just created in Jama Connect.

And we can see that the priority has been set below. We can see that there’s a comment that’s been added to add an attachment, and we can actually go ahead and add an attachment here, a picture of our cracked camera. And we’ll attach that to the item. So conversely, anything in Jama Connect that’s participating in the integration, any field, name, description, priority, all of these changes from the Jama Connect side will also be reflected over on the Jira side. And so if we navigate back over into the Jira defect, we’ll do that by following this URL here, we can see that our attachment came over onto the Jira defect.

Similarly, if we’re in Jira now, we’re working and we want to create an epic, we can go ahead and create an epic. Usability improvement, we can go ahead and create that. And then let’s take a look at that epic that we just created here. Similar to the defect scenario, any field that’s set up and configured in the integration will synchronize between the two applications, and that includes the name, description again, comments, and priority. Any field that’s configured will sync over. Then if I refresh this epic that I just created, you can see now that there’s a Jama Connect URL to the correspondent epic that’s just been created in Jama Connect. So I can go here into Jama Connect and I can add things like tables and further elaborate the description, and ask the development team to fill out the table for me.


RELATED: FORT Robotics Selects Jama Connect® to Replace Google Sheets for Product Development


Maldari: But more importantly, what I can do is start to establish traceability within Jama Connect now. Assuming maybe this usability improvement request came from a particular customer, I can link it to an upstream requirement, or initiative, in this case, usability improvement from the customer. And so I can start to establish traceability now, now that it’s in Jama Connect. All the work is being done in Jira on this epic, but the traceability is being established within Jama Connect. So I’m always getting the latest changes over from the Jira side participating in my traceability within Jama Connect. Let’s take a look back over to the epic in Jira, and we can see the table that I just added from Jama Connect showing up here. You can even see that there’s now an upstream link reference that gives me a reference to the traceability that I just created on the Jama Connect side.

So as you can see, the integration allows teams such as software developers to work in Jira while allowing for real-time status updates to flow over to Jama Connect and be reflected in various traceability views. This way, teams are guaranteed to have the latest status on their projects. Thank you for watching this Future in Five session on the Jira integration for Jama Connect. If you’re an existing customer and want to learn more, please reach out to your customer success manager or consultant. If you’re not yet a client, please go to our website at jamasoftware.com to learn more about the platform and how we can help optimize your development process.


To view more Jama Connect Features in Five topics, visit:
Jama Connect Features in Five Video Series


The ‘Square Root’-Process Model for System Engineering

In the rapidly evolving field of systems engineering, the traditional V-model has served as the cornerstone for development, defining system requirements and verification processes. However, the demands of modern engineering necessitate an extension of the V-Model to reduce time-to-market and elevate customer satisfaction. This article introduces the ‘square root’ model that extends the V-model that embeds continuous feedback and integration throughout the product lifecycle. By considering production, operation, support, and end-of-life sustainability from inception, the ‘square root’ model, visually represented in the accompanying diagram, ensures that engineering efforts align with practical constraints and market needs.

Leveraging Jama Connect®‘s advanced features, we will explore how this model fosters collaboration, efficiency, and strategic foresight, setting a new standard for systems engineering excellence.

Throughout this article, when ‘product’ is mentioned, understand that it can also refer to a service, software, or system.


There are aspects in engineering and feedback loops that the V-model implies to improve the engineering assets (mainly Verification and Validation focused) at the same information abstraction level; This article will describe the need to extend the traditional V-model to ensure the estimated time-to-market can be met with ease, customer satisfaction improves each product iteration and create a better tomorrow, using Jama Connect unique features to support your engineering teams to achieve these results.

Where the traditional V-model, starting at ‘Stakeholder Requirements’ and ending at ‘Acceptance Tests’ (or ‘Validation’), describes the engineering’s team involvement in the product being engineered, it is important to understand that this is only a small part in the entire lifecycle of a product. It’s the repeatable part for that product’s new releases and it’s the part that can be used to analyze the impact of changes before that change gets implemented in production.


RELATED: A Path to Model-Based Systems Engineering (MBSE) with Jama Connect®


Design Constraints

The word “constraint” has a negative connotation; Design constraints are limitations on what designers can do with a design. These limitations are usually byproducts of having deadlines, budgets, brand guidelines (and similar guidelines, see below), laws and regulations, finite resources, and limited decision power in terms of tools and processes.

Some product engineers view design constraints in a bad light because they feel like they’re being boxed in by a brick wall, while others embrace design constraints as directional guidelines that open the doors to creativity and strategic problem-solving.

On the surface, having design constraints can indeed feel like a bad thing; however, they can be extremely useful. Being limited to certain choices doesn’t necessarily mean being limited to certain outcomes. Often enough there are alternative options that are, at least, almost as good as what you originally envisioned.

Design constraints can come from various sources, in this article we’ll talk about the constraints that focus on time-to-market, customer satisfaction, and zero waste. In other words, design guidelines come from:

  • Production;
  • Operation and Support;
  • (Ecological) Sustainability; the recycling of your product’s used materials.

These design constraints facilitate engineering with the end in mind. Your team’s early decisions during product definition must include upgradability, serviceability, and for sure: disposal, and sustainability.

Please Note: As these are complex topics by themself and not part of the core business of Jama Software, this article will only emphasize the need for feedback from these product lifecycle phases into the product definition as design constraints. Design constraints might also be known and used as Non-functional Requirements (i.e., the different ‘-bilities’, like producibility, serviceability, etc.)

Production and Manufacturing

When production and manufacturing aren’t involved from the start, your engineering team might waste valuable engineering time and effort on a product that cannot be manufactured with the means your production facilities have at their disposal. This means that the product’s entire time-to-market will need to be extended to re-engineer the product to your current production capabilities; wasting precious time and putting your competitive edge at an unnecessary risk.

As an example, a Printed Circuit Board (PCB) might require that a set of components must be aligned in the same direction and at a specified distance when wave soldered to avoid short-circuits in operation. These wave soldering characteristics can be recorded and maintained in Jama Connect as Design Constraints. Source: https://www.mclpcb.com/blog/wave-soldering-issues/

The other side of this same coin; By knowing what your production facilities can and cannot do at the start of the product definition, your teams are capable of estimating when the new bleeding-/leading-edge product they are developing needs new production means.

These insights, when considered at the beginning of the product definition, will allow your teams to research, develop, and implement the required new production techniques and have them ready when the product hits the factory shop floor. This includes having purchasing ready with new suppliers, their delivery times, required stock levels, and other input required for your factory shop floor to hit the ground running producing your new product when it completes its V-cycle.

Operation and Support

The full value of a system or product is realized in its use and operation during the expected product lifespan. Your customers want to receive a product that meets their expectations, but those expectations extend beyond a product that works on day one. Customer Satisfaction, and thus Customer Lifetime Value, is heavily influenced by the ease and availability of maintenance, servicing, and upgrades that will extend the product’s lifespan. When a customer calculates Return on Investment (ROI), they are not only considering receiving a working product, but they are also factoring in;

  • Mean Time Between Failures (MTBF, a metric for failures in repairable systems);
  • Mean Time to Failure (MTTF, a failures that require system replacement);
  • Mean Time to Repair/Recovery/Respond/Resolve (MTTR, is the average time it takes to repair/recover/respond/resolve a failure in a product, service or system, usually technical or mechanical. It includes both the repair time and any testing time. The clock doesn’t stop on this metric until the system is fully functional again); and
  • Mean Time to Acknowledge (MTTA, a metric useful for tracking your team’s responsiveness and your alert system’s effectiveness).

Reliability represent a series of metrics designed to help customers understand how often incidents occur and how quickly they, in collaboration with your Operation and Support, bounces back from those incidents. Valuable indicators to determine if their investment, and any additional investment to keep it operational, is effective.

Analysis of these reliability, MBTF, MTTF, MTTR and MTTA metrics focused on means to reduce these indicators, lead to product enhancements that improve customer satisfaction for both users (better uptime, improved performance, etc.) and decision makers (value on their investment).

E.g., the accessibility of a repairable component, to improve the MBTF, can be recorded and maintained in Jama Connect as a design constraint.

Sustainability

For sustainability, it all starts with the design. The design decisions for the product contribute 80% to the carbon footprint of the solution! How to make your products and systems ‘green’ from the start, a topic most companies struggle with.

Once your teams start to include sustainability in your product’s mission, you’ll need a structured approach, as several factors will push for different considerations. The most obvious considerations are the choice of materials and the optimizing the production process (reducing carbon emissions).

However, the repairability/serviceability of the product should be considered with a more extended lifetime vision, just like upgradeability and reusing components.

Techniques like Lifecycle Analysis (LCA, shows how much influence a product has on the environment during its entire life cycle: from raw material extraction to waste processing) exist to determine the Design Constraints necessary for the sustainability of the product being developed.

The (material) considerations that come out of an LCA (e.g. switch from fossil fuels to hydrogen) can be recorded and maintained in Jama Connect as a design constraints.

Jama Connect supports the ‘square root’-model

Collaborate with stakeholders from Production, Operation & Support and Environment, Health & Safety

Recording design constraints is not unique to a (Requirements Management, or Product Definition) application like Jama Connect; The ability to collaborate with colleagues in reviews, from the respective product lifecycle phases that normally don’t have to deal with the product definition phase (and thus don’t work in Jama Connect) is unique.

This unique feature allows your teams to engineer your products with the end result in mind, by involving the stakeholders from beyond their own engineering reach, to collaborate and achieve the optimum time-to-market, best customer satisfaction and create a better tomorrow for ourselves and future generations.

These stakeholders don’t require to be Jama Connect users to be invited and collaborate in a review within Jama Connect. Involving those stakeholders into the review process allows these stakeholders to verify their design constraints are adequately and sufficiently addressed by the requirements of your product definition.


RELATED: The Benefits of Jama Connect®: Supercharge Your Systems Development and Engineering Process


First step in sustainability; reuse as much as possible

Not only does reusing and synchronizing requirements reduce your time-to-market and improve quality, but it is also a key strategy for getting your products sustainable. Jama Connect can help reducing the struggle to build on existing work when requirements, and their corresponding test cases, are spread across documents and systems, missing Live Traceability™. Your teams must manually identify and copy related content increasing the risk of rework and gaps. Additionally, teams tend to lack visibility across efforts, causing necessary changes to not propagate across reused content, potentially impacting quality and disconnected product design efforts.

Jama Connect simplifies and enhances the process of reusing requirements and verifications by allowing you to copy selected content with its container and its traced items. Synchronization ensures visibility and enables key use cases such as parallel product definitions, common content libraries (i.e. reusable component libraries) and product variants.

Further reading
  • INCOSE (International Council on Systems Engineering): INCOSE is a professional organization dedicated to promoting and advancing the field of systems engineering. Their website (www.incose.org) offers a wealth of resources, including publications, articles, and conferences, that cover various topics in systems engineering, including the V-Model.
Other sources used