Just as the logbook is the document that allows us to follow the route, incidents, and experiences of a ship and its crew (and, eventually, other types of ships such as airplanes), complicated large technological projects also have a kind of logbook, although in this case, it acts beforehand, and not afterwards: the backlog.
In technology, a backlog It consists of a document that explains the functionality and purpose of a complex system, what we want it to do, but not how to do it.
The backlog It is imperative in the Scrum methodology, which is used to build complex systems from the bottom up, when the traditional approach was to focus development precisely the other way around, that is, from top to bottom.
However, the backlog can be perfectly used by itself, as a concept, for any technological project.
In scrum there are two types of backlog: product backlog and sprint backlog. The product backlog it describes, in a generic way, the functionalities and uses that are going to be given to the system, as well as everything that you want it to do.
Free consultation for all members of the project, it can only be modified by whoever orders the system (or, failing that, whoever is delegated).
The fact that it is generic, allows someone without technological knowledge to carry out its update.
An aspect that the product backlog You must consider is the relationship between the cost of the system and the economic benefit that it will bring to those who implement it.
This is an especially important point; Creating a new system is only done for two reasons: the first is imperative, because for some reason the old system can no longer be used. This may be due to organizational and / or product / service changes, or to changes in the legal regulations in which the organization and business are framed.
The second reason is to introduce an improvement that allows us to be more productive, lower costs or maximize profit.
This second reason is always voluntary, and will naturally be introduced only if there is an effective improvement in financial results. It is, therefore, here where we are most interested in analyzing the price / performance ratio and knowing the benefits.
In the first case, we are interested in knowing the benefits, of course, but as it is a mandatory introduction measure, we will be more interested in controlling expenses (which is not always the same).
The sprint backlog It consists of a document that defines the way in which the modifications to the system will be implemented in the next iteration.
The document is divided into tasks, each of which must be brief (if it is not, it is subdivided into as many that are), although these tasks are not assigned directly to a member of the development team, but rather are divide them among these as they see fit.
Photo: Fotolia - Oleksandr
