Commit 20e0fcdb authored by Ricardo Avila's avatar Ricardo Avila
Browse files

Merge branch 'authoring'

parents 78f89ab4 11770bb4
Pipeline #143470871 passed with stage
in 1 minute and 7 seconds
......@@ -25,8 +25,8 @@ notes-nav:
url: /notes/database/sqlite.html
- title: <i class="fas fa-project-diagram"></i> DevOps
- title: The Zen of DevOps
url: /notes/devops/zen.html
- title: Thoughts on DevOps
url: /notes/devops/devopsthoughts.html
- title: <i class="fab fa-python"></i> Python
- title: Anaconda
layout: notes
title: On the Zen of Good DevOps
title: Thoughts on DevOps
toc: true
......@@ -13,8 +13,17 @@ This is a collection of thoughts on what constitutes good project management and
"Agile" is an adjective, not a noun. It should never be capitalized, with exception of when it is in a title.
The key points from the original "Manifesto for Agile Software Development" (2001):
1. **Individuals and interactions** over processes and tools
2. **Working software** over comprehensive documentation
3. **Customer collaboration** over contract negotiation
4. **Responding to change** over following a plan
### People, not processes
The original "Manifesto for Agile Software Development" states that we should emphasize: "Individuals and interactions over processes and tools", which ironically runs counter to much of corporate Agile™.
The first point of the original manifesto: "Individuals and interactions over processes and tools", is ironically, the most often violated in corporate Agile™ implementations, such as Scrum.
Key takeaways:
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment