The term ‘Meeting’ brings to our mind an atmosphere where a group of people are sitting together to discuss serious issues: Some sitting bored and uninterested; some staring blankly trying hard to get a grasp of what are being discussed; and still some aggressively trying to prove their point. However, with changing times and methodologies, with pressure to meet deadlines, with time constraints, with increasing competition and with the need to stay a step ahead, there arose a new face of meetings- ‘The Scrum Meetings’ or more commonly known as ‘The Daily Scrum Meetings’.
These meetings are short and crisp and the members actually stand as the discomfort of standing makes sure that the meeting does not stretch too long. These meetings are held daily (usually in the morning) or at short intervals pre-decided by the team mates working on a particular project. The issues raised in these meetings strictly include only these topics:
However, more often than not, these meetings tend to stretch too long and get unfocussed, thereby destroying the very purpose of such meetings. Here are some effective tips for a successful stand up meeting:
The meetings should start at a fixed time every morning and the timing should be followed strictly irrespective of the fact that some team members have not arrived. You could offer incentives for those who arrive on time and impose penalties on those who do not. Also keep the meetings short and to-the-point. The daily scrum meetings should last for around 15 minutes or so.
The order and discipline are the essence of a stand up meeting. Only the scrum leader and the team members (who are directly working on the project) should be allowed to report in the daily scrum meeting and only one person should be allowed to speak without interruption at a given time.
It is a good idea to prepare a list of topics and priorities which need to be discussed during a stand up meeting. Only those items which are currently in process or those whose due date is approaching should be dealt with. Also, the topics should be of universal interest, else they tend to go off track.
Since it is important to keep the meetings short and crisp, it is essential for the success of the meeting that all the members are genuinely and actively involved during the entire meeting. To kick start the interest, you can start each meeting with a new joke, a motivating quote, a comic strip or any other interesting picture or image. You could also introduce a lottery system to decide who would speak next, thus giving a fair chance to everyone besides keeping the fun quotient high.
We have become so addicted to our phones or laptops that it becomes difficult for members to focus on the meeting if they are constantly checking their messages, answering e-mails, playing games or going through their codings. To avoid this problem, ensure that your stand up meetings are tech-free. This ensures respect for fellow team mates and also avoids distraction.
Daily scrum meetings are not called stand up meetings without a reason. Conventional meetings tend to stretch long, get boring and off topic when members are sitting comfortably. Standing up during these meetings ensures that the meetings are short, to-the-point and the energy level is high.
Before you start wondering what I am talking about, let me tell you that sometimes dramatic attitude helps bring a major change. Having said this, you can put your foot down and make it obvious that something is wrong by skipping the meetings if they stop being productive and are a mere status update routine. By not attending the meeting, you make a statement that your time is better used for more productive development and other tasks.
The basic idea of daily scrum meetings is to let the team members know what is being done, what needs to be done and what are the hindrances in getting them done. Anything other than these, needs to be dealt with later. Define a ‘Parking lot’ and list down the issues which are to be dealt later. After the meeting gets over, schedule another meeting with only those members who are directly related with that particular issue. You could maintain a notebook or a whiteboard to list down topics that are to be handled by a particular sub division and need a lengthier discussion. Such ‘parking lots’ should be accessible to the team members outside the daily scrum meetings too where they can list down their items that need to be addressed. That way, they are totally focussed and are not thinking about off topics during their daily scrum meetings.
Since the time is short, the team members should know exactly what they would speak at the meeting. Their speech should be strictly limited to what they did the day before, what they plan to do today and what are the difficulties they are facing in meeting their goals. For this, the scrum leader should make it clear to the team members what he expects to hear from them at the meeting. Anything off the topic should be immediately interrupted.
If you have outsourced your scrum projects, involving the remote team members in the daily meetings would be good idea. For this, you could set up video chats or conference calling during your daily scrum meetings. Just make sure that your meetings here are not held at a time which is unreasonable for them (Say 1:00 a.m. for them). This ensures that you are working as a team with your offshore mates. Again, as a scrum leader make sure that the team members make eye contact with each other and communicate with each other instead of talking and focussing only on you. This will make the meetings more effective and develop better understanding among the team.
Call it a daily scrum, daily huddle, morning roll-call, morning meetings, coordination meetings or our very own stand up meetings, these meetings are the call of the hour. By getting an update of what each team member accomplished yesterday and what he plans to accomplish today, the team members get a clear and co-ordinated understanding of how much work has been done and how much work remains. These meetings are also a way to ensure commitments for every member. When a member stands up and says, “I will do this task today,” he knows very well that he is supposed to report the next day whether the task was done or not.
With more than 10 years of on-time, on-budget project delivery experience, including complex, large scale & global projects, I have led international teams and controlled project budget in excess of $2 million. Born in Vadodara, Gujarat and raised in Ahmedabad, Gujarat, India, in my early professional career, I became a part of e-Governance application development team. My passion for programming and project management introduced me with the responsibilities like, Sr. Team Lead, and client account manager. I have served big names in the IT industry, such as, Cybage Software. I would credit my till date success to the basic knowledge. While working for RapidOps Solutions Pvt. Ltd., I took over the post of Project Manager and there I play the key role in the success or failure of any project delivered under my guidance and mentorship. Playing single point of contact with the clients, I ensure faultless information flow between requirement and developer. I serve a relationship between the technical development team and business teams and help them understand projects\products and their key benefits. I lead cross department collaboration with engineering, design, quality assurance, marketing, and related constituents. I believe that Project and Product Development Life Cycle via perfect documentation must be strictly followed for hassle free application release and closure. My project and product management skills and a rich experience of technical field led me to start this blog. My entrepreneurial spirit to keep engineering novice up to date with the latest managerial skills urged me to start this new venture. My motto is to teach you all more than just coding and implementation.
Though I spend most of my time untangling strategic and tactical issues at the professional front, but I love, travelling, listening soft music, and playing guitar in the free time. I love action, and have a personal library of action/thriller DVDs and novels at home.
Although there are some learnable aspects of leadership, leadership is often identified as something that comes naturally to certain personalities. Therefore, it is no surprise that certain people can act as better servant leaders and better Scrum Masters.
Let's look at some characteristics that will help you master with your Scrum Master Role.Join This Discussion >>
Hi there, Have you ever wondered why only too few people are successful? Many people work hard, they constantly chase for opportunities but still they have to spend and finish their careers with unsubstantial results. This is sad, so is the truth.
Like unsuccessful people, successful people chase for opportunities too, but what makes success scarce whereas mediocrity is abundant in professional careers?Join This Discussion >>
Hi there, I love that you're here because one of my favourite things to do is take a smart professional and lifetime student like yourself and make you become even more successful.
It's something that I practice in my own career, of course, but I love helping others too.Join This Discussion >>
Hi there, I hope I found you well and healthy. I am writing you about a subject that I was thinking since long time to write about it. Today is the day. :)
Are you looking for PDUs (Professional Development Units) to get or maintain a degree?
You shouldn't. Here is why? Because PDU is a byproduct of Lock-In Business Model, and this business model badly takes advantage of students.Join This Discussion >>
The role of a Scrum Master is one of many stances and diversity. A great Scrum Master is aware of them and knows when and how to apply them, depending on situation and context. Everything with the purpose of helping people understand and apply the Scrum framework better.Join This Discussion >>
You are moving from the world of fixed nouns towards a world of fluid verbs. Within the next years you will continue taking solid things -such as a car or a jacket- and turning them into intangible verbs. Your products are becoming your services and processes. With high doses of built-in technology, your car is becoming a service, continuously updated set of benefits adapting to your own usage and feedback, fierce competition and global innovation.Join This Discussion >>
There is so much more to be a software tester than merely logging bugs and testing to identify errors. There are inspiring examples of Agile working environments. Software testers have there the privilege to work as part of development teams which are like working on a movie set with the writers and producers. The testers work with everyone on the team, from the Junior Programmers to the Senior Project Leaders and inventors to continuously improve and build quality into the products and services.Join This Discussion >>
Are you good at business models?
Of course you are. We know all about business models, don’t we?
A lifetime as a consumer and almost a lifetime as a professional we all believe that we are well proficient in business models. We don’t hesitate more than a second to give our opinion if a business idea will work or not. And we are very generous to give our feedback how a company can perform better. But do we really have enough insights about business models?Join This Discussion >>
Our typical approach is to present organisational and moral benefits of Agile Scrum. How instantly Agility would enhance our teams and excel the interactions within our organisation and with our client ecosystem. How wonderfully our companies would serve customer-oriented products and services.
Is this really the correct approach? Is it better to highlight benefits of adopting Agile Scrum or the cost of not adopting?Join This Discussion >>
Dear Friends and Colleagues,
For the last few weeks we worked hard for you to make this revamp happen. If you are curious to know how International Scrum Institute uses Scrum, here are two simple facts for you which may be also a benchmark for your own agile delivery projects.Join This Discussion >>