Agile Software Development Methodologies
The purpose of our agile methodologies is to speed up software development aiming for the continuous improvement of the process, creating benefits such as enhanced communication and interaction among the team members, daily organization to reach set goals, the prevention of development failures, fast response to changes and significant increase in productivity.
BRQ uses the agile Scrum process. Learn more:
What is Scrum?
Scrum is an iterative and incremental agile software development and project management process. It is used for complex projects of which it is impossible to predict all variables.
How Does it Work?
In Scrum, projects are split into five (typically monthly) cycles called Sprints. A sprint represents a predefined time within which a set of activities should be performed. Agile software development methodologies are iterative, i.e., the work is split up into tasks.
Product Sprint Backlog
The functionalities to be implemented in the project are kept in a list known as the Product Backlog. At the beginning of each Sprint, a Sprint Planning Meeting is held whereby the Product Owner (who represents the parties involved) prioritizes the Product Backlog items, and the team selects the functionalities that it will be able to implement during the current Sprint. The functionalities assigned to a Sprint are transferred from the Product Backlog to the Sprint Backlog.
Kanban (Work Chart)
The team may also include a “work chart”, also known as Kanban, to organize the activities of the Sprint Backlog items by arranging them into four states (this may vary according to the project): To do, Develop, Test, and Completed. This “chart” is very useful, as it allows one to read the Sprint progress at a glance.
During a Sprint, the team has a brief 15-minute meeting on a daily basis, with all members standing, called Daily Scrum. The purpose is for each member to relay what they did on the previous day, what they intend to on the current day and if there is any obstacle hindering their work.
Sprint Review Meeting
At the end of a Sprint, the team presents the functionalities that were achieved during the sprint at a Sprint Review Meeting . Finally, a Sprint Retrospective is made to identify what worked well and what can be improved, and the team begins to plan the next Sprint.
Burn Down Chart
Burn Down is a plain chart with an x- and a y-axis based on activities that are limited to a single work day. The x-axis represents the number of tasks existing in the Sprint and the y-axis the size of the Sprint.
Roles and Responsibilities
There are three main roles: Product Owner, Scrum Team, and Scrum Master:
- Defines product requirements, decides the release data and what it must contain.
- Responsible for the return on investment (ROI) of the product.
- Prioritizes requirements according to their market value.
- May change requirements and priorities of each Sprint.
- Accepts or refuses the result of each Sprint.
- Ensures the team is fully functional and productive.
- Facilitates the cooperation between functions and areas and removes obstacles for the team.
- Protects the team against external interferences.
- Ensures the process is being followed. Attends daily meetings, Sprint reviews, and planning.
- Cross-functional, 5-9 members.
- Selects, among prioritized items, which will be performed during the Sprint.
- Each member has the right to choose their task for the Sprint
Learn more through the links below:
- Agile Manifesto Website – History of the origin of the agile development paradigm
- Scrum Overview Website – Eclipse Project
- Implementing Scrum Website
- Agile Atlas Website
- Mind Master
- • Rush – Agile project management method prioritizing deadline