Product Line Engineering (PLE) and Lean/Agile share common goals – faster delivery and lower cost with better quality. PLE organizes people in a factory that produces the products in a product line from engineering assets shared across the portfolio. Lean/Agile organizes people in cross-functional, self-managed teams and teams-of-teams, which, at scale, are called value streams. Both approaches strive to reduce the handoffs, delays, and rework that occur when organizations mis-utilize their engineers and developers. This talk discusses how PLE and Lean/Agile principles support one another.
This talk presents the new SAFe 4.0 and discusses how these, and the other additions, help large, engineering system builders realize the benefits of lean and agile practices.
A large collection of managed and linked requirements is not necessarily a good set of requirements. This session will provide you with a wealth of guidance, key success factors and introduce you to proven tool capabilities that extend beyond “the usual” – all focused on helping you reach the goal of “good quality requirements.” In addition, we’ll look at these capabilities and associated results as applied in helping PALLAS as they work to realize a state of the art nuclear reactor.
The requirements paradigm has been changing over the last few years. There is much more interaction with stakeholders throughout the lifecycle. There is an acknowledgement that we do not know all the requirements at the beginning of a project, so we need to be able to readily accommodate change. There is also a realization that requirements drive complex projects, meaning that we need to be able to trace requirements to design, development and test. The new DOORS Next Generation facilitates all
In this webinar, we will present some of the technical and personnel challenges involved in deploying a major new Application Lifecycle Management (ALM) system across a global organization.
In this Webinar we discuss and Demonstrate the key features in CLM v 6.0
This webinar will describe the role of the Systems Engineer in agile development with emphasis on the principles. A principle is a fundamental truth or proposition that serves as a foundation for a system of belief or behavior. The value realized in Scrum and Agile are practices that place humans, not processes or techniques, at the center of an organization. Remaining true to these principles results in higher quality products that meet stakeholder needs and team members that are happy.
The Boeing Company has established an enterprise wide initiative, Integrated Product Architecture (IPA), to implement model-based systems engineering (MBSE) across the company. IPA offers programs a choice of two different MBSE implementations: SysML using IBM Rhapsody and Structured Methods using Siemens Teamcenter® software for Systems Engineering. This presentation will present the rationale for creating the initiative, and why we are offering two different implementations, the challenges we face and what we need from industry.
Learn about a systems engineering process that our team at the Pacific Northwest National Laboratory developed to successfully deliver a functional systems-engineered product. The process depended upon embedding Agile development practices within a plan-driven, hierarchical project lifecycle.
In this session we will explain a relatively new reporting feature within the IBM® Rational® Jazz™ solution. The Jazz Reporting Service (JRS) can extract data in a repeatable and consistent manner without requiring a major development effort.