Scrum

Scrum

1. Scrum vs Waterfall

   • Waterfall
     • It is a method that consists of carrying out a project following a few stages, but its methodology can be very time-consuming:
       • 1. Plan 2. Build 3. Test 4. Review 5. Deploy
         • In the event that at any stage of the methodology they find errors or are criticized, they would have to go back to the previous stage or even to the first stage to correct
   • Scrum
     • In Scrum it is different since the process of the project methodology is much more agile, managing to present a deliverable product in a short time
       • 1. Plan 2. Build 3. Test 4. Review
         • These stages are completed over a period of one to three weeks and are called Sprints, which can be repeated up to four times or more, thus creating new and better versions and being able to present the best product, for example, in Sprint number four

2. In Scrum there are 3 roles that are needed for the framework to work well, which are: 1. THE PRODUCT OWNER: defines the characteristics that are needed in the product 2. SCRUM MASTER: in charge of being the product leader and defending its process 3. TEAM: which is made up of programmers, designers, and anyone else who helps produce

   • There are also 3 artifacts or documents that are used in Scrum which are: 1. THE PRODUCT BACKGROUND: Owners create a prioritized list of features Known as user stories, that list changes priority with each Sprint. Example of User Stories: (As a) (I need) (So that) 2. SPRINT BACKLOG: They estimate the work and commit to graphing it in the next Sprint, 3.BURNDOWN CHART: a chart that should get closer to 0 points as work is completed
     • Likewise, we have 3 ceremonies in Scrum, which are: 1. SPRINT PLANNING: where the Scrum master product owner and the team meet to discuss user stories and estimate their relative sizes 2. DAILY SCRUM: is a meeting in which the team discusses what they have completed since the previous one meeting, what they are doing and any blockages that need help 3. RETROSPECTIVE: The team demonstrates the completed work to the product owner and their team where they analyze what can be improved.