Digital Humanities focuses on agile, flexible development, working closely with researchers to ensure high quality and reliability in project outcomes.
We hold the following guiding principles influenced by software process improvements such as agile:
- Realising the client's research objectives outcomes through early and continuous delivery of software and related outputs is what we aim to do.
- Research projects can change, and we adapt - even late in development. We value being flexible and responding to the information to hand at a point in time for decision-making rather than stick doggedly to an outdated original plan.
- We share our work-in-progress technical building frequently; we choose to focus on having less functionality but working properly rather than more functionality that is 'buggy' or untested.
- Research team members and developers expect to work together regularly throughout the project, even daily at key points.
- The most efficient and effective method of conveying information to and within a development team is face-to-face conversation so we do this where the project set-up allows.
- The best way of communicating technical progress is by demo. The earlier this uses real research data, the better.
- We keep an active eye on complexity – to understand where it is necessary for the project aims. Elsewhere, we aim to keep things simple.
- We evaluate the shortest route to achieving the highest priority tasks, and revisit priorities regularly.
- Building our team's long-term capabilities through working with researchers is a key outcome. Working in a team may not be most efficient, but is preferable where possible.
- We believe that teams that reflect on how to become more effective and makes adjustments to behavior regularly continue to improve and learn with each project. We embrace this way of working.
Influenced by the 12 Principles Behind the Agile Manifesto (https://www.agilealliance.org/agile101/12-principles-behind-the-agile-manifesto/