DevOps can be described as a set of working practices which combines Development and IT Operations. It brings people, processes and technology closer together, which is renowned for offering higher value to customers and achieving costs.
Paul Raybould is back with the final section of 'A Real-World intro to SAFe - Scaled Agile Framework' series.
Here’s the last part in my series on Scaled Agile Framework. In this last part, I cover a range of topics including Inspect and Adapt, Measuring Flow and other useful principles to consider. If you haven’t read the first two parts, do check out part 1 and part 2 before reading on.
What is SAFe?
SAFe is a framework which combines various pieces of different agile methodologies and principles such as Scrum, Kanban, Extreme Programming (XP), Lean and DevOps.
Why use SAFe?
The SAFe model of working is relevant to large organisations with multiple development teams delivering highly complex systems.
Should everyone adopt SAFe?
Adopting SAFe in smaller team structures with few cross-team dependencies would negatively impact the agility of these teams and affect delivery and velocity.
Now, let me guess? Whilst you are reading this article you can name a project that has run late, ran out of budget, not met the requirements, generally underperformed against budget or proved problematic when put live?
Topics: DevOps and Testing