Agile/DevOps

DevOps

DevOps is the way a group of people, who typically hold different roles, skills, and responsibilities, work together to achieve some goal. It’s a collaboration protocol, and asking one person or one team to “do all the collaborating” makes no sense. Put another way, if you adopted DevOps because you had a silo problem, creating a new “DevOps” silo is unlikely to be an effective solution. (1)

Widely accepted definitions of DevOps:

The DBA Role in DevOps

"We simply don’t give DBAs enough credit for all the tasks they do beyond writing queries."

https://towardsdatascience.com/has-devops-killed-the-ba-qa-dba-roles-fbc187abdde

Agile

The Agile Manifesto

Manifesto for Agile Software Development
We are uncovering better ways of developingsoftware by doing it and helping others do it.Through this work we have come to value:

Individuals and interactions 

Working software

Customer collaboration 

Responding to change


over

Processes and tools

Comprehensive documentation

Contract negotiation

Following a plan

That is, while there is value in the items on the right, we value the items on the left more.

Kent Beck, Mike Beedle, Arie van Bennekum, Alistair Cockburn, Ward Cunningham, Martin Fowler, James Grenning, Jim Highsmith, Andrew Hunt, Ron Jeffries, Jon Kern, Brian Marick, Robert C. Martin, Steve Mellor, Ken Schwaber, Jeff Sutherland, Dave Thomas
© 2001, the above authorsthis declaration may be freely copied in any form,but only in its entirety through this notice.

Scrum / Kanban / Scrumban

Unplanned Work

Unplanned Work Cheat Sheet.pdf

Tools

Online tool for running Retrospectives (aka Lessons Learned)

Bibliography & References