1. Introduction
Scrum is a framework used to manage complex projects. It is highly popular in software development, but it can be used in any other field where you want to deliver value in an iterative and incremental way. It gives us a clear structure for organizing teamwork, making collaboration and adaptability easier. Contrary to what you might expect, there are no hierarchies, individual obligations, or rigidly assigned tasks. The goal is for the team to operate autonomously, sharing responsibilities among all its members. It also provides short development cycles called Sprints, which allow you to deliver functional products frequently, receive continuous feedback, and smooth out the rough edges of the project over time.
There are 3 main roles in Scrum:
- Product Owner, in charge of defining the product's features, creating small, very clear and well-documented tasks, and prioritizing the work.
- Scrum Master, who makes sure the team follows Scrum practices, facilitating meetings and removing obstacles.
- Development Team, which is the team in charge of building the product.
There is a very important concept in Scrum that is the heart of the framework itself: the Sprint. A Sprint is a set of ordered events, spread over a fixed period of time, generally 2 to 4 weeks, during which the team works to complete a specific set of tasks. Later we will dissect them one by one, but in general terms, a Sprint includes:
- Sprint Planning: where the work to be done during the Sprint is defined
- Daily meetings (Daily Scrum): brief daily gatherings to synchronize the work
- Sprint Review: where the completed work is presented at the end of the Sprint
- Sprint Retrospective: a meeting to reflect on the process and look for improvements
When a Sprint ends, another one starts immediately, creating a continuous development cycle. Sprints end when there is no more work to do, or when the Product Owner decides that the product is ready for release.
If you want to dig deeper into this, I recommend reading the official Scrum guide at https://scrumguides.org/.
Now that we understand what Scrum is and what a Sprint is, let's look at the values and roles that make up this framework.
This work is under a Attribution-NonCommercial-NoDerivatives 4.0 International license.
Building SPAs with Django and HTML Over the Wire: Learn to build real-time single page applications with Python
The HTML over WebSockets approach simplifies single-page application (SPA) development and lets you bypass learning a JavaScript rendering framework such as React, Vue, or Angular, moving the logic to Python. This web application development book provides you with all the Django tools you need to simplify your developments with real-time results.
Buy the bookHelp me keep writing
Every coffee gives me a push toward the next article.
Sure, it's on me!
Comments
There are no comments yet.