Scrum methodology and the time factor
It is very important to control the time factor while implementing scrum projects. Scrum methodology advocates time bound activities, and one of the main reasons why scrum is capable of adapting itself to the changing development related conditions is because each activity is closely linked with a certain time frame. Whether it be the sprint planning meeting, or a sprint retrospective, none of the activities are supposed to extend beyond the time limit set up for the particular activity. It is the only way scrum can work and function properly. If an activity cannot be completed in time, it is either recalled, or reconsidered for another “go” or iteration, but under no circumstances the time limit can, and should, be extended. Setting up time limits for activities is also termed as “time boxing” in scrum.
It is very important to control the time factor while implementing scrum projects. Scrum methodology advocates time bound activities, and one of the main reasons why scrum is capable of adapting itself to the changing development related conditions is because each activity is closely linked with a certain time frame. Whether it be the sprint planning meeting, or a sprint retrospective, none of the activities are supposed to extend beyond the time limit set up for the particular activity. It is the only way scrum can work and function properly. If an activity cannot be completed in time, it is either recalled, or reconsidered for another “go” or iteration, but under no circumstances the time limit can, and should, be extended. Setting up time limits for activities is also termed as “time boxing” in scrum.
Importance of time boxing in scrum
Time boxing ensures that the development team members do not consume too much or extra time than that allotted to complete a user story or a development task, and at the same time the team members should not run out of development requirements before the sprint time is over. Scrum is all about balancing things and aspects, in the proper manner. The basic reason why time plays such an important part in all scrum related activities is team members should not spend or invest undue time and efforts after tasks, other than that suggested or recommended. Each requirement or the product backlog item has a certain value or importance attached to it. An item that has a significant market value attached to it is more important, and the team can afford to spend more time for its development. On the other hand, items which are less important or have a lesser value attached to them should be developed by investing least resources and time. Basically, it is a question of attaching the proper degree of importance to the items in direct relation to their worth.
Time boxing ensures that the development team members do not consume too much or extra time than that allotted to complete a user story or a development task, and at the same time the team members should not run out of development requirements before the sprint time is over. Scrum is all about balancing things and aspects, in the proper manner. The basic reason why time plays such an important part in all scrum related activities is team members should not spend or invest undue time and efforts after tasks, other than that suggested or recommended. Each requirement or the product backlog item has a certain value or importance attached to it. An item that has a significant market value attached to it is more important, and the team can afford to spend more time for its development. On the other hand, items which are less important or have a lesser value attached to them should be developed by investing least resources and time. Basically, it is a question of attaching the proper degree of importance to the items in direct relation to their worth.
Which activities should be time boxed while implementing scrum methodology?
Every activity in scrum should be ideally time boxed. It is the duty of the scrum master to ensure that activities remain time boxed, and the scrum team does not over extend it. The main features, which are an inherent part of scrum methodology, should be mandatory time boxed.
Every activity in scrum should be ideally time boxed. It is the duty of the scrum master to ensure that activities remain time boxed, and the scrum team does not over extend it. The main features, which are an inherent part of scrum methodology, should be mandatory time boxed.
Sprint planning meeting
The sprint planning is conducted in two parts, with each part not extending more than four hours each. Therefore, the entire sprint planning meeting should not extend more than eight hours excluding the lunchtime in the afternoon.
The sprint planning is conducted in two parts, with each part not extending more than four hours each. Therefore, the entire sprint planning meeting should not extend more than eight hours excluding the lunchtime in the afternoon.
Daily scrum meetings or the stand ups
Daily stand ups are brief, and should not extend more than 15 minutes each day.
Daily stand ups are brief, and should not extend more than 15 minutes each day.
Daily sprint
Ideally, the daily sprints should last for 8 hours. However, they may be set up to last for more time depending upon the complexity of the user stories and the time allotted to the project. The total sprint time should be decided unanimously by the team members and approved by the scrum master as well as the product owner. Whatever time is decided, it should be fixed and kept consistent on a daily basis.
Ideally, the daily sprints should last for 8 hours. However, they may be set up to last for more time depending upon the complexity of the user stories and the time allotted to the project. The total sprint time should be decided unanimously by the team members and approved by the scrum master as well as the product owner. Whatever time is decided, it should be fixed and kept consistent on a daily basis.
Sprint review meetings
The review should not extend more than 4 hours for a month long sprint.
The review should not extend more than 4 hours for a month long sprint.
Sprint retrospective meetings
The retrospectives should also not extend for more than 4 hours.
The retrospectives should also not extend for more than 4 hours.
Advantages of being time boxed
The main advantages of maintaining tight time schedules are:
The main advantages of maintaining tight time schedules are:
- The development process becomes more efficient
- The overheads are drastically reduced
- The velocity of the team increases significantly
Find out more, and download our free QuickScrum tool which can help you in implementing scrum in an effective and profitable way!
No comments:
Post a Comment