The Key Principles of the Agile Manifesto
The Agile Manifesto’s 12 principles, as described by the Agile Alliance, include these essential components:
- User satisfaction: The highest priority of an agile development approach is to satisfy users through continuous delivery of software.
- Frequent release cycles: Agile development relies on release cycles of a few weeks to a few months.
- Close collaboration: University staff should work closely with developers on the project to ensure it meets the institution’s unique goals.
- Sustainable development: The approach should allow for a constant pace that can continue indefinitely.
There are different types of agile development methodology — most notably, scrum, a sprint-driven approach that is most common among agile proponents. Ultimately, the goals of agile methodology focus on continuous software development that considers the needs of students, faculty and staff. It can adapt to changes as they happen.
DIVE DEEPER: Learn more about DevOps and how it can work for your institution.
What’s the Difference Between Agile and DevOps?
DevOps, in many ways, is the expansion of the agile development approach, as both are a reaction to the waterfall style of development. One concept that applies to both disciplines is the idea of “shifting left,” which explores the later pieces of the waterfall process much earlier in a DevOps or agile environment.
But DevOps has a different target audience and moves more quickly. As a blog post from the tech education platform Guru99 notes, there are significant differences in team structure, audience and scale. Agile development tends to enable problem-solving for smaller teams, while DevOps by nature tends to work across departments to achieve larger goals quickly.
In essence, DevOps “brings two large siloed teams together to allow for quicker software releases while Agile is focused on getting smaller teams to collaborate with each other so it can react quickly to the ever-changing [user] needs,” wrote Kaya Ismail in a 2018 comparison of the technologies for CMS Wire.
The role of interaction also differs in each approach. For example, DevOps leans heavily on process automation tools such as Infrastructure as Code, while agile focuses on a collaborative approach to problem-solving.
GET THE INFOGRAPHIC: Here’s how it started. And here’s where it's going. Click the banner to learn the history of higher ed IT.