Some basics of the Agile methodology

[mdabuhasan]

One of the most widely used Agile methodologies is Scrum . The Scrum methodology organizes work in Sprints . Each sprint is composed of a planning phase, a modest block of time useful for producing deliverables that have value but are not too complex and ends with a review that allows for gathering feedback from stakeholders or the market. A sprint has a relatively short duration, more than a week but less than a month.

A project will be completed with the sum of several Sprints that will produce the final result in an incremental logic , with the benefit of being able to make adjustments along the way (I will go into this point in more detail later).

But what exactly happens in a Sprint?

In the Sprint, tasks (project activities) are carried out and concluded, which are chosen and prioritized from a list of User Stories (which I briefly describe as a series of tasks) to be completed. The activity of associating a priority to the User Stories is carried out before the Sprint starts and is the task of the Marketing Owner (or Product Owner in agile jargon, i.e. the person responsible for completing the project).

During Sprint Planning, team members review prioritized tasks in the backlog, estimate the work required to complete them, and commit to their development and completion during the Sprint.

In the preliminary stages it is also useful to define buy phone number list the rules of the game and specifically what the “ Definition of done ” is, that is, what is meant when a task is indicated as concluded.

It is immediately noticeable that during Sprint Planning there is more of a “ pull ” mechanism than a “ push ” mechanism. In fact, the User Stories are prioritized by the Marketing Owner but it is the team that examines them, estimates the completion of the tasks and makes the commitment to complete them.

At the conclusion of the Sprint, the team and other stakeholders meet to review the results obtained in order to gather insights.

Before closing the Sprint, the team asks itself in the Sprint Retrospective how things went. Typically, the questions are answered: what went well? what went badly? what can we do to improve?

Once the Sprint is concluded , the new one starts. This process is repeated over time and allows to react to the change given its elasticity.