The IT Applications/Development team at DORIS uses a software development methodology
called Agile. The basic premise behind Agile is to break down a project into smaller
parts and to plan development two weeks at a time. These two-week intervals are called
sprints. During each sprint, the team works on the features of the project that can be
completed in that timeframe. These features are taken from the backlog. This is a list
of features needed to complete the project.
Another basic principle of Agile methodology is to have the project team communicate on
a daily basis so that any issues can be identified and addressed without delay. This is
done by holding daily standup meetings where the team meets briefly for 15 minutes to
discuss progress and anything blocking the development work. The Agile team consists of
the Software Developers, Quality Assurance Analysts, the Business Owner and the Scrum
Master, who manages the backlog and the standup meetings.
Following are the terminologies used within the Agile development methodology:
Backlog Development The prioritized features list, containing short
descriptions of all
functionality desired in the product called user stories as well as a list of
acceptance criteria that describes the requirements for each feature.
Backlog Grooming When the Business Owner and the team review the user
stories in the
backlog to ensure the backlog contains the appropriate items, that these items are then
prioritized, and the items at the top of the backlog are ready for delivery.
Sprint Planning A collaborative effort involving the Scrum Master, who
meeting, the Business Owner and the entire Agile team. The purpose is to define the
work necessary to complete the user stories in the two week sprint by selecting stories
from the prioritized backlog.
Daily Standups Daily 15 minute meetings are typically held in the same
location and at
the same time each day. Ideally, a daily sprint meeting is held in the morning, as it
helps set the context for the coming day's work. This is a meeting of the entire team
and is run by the Scrum Master.
Retrospectives Meetings A meeting that's held at the end of each
sprint. During the
retrospective, the team reflects on what happened in the sprint and identifies actions
for improvement going forward. The work completed in that sprint is demonstrated for
the Business Owner and other stakeholders.