SDLC Stages Devops

Download as pdf or txt
Download as pdf or txt
You are on page 1of 3

SDLC Stages in Devops-

Devops landscape involves multiple stages based on SDLC, enabling Agile in a proper way.

1. Planning

Product owners collect requirements from customer and create user


stories. Eg. JIRA is used generally to cover all user stories and track
progress.

2. Design

POs/Scrum master/Architect/Technical team together to compile design


of the product based on user stories.

3. Development

Developers comes into picture who starts working into development as


per the assigned task. Priority will be set by Scrum master who acts as a
coach.
Code will be checked into Gerrit/GitHub/SVN/TFS repository.

4. Build

Devops uses Jenkins, TeamCity or Bamboo tool for running build

(MS Build, maven etc.) stage on each commit.


5.
6. Test

Devops run different types of test and code coverage. Test can be written
in BDD approach [Given, When & Then] . eg. Writing in python/Java unit
test cases etc..
s
7. Feedback/Demo

Dev team collects feedback from the build reports, test and code coverage
etc.. If all good then moves for the promotion else goes back to code.

8. Delivery

Devops delivers artifacts to respective Artifactory depending on the test


stage results. If passed, we can ensure smooth delivery of our product.
All above phases in devops landscape ensures smooth and precise delivery of our product
Artifacts. In turn increasing accuracy of the team with productivity. However, this devops
differ from organisation to or organisation but above stated model is quite generic.

More the time you save, more you utilize it in research of innovation to bring Success.

PATIENCE- Road-map to Success in Devops [Beginner Guide]

Patience is the key in the road-map of Devops for achieving acme of success.

Devops idealize various technical methods to come together as a unit. And align
organisations business values into final asset.In a nutshell, an efficient way for continuous
delivery.

Devops is nothing but combination of development and operations.

Usually known as CI/CD, which is continuous integration of source code with latest changes.
This allows us to capture any issue at early stage of the Devops landscape.

Two major Mantra’s [practices] here are –


1. Automate as much as you can, to get quick turnaround and high precision in error.
2. Put brakes using different brakes to fail the build as early as possible.
During initial stages, things might not go as planned, but one need to have patience during
early stages it takes few months to get all on track. Once everything starts heading as per plan
then one can enjoy years of rising productivity for each product unit.

Devops landscape involves multiple stages based on SDLC, enabling Agile in a proper way
as follows-

A. Feature definition/Planning.
Product owners (POs- Managers)collect requirements from customer and create user stories.
Eg. JIRA is used generally to cover all user stories and track progress.
B. Design.
POs/Scrum master/Architect/Technical team together to compile design of the product based
on user stories.
C. Code/Development.
Developers comes into picture who starts working into development as per the assigned task.
Priority will be set by Scrum master who acts as a coach.
Code will be checked into Gerrit/GitHub/SVN/TFS repository.
D. Build Artifacts.
Devops uses Jenkins, TeamCity or Bamboo tool for running build (MS Build, maven,
Dockers etc.) stage on each commit.
E. Test/Code Analysis.
Devops run different types of test [Sanity, SIT, QA, UAT etc..] with code Analysis.
I would recommend, test to write using BDD approach [Given, When & Then] . eg. Writing
in python/Java unit test cases etc..
F. Feedback/Demo.
Dev team collects feedback from the build reports, test and code coverage etc.. If all good
then moves for the promotion else goes back to code.
G. Deployment and Validation.
Automated nightly builds runs the automated deployment over Physical
machines/VMs/Dockers/Kubernetes etc.. and runs the system tests for validation.
H. Delivery.
Devops delivers artifacts to respective Artifactory/destination depending on the all above
stage results. If passed, we can ensure smooth delivery of our product.
I. Continuous Monitoring and Reporting.
Devops enables log collection and app system events history for analysis of error/issues
handling in future releases. It also helps to gain apt feedback from users and figure out
direction to innovation. Eg. your Andriod seek permission to send event logs to google for
analysis to improve their service.

All above phases in DevOps landscape ensures smooth and precise delivery of our product
Artifacts. In turn increasing accuracy of the team with productivity. However, this DevOps
differ from organisation to or organisation but above stated model is quite generic.

More the time you save, more you utilize it in research of innovation to bring Success.

You might also like