SCRUM Backlog

The agile manifesto possesss four (4) pillars: People and interactions on processes and tools; Software functioning on extensive documentation; Contribution of the customer on contract negotiation; To work with changes on following the plan. (AGILE, 2011). The base of the SCRUM sprints is its (Iterations with fixed time – generally the 2 6 weeks – and definitive activities daily pay). These sprints are executed until it does not exist more activities to be done in that project. These activities are told in the Product Backlog and possess urgency and priorities defined for the customer.

So that the activities of the Product Backlog enter in a Sprint, them they must be segmented in small activities. For possessing empirical character, the SCRUM bases the cost of software through the acquired knowledge already in the previous projects. That is, to determine in how many item the Product Backlog will have to be segmented, the team and the ScrumMaster (responsible for the good use of the SCRUM) they search knowledge in the previous projects esteem how many item of the Product Backlog will be necessary so that the product is produced. With these defined item, through the empirical knowledge, the team obtains to determine how many SPRINTS will be necessary to carry through the stipulated activities, taking with consideration its priorities and difficulty of implementation (using the concepts of cited LOC and FP previously). This type of boarding is used so that the cost of software is malleable for the customer.

That is, the customer will be able consequentemente to modify the Product Backlog and the amount of item that must be produced to the end of each Sprint. This activity is extremely useful when the customer not yet possesss well definite requirements or these requirements move constantly. The concept used in the SCRUM is the same concept of the estimate based on the process.