#DevOps: What is it?
#DevOps is a group of practices used to bring automation to the interactions between software development teams and IT teams, so that the processes of building, testing, and releasing is done more efficiently and with less error.

● A Mindset
 Much like #Agile, #DevOps is a mindset, integrated into a team culture. It’s used to bring better communication with the software and IT teams. It does this by working a new software development method into the development team, where smaller increments are deployed in hours rather than days, so bugs can be reported, fixed faster, and managed more easily.

● One Piece at a Time
 When building a house, you go one brick at a time, rather than building four walls separately, then cutting them down to fit when they’re all different sizes. This is the #DevOps approach-- one small part at a time, dealing with the bugs and problems in the software in small bits, building it up to be better integrated. Because of this smaller-part approach, possibly game-breaking bugs can be spotted sooner and with less repercussions should they happen.

● Done Faster, Done Better
When feedback comes around faster, teams work faster. Fast, transparent communication keeps teams working, making the downtime as one team waits for feedback much shorter. When teams work faster and communicate better, they can put out a product sooner, and have it be stronger than in traditional frameworks.

● Frequent Delivery
 With small and frequent software changes, content can be reviewed and polished to be ready much sooner than traditional, large-scale updates. This leads to frequent delivery of  #content, where customers can review the software as it builds and send feedback before something they want to be changed has already had hours of work put into it.

● Shared Data, Shared Ideas
 In a DevOps mindset, data and work are shared among the group, which integrates a culture of feedback and teamwork. Imagine you’ve written code, and there is a bug embedded in it you somehow missed, and it could lead to a memory leak that significantly impairs the performance of the software increment. Rather than bringing the code into the #increment and having to fix the issue after it’s already caused a problem, another team member could spot it in the work you’ve shared with the team and rectify it before it causes downtime.

 Those are the basics of the #DevOps method. #Certifications like #SAFe DevOps and #ICP-IDO are utilizing #DevOps to integrate a better back-and-forth between operations and development.

---

Send in a voice message: https://anchor.fm/aleph-global-scrum-team/message