Application Lifecycle Management

Application Lifecycle Management

Lifecycle the word means “Series of stages through which something passes during its lifetime.”

Application lifecycle is similar to giving birth to a young one as per the God’s management.

Creating an application is not a big task, but adding the word Management in that Application 
Lifecycle is adding a process of distributing with or governing things or people. 
When Process comes in a picture, we bound to work according to that, which give the 
picture of Application Lifecycle Management.

Accumulation process is not that you are bound to move in that particular line only, but it 
means you are moving in the correct direction which will give success and 99.9% 
assurance that the Project on which you have implemented is having a correct planning, 
great controlling, and using the resources in an organized behavior.

Application Lifecycle Management is controlling of a software application from planning 
phase till it goes LIVE. But in the current era, customers are more demanding, 
technology is expanding so after the software is in a Live state, still, 
continuous improvement and maintenance are going on them, 
so application management lifecycle(ALM) has no retirement age.

Different phases of ALM

1.       Requirement Management

2.       Development and Quality Management

3.       Defect Management

4.       Configuration Management

5.       Reports

6.       Timesheet Management

7.       Build Management

8.       Release Management

9.       Variant Management

Each Phase has its own ownership according to the roles assigned to them.

Phases	Ownership	Open Source Tool
Requirement Management	Stakeholders, Product Manager	Jira Software
Development and Quality Management	Technical Team which include Developers, UI Developers, Testing Team	Jira Software
Defect Management	Testing Team	Jira Software
Configuration Management	Engineering Manager, Technical Architect	Chef, Puppet
Reports	Project Manager	Jira Software
Timesheet Management	Project Manager	Jira Software
Build Management	Release Team	Jenkins
Release Management	Release Team	Jenkins
Variant Management	Engineering manager, Technical Architect	Jira Software

Requirement Management

Requirement document is a high-Level document comprises of all proposed features which
 include the pathway (flow diagram), mock-up, list of all elements, their behavior etc.

Requirement Management is a process of getting all information from the marketing team, 
copywriters and graphic designer which incorporated as per the application and getting signed 
off by the stakeholders and product team. To get all the things to flow in the correct direction 
and maintain the same in the continuous integration process.

Documentation of all the requirements which includes analyzing the requirement along 
with its risk and mitigation plan to be well communicated to the stakeholders of the product 
is called Requirement Management

Development and Quality Management

The process of code review, writing acceptance criteria, reviewing test cases, creating 
test plan is known as Development and Quality Management.

Developer start working on any of the functionality, simultaneously QA folk write the 
acceptance criteria and create the test plan. Both the task go hands-on hand. 
Once the coding is finished, a code is reviewed and assign the task to QA for testing. 
QA test the functionality as per the Acceptance Criteria and Test Plan.

Defect Management

When the product is development state, all the bugs found by a QA or Product team should 
be logged in bug tracking tool (Jira, Mantis). All critical and high priority bugs should be fixed 
in that phase only. But as per the availability and time frame, Minor and trivial bugs are moved
in backlog which can become as a planned bug in next phase/sprint.

When a product is Live and the bug comes from the production server, Root Cause Analysis 
should be done for that bug. So that moving forward the team would not miss that cases. 
And QA also adds that cases in the test cases.

Bug life cycle

Configuration Management

The process of maintaining, tracking, controlling all the cross-functional aspect and interface -
 jumper settings which support the software and hardware configuration required for the application. 
Due to this process engineering manager and infra team control the configuration of all 
hardware and software support.

Reports

For each and every entity/management process has the result, which can we viewed as a report

Timesheet Management

Tracking and reporting for the employee amount of work spent on the project. It generally helpful 
for those working on multiple projects at the same time.

It also helpful for tracking the leaves like sick, vacations and overhead hour’s employee 
devote in the office. This is according to the Labor Laws and Company rules

Build Management

The process of merging the code of all function together to get the software application in workable 
mode. The build process can be done automated as well as manually also.

The main motive of build management to have control over all the code and have version controller. 
Due to this version controller fixing of an issue is done in more quick and reliable.

Release Management

Variant Management

In a competitive era, variant management plays a vital role. Each product maintains different 
variant to get more customer attraction. Adding different variant in the application give benefits 
along with risk is also there, but mitigation plan is also included while doing Variant Management.

Test link

Open source tool which can be integrated with Jira and Jenkins