When beginning with any large development project, typically your company will go into a meeting with a development firm with a set of ideas about what you want. You have a general idea of something you need. Maybe you need a website for your business. You may need some software that will help you process payments. You need a way of understanding something out of your data. You typically have a “why” in your head; you approach a meeting with a problem to be solved.
DevOps is a collaborative culture that automates processes between development (Dev) teams and operational (Ops) departments to facilitate software development, testing, and delivery.
Within any methodology that has been around for some time, it is inevitable that competing camps will eventually arise within the system. While as scrum is easily the most popular method used for moving projects through to their completion within an Agile environment, an older idea, taken from the Japanese model of Lean production, or Kanban, has seen a resurgence. Whereas Scrum breaks projects down into small pieces allowing a team to focus on one task at once, Kanban sees projects as part of a larger flow.
Read more