DevOps, the Software Jack-Pot

<h2> </h2> <p>I started working in IT in 2007, and while I have never worked in a tech company, I saw how things progressed from the “expert” to “jack of all trades, master of none,” sustained by technical progress, automation, and cost-cutting. This article goes through the roles needed to deliver an IT product and how they were affected by the adoption of Agile and DevOps frameworks.</p> <h1>There Used To Be Business and Technical Analysts</h1> <p>A long, long time ago, there used to be a role for each phase of the Software Development Life Cycle; hence from a requirement of a “business person” until an actual production release, it was quite a long way.</p> <p>Hey, look, there’s a requirement! One eternity later…</p> <p>First, a business analyst was creating a business analysis document, in which the requirement would have been detailed out, usually after a few meetings with the business initiator.</p> <p>The document was passed along to the technical analyst, who would make the technical analysis, answering to questions such as “where is this requirement fitting the existing application, what is the impact, how should it be functionally and technically implemented?” The analysis was documented in a technical analysis document, which was passed along to the developer.</p> <p>The developer would implement the requirement based on the technical document. The implementation would be packaged into a release and sent to the testing team, which was testing the deliverables based on the technical analysis document. The business would also test during the user acceptance testing phase to confirm that the implementation is as expected.</p> <p><a href="https://betterprogramming.pub/devops-the-software-jack-pot-8111a2f1040a">Website</a></p> <h2> </h2>