Change is constant. That saying couldn’t be truer when applied to software development. And with all that change comes extensive product complexity. How do you manage it all? As software developers ourselves, we can certainly empathize with the challenge.
On April 3, 2012 Stephen Van Lare, VP of PLM Product Development, hosted a webcast to share how Oracle uses Agile to develop Agile – a PLM solution for managing a PLM solution! Stephen passionately shared his unique insight based on 10 years of using Agile PLM to manage the development process, as well as customer use cases. He shared our time-proven view of the software’s relationship to the product record, while pointing out that PLM is not source control. He began with the challenges of software development, which boiled down to the deduction that “despite many great tools in the software development industry, it takes a lot more than good source control, more than good bug tracking, to get to an on-time, on-budget and quality release in your marketplace. It requires defining the right things you want to do, managing the scope, managing your schedule, and, most importantly, managing the change to all those things over the lifecycle of the process. And this is the definition of PLM.”
Stephen then defined the relationship of PLM to the software development process by detailing the two main use cases – Product Lifecycle and Mechatronics – which can be used simultaneously and in fact are already used in most industries today. The Product Lifecycle use case is used to manage artifacts and change throughout product development, while the Mechatronics use case involves the software, hardware and electrical design in the BOM. In essence, PLM is just as relevant to software as the rest of the BOM when trying to maximize profits during any phase of the lifecycle.
Please take the opportunity to watch Stephen Van Lare as he details how and why based on his own experience developing Agile with Agile, as well as a lively Q&A session, in the Software PLM Webcast Replay.
