Product complexity continues to increase in the life sciences industry, making it more important than ever for companies to effectively leverage traceability in their product development process. However, more than half of industry experts surveyed say they are unable to use traceability for more than compliance purposes, according to the 2016 Life Sciences Product Development Survey Report. What prevents them from making better use of this key product development component? Continue reading “Traceability’s Importance for Life Sciences Product Development”
Thanks to everyone who attended the TestTrack 2016.1 Sneak Peek webinar last week. The webinar recording is now available if you weren’t able to attend or if you would like to watch it again. The Q&A from the webinar follows.
ACQUISITION EXPANDS PORTFOLIO OF DEVELOPER AND DESIGNER PRODUCTIVITY AND COLLABORATION TOOLS
Minneapolis, MN, November 17, 2016—Perforce Software, a leader in version control and source code management, today announced its acquisition of Seapine Software, a leading provider of application lifecycle management (ALM) solutions, based in Mason, Ohio.
This acquisition expands the Perforce portfolio of developer and designer tools beyond enterprise class version management and code review, and provides customers with additional capabilities across the development pipeline. Seapine’s ALM solution accelerates development and delivery cycles through more efficient management of the product development process.
“The Seapine suite of products strongly complements the Perforce portfolio and both companies address many of the same enterprise product development needs including traceability, auditability, and predictability of the development process for high value assets,” says Janet Dryer, Perforce CEO. “The depth and experience the Seapine team has in ALM and building efficiency and quality into the development pipeline is a welcome addition to the Perforce team.”
Seapine’s ALM solutions help companies manage the process of developing high-quality complex products—often in regulated industries, such as life sciences, automotive and financial services. Seapine’s solution consists of scalable team-based tools for superior requirements management, issue tracking, software configuration management, automated software testing, load testing, and test case management. When used together, these tools provide end-to-end traceability of artifacts, resulting in increased product quality and development predictability.
“We found the technology, teams, and application development expertise at these two companies to be a great fit,” says Rick Riccetti, CEO, Seapine Software. “Our leadership team is excited about the opportunity to expand the capabilities and the reach of the Seapine portfolio with the resources and support of an organization like Perforce.”
Enterprises across the globe rely on Perforce to build and deliver complex digital products faster and with higher quality. Perforce is best known for its highly scalable version management and collaboration platform that securely manages change across all digital content – source code, art files, video files, images, libraries – while supporting the developer and build tools your teams need to be productive, such as Git, Visual Studio, Jenkins, Adobe, Maya and many others. Perforce also offers complete project lifecycle management tools to accelerate a project’s delivery cycle by linking the requirements, test plans, source code, and helpdesk in an integrated platform. Perforce is trusted by the world’s most innovative brands, including NVIDIA, Pixar, Scania, EA, Ubisoft, and VMware. The company has offices in the US, the United Kingdom, Germany, Canada and Australia, and sales partners around the globe. For more information, please visit www.perforce.com.
This is the final installment in our discussion of the barriers to Agile adoption in highly regulated product development environments. In the other four parts, we looked at the lack of documentation, the loss of traceability, the issues with enforceability and auditability, and the inflexibility of Scrum tools to integrate into the broader development process. This time, we look at the difficulty of integrating formal testing into an Agile process.
Agile is often perceived to be great for developers, but with a big gap—testing. Some organizations transitioning to Agile struggle to understand where traditional testing teams fit into the new process. Agile teams often focus on user stories and tasks, keeping testing as a separate activity outside of the sprint or iteration. In a functional safety environment, however, that separation doesn’t work. Testing and development need to remain integrated and traceable, so you know that what was developed was tested, and all defects were addressed. Continue reading “Agile in Highly Regulated Product Development, Part 5”
Thus far, this series has looked at three barriers to Agile adoption in highly regulated product development environments: the lack of documentation, the loss of traceability, and the issues with enforceability and auditability. This installment discusses the inflexibility of Scrum tools to integrate with the broader development process.
You want the development team to be as creative as possible, but what they do needs to be directed by the strategic priorities and requirements that are defined by the business. The development team must use tools that allow for traceability and compliance, but the team still needs to be flexible enough to realize the benefit of an Agile process. Dedicated Scrum tools are good for providing flexibility, but not great at meeting traceability and compliance needs. Continue reading “Agile in Highly Regulated Product Development, Part 4”
Part One of this series gave an overview of the barriers to Agile adoption in highly regulated product development environments, and examined the first barrier: the lack of documentation. Part Two discussed how to overcome the loss of traceability, which is another major barrier.
This segment explores the issues with enforceability and auditability of an Agile process, including sign-offs.
One of the key benefits of Agile is that the design is expected to evolve. As the development team gets feedback on each iteration, they gain more insight into how the product should function, and can alter the design to accommodate those changes. Iterative development is central to Agile’s ability to accelerate product development and drive quality. Continue reading “Agile in Highly Regulated Product Development, Part 3”