Agile Methodology

Hastega lives one sprint at a time. More flexibility, more control and more resilience to change.

Agile and Scrum: what does it mean?


Agile is a methodology of work applied within the framework of Lean Manifacturing around the 1950s. We talk about Agile Methodology in the field of software development for the first time in 2001, with the drafting of the Agile Manifesto.

Individuals and interactions more than processes and tools.
Working software more than exhaustive documentation.
Collaboration with the client more than contract negotiation.
Responding to change rather than following a plan.

Scrum is an agile framework, that is a particular declination of the method focused on finding flexible solutions to complex problems. Within Scrum every member of the team has a precise role (e.g. Product Owner, Scrum Master…) and must follow a series of well-defined practices to achieve the Sprint Goal.

Transparency

Inspection

Adaptation

Step 1

Analysis & Design


At the beginning of the project the functional requirements are collected and described through the User Stories. All the material is then collected inside the Sprint Backlog and sorted by priority. In this phase the technologies, the instruments and the duration of the Sprint are also defined (usually from 2 to 4 weeks).

Step 2

Sprint


Once the project is started a Sprint Planning is done, a meeting necessary to determine the Sprint Goal, or the goal you want to achieve by the end of the Sprint. User Stories are broken down into smaller Tasks and the team proceeds with software development. Every day a short alignment (Daily Scrum) is carried out to understand any difficulties encountered and make sure that the work proceeds smoothly.

Step 3

Review & Release


At the end of the Sprint is carried out the so-called Sprint Review, in which the final customer is also involved. The progress made in the previous weeks is shown and feedback is collected. In this context, the Increment takes shape, which represents the sum of all the features and fixes on which the team worked during the Sprint: then a release of the software takes place. Finally we proceed with a new Sprint Planning and the procedure starts from the beginning.

The method is not everything

Agile and Scrum define practices, then we implement them thanks to the use of the most sophisticated tools and the best technologies.

Toolkit
Privacy Settings
We use cookies to enhance your experience while using our website. If you are using our Services via a browser you can restrict, block or remove cookies through your web browser settings. We also use content and scripts from third parties that may use tracking technologies. You can selectively provide your consent below to allow such third party embeds. For complete information about the cookies we use, data we collect and how we process them, please check our Privacy Policy
Youtube
Consent to display content from Youtube
Vimeo
Consent to display content from Vimeo
Google Maps
Consent to display content from Google
Spotify
Consent to display content from Spotify
Sound Cloud
Consent to display content from Sound