| Engaging user stories with scrum
Benefits of compromising user stories with scrum
In a sprint within the scrum framework, committing User Stories for its execution is an excellent action to lead the Work Team to define the tasks that they consider have the ability to execute within the established sprint time, therefore, the Work commitment is not defined by a boss and not by the client, but by the Work Team who will be in charge of executing the agreed commitments within a set time and it is only the Work Team who will receive the clients praise or criticism and users once the sprint ends.
The interesting thing about this action is that the commitment is not defined by a boss but by the project executing stakeholders who know their skills and response times, therefore, it is not accepted that an interested party who will not be executing tasks and making additional efforts in the case if required, impose the volume of work and the delivery time of the product increase.
Based on the above, the benefits of engaging User Stories with scrum are as follows:
1) The Work Team is the only one that defines the volume of work within the sprint.
2) The project manager or leader only plays a moderating role during the negotiation of the sprint content between the client and the work team.
3) The members of the Work Team will be more motivated to fulfill the commitments, since they are the ones who define the workload of the sprint.
4) The praise and criticism of the sprint product increments fall on the Work Team.
5) Recognition for the work done within a sprint is objectively directed to the Work Team.
¿How to compromise user stories with scrum?
During the sprint planning, the Work Team at the time of defining the volume of User Stories and tasks with which they undertake to deliver once the sprint is finished, requires the analysis and review of the following points:
1) Knowledge of the product, service or process which they are going to implement or improve.
2) Number of sprints where they have worked together and their sequential increase in team productivity.
3) For each work story, break down the tasks that must be executed to implement a user story.
4) Identify the level of dependency that each user story has with respect to the inputs that external agents must provide during the execution of the tasks.
5) Identify the risk level of each user story during its execution.
Steps to engage user stories with scrum
Known the benefits and how to compromise User Stories. The sequential steps to follow are the following:
1) The Product Owner reports the prioritization of User Stories.
2) The Work Team reports the technical limits that the prioritization of User Stories may present at a functional level.
3) The scrum master leads the meeting between the client and the work team.
4) The work team with the Product Owner define the User Stories that they expect to deliver in the next sprint.
5) The Work Team identifies and evaluates the tasks that must be executed per user story to inform how many user stories are engaged in the next sprint.
Created by - Being its last update the: 2021-09-21Send commentOther topics of interest |
|