A sample text widget

Etiam pulvinar consectetur dolor sed malesuada. Ut convallis euismod dolor nec pretium. Nunc ut tristique massa.

Nam sodales mi vitae dolor ullamcorper et vulputate enim accumsan. Morbi orci magna, tincidunt vitae molestie nec, molestie at mi. Nulla nulla lorem, suscipit in posuere in, interdum non magna.

Make sure that you plan some of the logistics around your Scrum implementation – else you can get tripped up

People worry a lot about their Scrum implementation, in terms of ensuring that their people have got the required training, that some of the obvious pain points have been resolved, and in some cases, that a Scrum coach has been put in place. Over a period of time, getting hold of some of the issues related to the logistics of the Daily Scrum meeting, the rules for these meetings, and so on need to be set. These cause some of the biggest pain points related to the Scrum implementation, and some of the biggest issues for the team. However, there are some of the smaller issues that need to be resolved and set in place, and which ensure that the various meetings happen as desired. Some of these issues are:
Durations of meeting: Durations of the Daily Scrum is typically set for around 15 minutes, but there are a number of other meetings that are needed as a part of Scrum. Some of these meetings are the Sprint Planning, the Sprint Retrospective, the Sprint Review. Typically all these meetings are set for the Sprint end and Sprint beginning, but it is required to set the days on which these meetings need to happen; whether they need to be set for 1 day or stretch over 2 days, as well as the number of hours in which these meetings happen. Many people prefer to set exact timelines such as the Sprint Review happening for 2 hours, the Sprint Planning being broken down into 2 parts (User Story explanation, and Task estimation) together for 8 hours.
Setting the time that everybody can meet: When the teams have people from different geographic locations, setting meeting times and deciding who all needs to attend which meeting can be a logistical issue that requires effort to resolve. In some cases, people are pushed to re-schedule some of their meetings to alternate times, and it would be a mistake to diminish the importance of this logistical issue.
Defining your Sprint length: This means specifying the exact start and end dates for the Sprint, something that most people take for granted. When you set a specified Sprint length (something that is needed to happen at the start of the Sprints), it helps in getting a defined interval for the calculation of capacity, velocity. Typically when a team tries to calculate a Sprint length, the team can have their own opinions, and these can be 2 weeks, 3 weeks, 4 weeks, or more. Sometimes, there can be no way to get everybody to agree to the Sprint length, and in such cases, it is just easier to get everybody to vote and agree on the Sprint length which most people have voted on. Keep in mind that if you set a Sprint interval that is too short, then you will have the Sprint Planning, Retrospective, and Demo happening that often, which is something that people may not have thought about.
Decide penalties if people cannot attend: It is easy for people to use excuses for not attending the meetings, but it is very easy for such non-attendance to become a precedent, and more and more people use reasons for not attending rather than trying to re-shuffle their schedule in order to be able to attend the meeting. Set penalties and implement them (get the team to propose the penalties).

Leave a Reply

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>