Continuous delivery and infrastructure as code are mainstream, right? At least, many claim to practice it. If you don't do it, you're out - or at least falling behind. So taken to its logical conclusion, we should see a huge improvement in delivery speed in our IT world - and not just for small businesses and projects.
Kanban is an agile alternative that’s been receiving more and more attention in software development lately. Praised for its flexibility and simplicity, this method is known for the fact that instead of focusing on maximum utilization, it optimizes flow—the flow of work. We spoke with Agile coach Thomas Schissler about Kanban’s possibilities and its challenges.
Scrum has become a symbol of enterprise agility. Agility and scrum are often used synonymously. But anyone who does Scrum is not automatically agile, even though the framework can serve as a path to agility. Strict adherence to the Agile Manifesto’s values is much more decisive.
Companies often have an extensive application landscape. Nevertheless, there’s often a desire or need to regularly put new versions of the products into production, either to deliver new features or to close security gaps. This article presents prerequisites for continuous deployment using a roadmap. We will address the challenges of availability, security, and quality requirements. Special attention will be paid to the aspect of distributed responsibilities, independent of a successful establishment of DevOps culture.
When talking about successfully implementing software projects, Scrum as a framework paired with agile development is the current state of the art. You almost feel transported back to your teenage years, listening to schoolyard conversations about “the first time”. The comparison with agile development using Scrum isn’t so far-fetched. Everyone wants to do it, everyone says they do it, everyone seems to do it better than you - and yet, probably only 10 percent do it. And those who really do it, do they do it “right”?
In this tutorial, we want to build a complete Angular web application using Azure DevOps. The road will lead us through setup, YAML pipeline, Docker provisioning, and finally, creating the build content in Stages.
In the previous article "Scrum - an introduction for developers", we briefly addressed the topics of product backlog and user stories. We explained that an assessment of requirements with regard to scope and complexity is also necessary for agile product development. This article will go into this in more detail. We will provide an overview of how to move from time estimates and a content framework for a rough roadmap, or release planning to a concrete estimate of requirements for planning the iteration. It will become clear that developers help to get the estimates underway, especially during the process of estimating as a basis for planning.
The world has become more complicated, and not just since the onset of the pandemic. Simultaneously, increasing complexity requires a more flexible approach to projects, specifically in the development and IT fields. The notion of agile development is not new. It offers an opportunity to better position oneself to transition from reactivity back to proactivity, especially during turbulent times. Scrum in particular continues to prove itself as a crisis-proof companion.
So you’ve decided to attend DevOps Conference but you don’t know how to break it to your boss that it is a win-win situation. Don’t worry, we’ve got you covered. Follow four simple steps and use these arguments to show why your organization needs to invest in DevOps Conference!