0% found this document useful (0 votes)
13 views

Product Lifecycle Management

Uploaded by

Rahul
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
13 views

Product Lifecycle Management

Uploaded by

Rahul
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 13

Product Lifecycle Management

CDN
20th Feb’2023
Table of Contents.
• Introduction to Product Lifecycle Management
• Benefits of Product Lifecycle Management
• Stages of Product Lifecycle Management.
• Improved CDN Product with PLM.
Product Lifecycle Management
Analysis

1
Disposal Planning
7 2 and design

• Product lifecycle management (PLM) is the process


of managing a product’s lifecycle from inception, Product
through design and manufacturing, to sales, Lifecycle
service, and eventually retirement. 6 3
Evaluation Development
and testing

5 4

Maintenance Deployment

3
Benefits of PLM
The following are five key reasons:

• Improvements to development, engineering efficiency, and


effectiveness

• Elimination of errors during the engineering release process

• Reduced time to market

• Improved project delivery

• Higher quality designs


Stage 1
Analysis

Description:
Analysis is the first stage in the product lifecycle. This stage is required
whenever a new product, release, or “key feature candidate” is being
considered.

Objective:
• Define the market trends and gauge customer interest
• Capture and document market and product requirements
• Estimate the business value of CDN Product
• Define and assess the competition for the considered product or feature.

Stage 1
Analysis

5
Stage 2
Planning and design

Description:
Planning and design is the second stage in the product lifecycle. This stage
is required define and schedule a new software release, as well as to
provide architectural guidance to developers on how to best fulfill specific
feature requirements. This applies to new or existing products.

Objective:
Planning
• Define a release structure
• Assess constraints, prioritize and select feature candidates for the release
• Identify the design considerations (deployability, scalability, etc.)
• Define/document solution that fulfills the requirements/addresses
considerations.
Stage 2
Planning and design

6
Stage 3
Development and testing

Description:
Development and testing is the third stage in the product lifecycle. This
stage is required to build solutions that fulfill the feature and timetable
requirements of a planned release, as well as test that the solutions meet (or
exceed) software quality standards for deployment.

Objective:
Development
• Complete a detailed system design using FR’s and architectural design
docs.
• Develop software that addresses the feature requirements and business
needs.
• Complete development according to the prescribed timetable / resource
plan.
Testing
Stage 4
• Test software under simulated real-world conditions, in representative
environments Development and testing
• Characterize performance under common usage scenarios/traffic loads.
• Identify and document any blocking / non-blocking issues

7
Stage 4
Deployment

Description:
Deployment is the fourth stage in the product lifecycle. This stage is
required to deploy new software releases in the field.

Objective:
The objective of this stage is to:
• Define the methods of procedure for deploying CDN software releases at
customer sites, accounting for each customer's unique needs and
environment.
• Successfully deploy CDN software releases for new installations or site
upgrades.
• Identify and relay back any installation or upgrade issues that occur so
they may be fixed via a patch or addressed in a future release. Stage 4
Deployment

8
Stage 5
Maintenance

Description:
Maintenance is the fifth stage in the product lifecycle. This stage is required
to support releases after they are deployed to the field. This includes
providing call center support to analyze issues, identify potential bugs,
remediate problems, restore services, and answer questions.

Objective:
• Provide support for customers that have deployed a software release.
• Troubleshoot issues that are reported to determine their root cause.
• Restore service and provide solutions or workarounds to reported issues.
• Document and track bugs so they can be addressed in a future release.
• Satisfy the terms of the Service Level Agreement defined in customer
contracts.
Stage 5
Maintenance

9
Stage 6
Evaluation

Description:
Evaluation is the sixth stage in the product lifecycle. This stage is required
to assess the health of each product and release relative to goals defined in
earlier stages. Health is defined based on contribution to the business,
achievement of defined business goals, and (competitive) market success. If
required, actions will also be defined to improve product/release health to
meet company goals.

Objective:
The objective of this stage is to:
• Assess the health of CDN product and release
• Identify actions that can be taken to improve product health
• Implement these actions and measure progress against defined goals
Stage 6
Evaluation

10
Stage 7
Disposal

Description:
Disposal is the seventh and last stage in the product lifecycle. This stage is
required to define the schedule and process for terminating the lifecycle of
a software release, including support and maintenance activities.

Objective:
The objective of this stage is to:
• Define a timetable and process for terminating support and maintenance
activities for a release
• Establish a standard procedure and mechanism for communicating end
of support / last time buy timetables to customer to ensure customers
are keeping their systems on a supported release / hardware version.
Stage 7
Disposal

11
Improved CDN Product with PLM.

• With PLM we can address New Product Releases in more connected


and cost-effective Manner.
• We can identify the areas of improvement at each stage and fix it with
New Releases.
• The request for New Features and Bugs on CND Product can be
gathered from Jira and then prioritize.
• It gives more structured architecture of the Product.
• Documentation can be more accurate with PLM.
Thanks
Q&A

You might also like