How does one create a DevOps Culture?
This is probably the most frequently asked question related to adopting or rolling out a DevOps initiative in an organization. We need to look at this question more closely based on the principles of DevOps. While traditionally, organizations are structured into functional silos or departments, value for a customer is not created by any one […]
Role of testing in DevOps
One question that I get asked frequently is whether DevOps implies significantly higher costs for testing. Before answering that question, I would like to spend a few minutes on the types of testing that is usually recommended and what is done. Teams following the V-model would have a focus on Unit, Integration, System and Acceptance […]
Role of Architecture in DevOps
DevOps approaches highlight the value of early and frequent releases into production. In extreme cases, it is continuous deployment. In order to achieve this – or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution. The discipline of Enterprise Architecture recommends structured approaches to layer […]
Tracking in Agile projects
During a workshop on Agile Scrum, for participants new to Agile, a question came up – how is tracking in Agile different than in traditional project management? A very interesting question, which cannot be answered in short – covering some aspects, more to elicit interest in those new to Agile Scrum. In a typical project, the team […]
How to begin a DevOps journey?
Image source : blogs.msdn.com // https://www.linkedin.com/in/adriancockcroft One question that I get asked frequently, when talking about DevOps is: where do I begin? A follow-up question is – Can you recommend any checklist or set of steps to get into DevOps? My short answer to that question is: start where you can show some short term […]
Co-location of teams and collaboration in Agile – are we making too much of it?
When I started as an Agile coach eight years ago, my only relative and somewhat debatable “agile” experience was some iterative development we did on a very large product over nearly 19 months. This was a project where we worked with 6-week iterations for 14 iterations!! One thing that project taught me was the value […]
