-
Notifications
You must be signed in to change notification settings - Fork 1
Agile Development
This section gives a very brief overview of the key terms of Agile development and how we implement it in the DiSSCo team. This section is meant to be a practical guide on how to get started within the DiSSCo team, not necessarily a comprehensive look at Agile development.
User Story: A feature written from the user’s point of view: “As a researcher, I would like to annotate a digital specimen with a correction based on my experience in the subject.” User stories are preferred to feature lists as they allow the team to more easily understand the value.
Backlog: A list of User Stories to be completed in a project. Essentially, a prioritized to-do list.
Sprint: A set period of time where the team completes a set number of User Stories. Our sprints are two weeks long.
Daily Standup: Every morning, the developers (and often project leads) meet briefly for the daily standup (30 mins). During the meeting, each person present answers the following:
- What did you do yesterday?
- What are you planning today?
- Any challenges?
Sprint Meeting: These occur bi-weekly on Thursdays and mark the end of one sprint and the beginning of the next. These meetings have two components: the Retrospective and Sprint Planning. Before the meeting, the team should fill out the Retro Board usually sent out before the meeting on parabol, indicating what went well and what needs improvement. The Retrospective part of the Sprint Meeting involves discussing these issues and deriving action points from them.
The Sprint Planning involves looking through the backlog and assigning work to each team member for the following sprint.
Backlog Refinement: This occurs mid-sprint, on the opposite week of the Sprint Meeting. In these meetings, the team examines the existing backlog, discusses new user stories to add to the backlog, and prepares for the next sprint.