- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
- Limitation of Work In Progress (WIP)
- Visual representation of work (Kanban Board)
- Pull system (team members to only “pull” new tasks once the previous task is complete.)
- Work in short iterations (called Sprints)
- Plan you tasks for Sprint in Advance, during Sprint you are working only on tasks from Sprint Backlog)
- Short Daily meetings, when team members talk about progress and obstacles
- After a Sprint there is a time for Review and Retrospective
- Next iteration begins from planning and incorporating feedback from previous Sprint
- Work in Discrete Iterations
- Minimal Viable Product (Draft of the paper?)
- Visualize your Workflow
- Shorten the Feedback Loop and Look for it
- Test Driven Design
- Be Adaptative, Not Predictive
- Team Work
- Academic work is solo work
- If you are a PhD student is harder to change your environment (easier for PI)
- Feedback in academia often happens too late
- ‘Things go slower here’
- Agile vs Slow Science
- Every discipline and research project is different