{"id":188,"date":"2023-12-10T18:08:11","date_gmt":"2023-12-10T18:08:11","guid":{"rendered":"https:\/\/nextagile.ai\/blogs\/?p=188"},"modified":"2025-12-18T12:36:19","modified_gmt":"2025-12-18T12:36:19","slug":"how-to-make-a-timeboxed-event-more-effective","status":"publish","type":"post","link":"https:\/\/nextagile.ai\/blogs\/agile\/how-to-make-a-timeboxed-event-more-effective\/","title":{"rendered":"How to Make a Timeboxed Event More Effective?"},"content":{"rendered":"\r\n<p>How do we better utilize our time attending an insane number of meetings?<\/p>\r\n\r\n\r\n\r\n<p>Coaches get this asked a lot. While little can be done about the number of meetings just like driving in bumper to bumper traffic, we can surely improve the in-car time utilization!<\/p>\r\n\r\n\r\n\r\n<p>To make the situation worse, we are in the middle of a pandemic, and one thing that we all have experienced is the spike in the sheer number of meetings. What makes this situation more annoying is the purposeless, lacklustre, voice dropping due to poor internet connections and an absolute lack of timeboxing sense in a virtual environment.<\/p>\r\n\r\n\r\n\r\n<p>Those who are applying <a href=\"https:\/\/nextagile.ai\/blogs\/agile\/kanban-vs-scrum\/\">scrum<\/a> have to deal with the additional pain of\u00a0 all the events being timeboxed. Below is an estimate of the time spent across various events based on the sprint size.<\/p>\r\n\r\n\r\n\r\n<figure class=\"wp-block-table\">\r\n<table>\r\n<tbody>\r\n<tr>\r\n<td colspan=\"5\"><strong>Sprint Size<\/strong><\/td>\r\n<\/tr>\r\n<tr>\r\n<td><strong>Meetings<\/strong><\/td>\r\n<td><strong>1 Week<\/strong><\/td>\r\n<td><strong>2 Week<\/strong><\/td>\r\n<td><strong>3 Week<\/strong><\/td>\r\n<td><strong>4 Week<\/strong><\/td>\r\n<\/tr>\r\n<tr>\r\n<td><strong>Sprint Planning<\/strong><\/td>\r\n<td>2 Hrs<\/td>\r\n<td>4 Hrs<\/td>\r\n<td>6 Hrs<\/td>\r\n<td>8 Hrs<\/td>\r\n<\/tr>\r\n<tr>\r\n<td><strong>Daily Scrum<\/strong><\/td>\r\n<td>15 Min<\/td>\r\n<td>15 Min<\/td>\r\n<td>15 Min<\/td>\r\n<td>15 Min<\/td>\r\n<\/tr>\r\n<tr>\r\n<td><strong>Refinement<\/strong><\/td>\r\n<td>30 Min<\/td>\r\n<td>1-2 Hrs<\/td>\r\n<td>3-5 Hrs<\/td>\r\n<td>5-8 Hrs<\/td>\r\n<\/tr>\r\n<tr>\r\n<td><strong>Review<\/strong><\/td>\r\n<td>1 Hrs<\/td>\r\n<td>2 Hrs<\/td>\r\n<td>3 Hrs<\/td>\r\n<td>4 Hrs<\/td>\r\n<\/tr>\r\n<tr>\r\n<td><strong>Retrospective<\/strong><\/td>\r\n<td>45 Min<\/td>\r\n<td>1.5 Hrs<\/td>\r\n<td>2 Hr 15 Min<\/td>\r\n<td>3 Hrs<\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n<\/figure>\r\n\r\n\r\n\r\n<p>* Timeboxing for Refinement event is not mentioned in\u00a0<a href=\"https:\/\/nextagile.ai\/blogs\/agile\/scrum-guide-versions-and-implications\/\">scrum guide<\/a>\u00a0and is purely based on experience\u00a0So how does one rationalize the time spent on these events? How does one make best use of the time allotted, focusing on keeping the event productive and motivate team members to contribute effectively and efficiently so that everyone\u2019s time is better utilized?\u00a0Below are some of the things which have worked for us.<\/p>\r\n\r\n\r\n\r\n<ul class=\"wp-block-list\">\r\n<li>\r\n<ul class=\"wp-block-list\">\r\n<li>All the events should be booked in advance and we should emphasize invitees on accepting or rejecting the event. No action leads to confusion on their participation<\/li>\r\n\r\n\r\n\r\n<li>It\u2019s Ok to wait for people if they haven\u2019t shown up on time but that should be not more than 2 minutes.\u00a0<\/li>\r\n\r\n\r\n\r\n<li>We should have a facilitator of the meeting and if there is none then by default the organiser of the event should facilitate<\/li>\r\n\r\n\r\n\r\n<li>Try to keep 4 parts of your meeting \u2013\r\n<ul class=\"wp-block-list\">\r\n<li>\r\n<ul class=\"wp-block-list\">\r\n<li>\r\n<ul class=\"wp-block-list\">\r\n<li>Header \u2013 To read the objective of meeting, the ground rules, expected takeaways and also if any participant want to add something more to agenda<\/li>\r\n\r\n\r\n\r\n<li>Body \u2013 This is where we discuss the agenda items in detail and fulfil them.<\/li>\r\n\r\n\r\n\r\n<li>Tail \u2013 This is about concluding the takeaways of the meeting. Checking if we have fulfilled the agenda and the mutual agreements<\/li>\r\n\r\n\r\n\r\n<li>Next steps \u2013 In case we are vouching to meet again then we need to talk about what could be the agenda of that meeting<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n<\/li>\r\n\r\n\r\n\r\n<li>We believe that any meeting without an agenda should be rejected ????<\/li>\r\n\r\n\r\n\r\n<li>Many times, we get stuck in endless loop and in that case the facilitator should be empowered to cut it and let people get aligned with agenda again<\/li>\r\n\r\n\r\n\r\n<li>Also, try to find a \u2018no meeting zone\u2019 where a stretch of 5-6 hours in a day should be for individuals to do their \u2018work\u2019. For example, we can insist all stakeholders keep meetings before 11 am or after 5 pm so that the team members could have productive time for finishing their daily commitments.<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n<blockquote>\r\n<p><em>Explore top <a href=\"https:\/\/nextagile.ai\/agile-transformation-consulting\/\">Agile Transformation Companies<\/a> that redefine agility. Unlock speed, collaboration, and innovation for long-term success.<\/em><\/p>\r\n<\/blockquote>\r\n\r\n\r\n\r\n<p>PS \u2013 At few customers, we have kickstarted \u2018No meeting Fridays\u2019. We all need some breathing space for ourselves.\u00a0Wishing you all the best in your\u00a0<a href=\"https:\/\/nextagile.ai\/blogs\/agile-transformation\/agile-transformation-journey\/\">Agile Journey<\/a>!\u00a0Do leave your comments, we will love to hear your experience and unique perspectives.\u00a0<a href=\"https:\/\/nextagile.ai\/trainer-anuj-m-ojha\/\" target=\"_blank\" rel=\"noreferrer noopener\">Anuj M Ojha<\/a><\/p>\r\n","protected":false},"excerpt":{"rendered":"<p>How do we better utilize our time attending an insane number of meetings? Coaches get this asked a lot. While little can be done about the number of meetings just like driving in bumper to bumper traffic, we can surely improve the in-car time utilization! To make the situation worse, we are in the middle&#8230;<\/p>\n","protected":false},"author":4,"featured_media":4424,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"content-type":"","footnotes":""},"categories":[2],"tags":[5,7,6],"class_list":["post-188","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-agile","tag-agile","tag-project-management","tag-scrum"],"_links":{"self":[{"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/posts\/188","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/comments?post=188"}],"version-history":[{"count":8,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/posts\/188\/revisions"}],"predecessor-version":[{"id":5200,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/posts\/188\/revisions\/5200"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/media\/4424"}],"wp:attachment":[{"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/media?parent=188"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/categories?post=188"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/tags?post=188"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}