Please enable JavaScript.
Coggle requires JavaScript to display documents.
Azure DevOps Getting Started - Coggle Diagram
Azure
DevOps
Getting Started
Union of
people
process
product
build, test, deploy
improves
release process
no# of releases
Quality of S/W
VSM
Value Stream Maps
Compute the activity ratio, or overall efficiency, of your processes
STEP1: Analyzing
Your existing artifacts, such as deployment packages and NuGet, as well as your container repositories.
Your existing test management tools.
Your existing work management tools.
Recommending migration and integration strategies.
Assess current process
Waterfall model issues
They use a waterfall approach. Management sets the priorities. Developers write code and hand the build off to QA. QA tests and then hands off to ops for deployment.
Waterfall could be acceptable for a small team, but here the goals aren't always clear and they seem to change frequently.
Testing is delayed until late in the process. That means it's harder and more expensive to fix bugs and make changes.
There's no clear definition of what "done" means. Each team member has their own idea. There's no overall business goal that everyone agrees on.
Some code is in a centralized version-control system. Many tools and scripts exist only on network file shares.
There are many manual processes.
Communication is haphazard and depends on email, Word docs, and spreadsheets.
Feedback is also infrequent and inconsistent.
On the plus side, the team seems to get along, and they want to make things better
Best approach:
A DevOps practice often begins with an understanding of your existing processes. From there, you can evaluate what's working well, what's not, and focus on what to fix first.
STEP2: value stream mapping
to asses process efficiency
The purpose of a
VSM
is to visually show where in the process a team creates value and where there's waste
Azure DevOps Resource Center
elite performers
deploy more frequently
Reduce lead time from commit to deploy. Lead time is the time it takes for a feature to make it to the customer
Reduce change failure rate
Recover from incidents more quickly.
the key is DevOps