Scrum Framework

Scrum Framework

1. Why scrum?

   • because traditional development methodologies are very slow with heavy processes. Scrum, which is agile and short-lived with satisfactory results
     • What is agile?
       • interact in the processes, collaborate with the client, work with complete documentation and make modifications

2. Scrum story

   • (1995) Designers of this method: Jeff Sutherland and Ken Schwaber
   • (1996) combination with extreme programming by: Mike Becdey
   • (2001) Agile Software Development Post with Scrum by: Ken and Mike

3. roles

   • Product Owner
     • in charge of defining the characteristics, profitability, launch dates, content and accepting or rejecting the development of the product
   • The Scrum Master
     • in charge of representing the project management, promoting scrum values ​​and practices and allowing close cooperation in all roles and functions.
   • Team Scrum
     • The team in charge of product development

4. artifacts

   • Product Backlog, Sprint Backlog, and Burndown Chart
     • These artifacts allow to have a clear vision of the product and the expected result.

5. ceremonies

   • Sprint Planning, Sprint Review, Sprint Retrospective, & Daily Scrum Meeting
     • They are all the meetings necessary for the development of the project, such as the daily Scrum meeting that serves to see the progress of the development team day by day.