<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Arquivos Daily | beefor</title>
	<atom:link href="https://beefor.io/tag/daily-en/feed/" rel="self" type="application/rss+xml" />
	<link>http://54.214.97.162/tag/daily-en/</link>
	<description>making people awesome</description>
	<lastBuildDate>Sat, 26 Feb 2022 01:13:31 +0000</lastBuildDate>
	<language>pt-BR</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://beefor.io/wp-content/uploads/2021/12/cropped-Favicon-32x32.png</url>
	<title>Arquivos Daily | beefor</title>
	<link>http://54.214.97.162/tag/daily-en/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Daily Scrum: Five tips to implement today</title>
		<link>https://beefor.io/daily-scrum-five-tips-to-implement-today/</link>
		
		<dc:creator><![CDATA[admin@beefor]]></dc:creator>
		<pubDate>Sat, 26 Feb 2022 01:12:54 +0000</pubDate>
				<category><![CDATA[Management]]></category>
		<category><![CDATA[teams]]></category>
		<category><![CDATA[Agile Ceremonies]]></category>
		<category><![CDATA[Agile Transformation]]></category>
		<category><![CDATA[awesome teams]]></category>
		<category><![CDATA[Daily]]></category>
		<category><![CDATA[scrum]]></category>
		<category><![CDATA[Scrum Master]]></category>
		<guid isPermaLink="false">https://beefor.io/blog/daily-scrum-five-tips-to-implement-today/</guid>

					<description><![CDATA[<p>Conducting the Daily Scrum constantly contributes to improving the communication [&#8230;]</p>
<p>O post <a href="https://beefor.io/daily-scrum-five-tips-to-implement-today/">Daily Scrum: Five tips to implement today</a> apareceu primeiro em <a href="https://beefor.io">beefor</a>.</p>
]]></description>
										<content:encoded><![CDATA[<div style="margin-top: 0px; margin-bottom: 0px;" class="sharethis-inline-share-buttons" ></div><p><span style="font-weight: 400;">Conducting the Daily Scrum constantly contributes to improving the communication and engagement of the agile team in favor of the desired results through the product vision. However, knowing exactly how this meeting is carried out is important so as not to lose the purpose for which it is intended. </span></p>
<p>&nbsp;</p>
<p><span style="font-weight: 400;">Read more here:</span> <a href="https://beefor.io/blog/sua-daily-esta-prestes-a-mudar-com-o-beefor/"><span style="font-weight: 400;">Your Daily is about to change</span></a></p>
<p>&nbsp;</p>
<p><span style="font-weight: 400;">Several teams were used to periodically presenting the &#8220;status&#8221; of the project&#8217;s progress or deliveries to the leadership. Therefore, when making the transition to agile methods, they transfer some vices that harm the result of the meeting.</span></p>
<p>&nbsp;</p>
<h1><b>Daily Scrum with results</b></h1>
<p><span style="font-weight: 400;">The Daily Scrum needs to be an effective and results meeting. In other words and in a practical way, it is where you inspect progress towards the Sprint Goal and the evolution towards the completion of the work in the Sprint Backlog. So here are 5 tips to implement today and get more benefits:</span></p>
<p>&nbsp;</p>
<h2><b>01- Respect the 15-minute timebox</b></h2>
<p><span style="font-weight: 400;">According to the</span> <a href="https://scrumguides.org/docs/scrumguide/v2020/2020-Scrum-Guide-PortugueseBR-2.0.pdf"><span style="font-weight: 400;">Scrum Guide</span></a><span style="font-weight: 400;">, the maximum duration of the Daily is 15 minutes. This imposes on the team the need to be objective and direct. That is, it allows members to focus on what really matters and report progress or impediments to achieving the Sprint goal.</span></p>
<p><span style="font-weight: 400;">If the speech of a team member is not adding value, suggest that a certain issue can be resolved later, so that the focus is maintained and the timebox respected.</span></p>
<p>&nbsp;</p>
<h2><b>02- Focus on the Sprint Goal</b></h2>
<p><span style="font-weight: 400;">The focus is on evaluating progress towards achieving the Sprint Goal. Each day needs to represent progress towards the Sprint goal. Therefore, in each Daily, activities are reviewed and planned for the next 24 hours.</span></p>
<p><span style="font-weight: 400;">This is where the team&#8217;s progress is inspected, limiting itself to what has been done, what will be done and its impediments.</span></p>
<p>&nbsp;</p>
<h2><b>03- Identify impediments</b></h2>
<p><span style="font-weight: 400;">During the reports, impediments may arise. They appear throughout the development of activities and hinder or delay progress. It should be noted that the Daily is not to solve them, but to carry out their identification.</span></p>
<p><span style="font-weight: 400;">Then, after completion, together with the Scrum Master, take time with the members who identified the impediment to understand in more detail to help them. </span></p>
<p>&nbsp;</p>
<h2><b>04- Give visibility to activities</b></h2>
<p><span style="font-weight: 400;">One of the principles of agility is to make it clear and understandable to everyone involved what is happening. In this way, transparency becomes relevant, especially in projects that involve a high degree of complexity. To achieve this, simply make available to the team, for example, the Scrum Board or kanban. Through them, the team maintains the activities and their respective status in a visual way of the progress of the sprint. By demonstrating the different stages of the value stream, it encourages communication between members and clearly conveys progress.</span></p>
<p><span style="font-weight: 400;">In this sense, hold the meeting around the task board, if you are remotely, share the virtual board with everyone to highlight the evolution towards the Sprint goal.</span></p>
<p>&nbsp;</p>
<h2><b>05- Produce an action plan for the day&#8217;s progress</b></h2>
<p><span style="font-weight: 400;">At the end of each Daily, have an action plan agreed between the members for the working day. It should be possible to meet until the next day, when a new meeting will be held and the progress will be inspected again.</span></p>
<p><span style="font-weight: 400;">That way all members focus on what really needs to be accomplished.</span></p>
<p><span style="font-weight: 400;">The daily meeting is the moment in which the team articulates adaptations to be executed during the day and to be able to advance towards the Sprint goal.</span></p>
<p><img fetchpriority="high" decoding="async" class="aligncenter wp-image-926" src="https://beefor.io/wp-content/uploads/2022/02/blog_conteudo_Daily-Scrum-1024x800.png" alt="" width="633" height="514"></p>
<p>With beefor you can register the Daily, make action plans and check the history.<br />
This provides greater transparency for the team and focus on what is most important.</p>
<p>Get to know today what it&#8217;s like to have the beefor experience and bring more agility to your team! And you don&#8217;t need a credit card ?</p>
<p style="text-align: center;">
<p style="text-align: center;"><button id="btn-post-blog" class="beefor-btn btn-swipe-orange3-gradient">Start now!</button></p>
<p style="text-align: center;">
<p><span style="font-weight: 400;">If you liked this article, you may also be interested in these that describe the other Scrum meetings:</span></p>
<ul>
<li style="font-weight: 400;" aria-level="1"><a href="https://beefor.io/blog/sprint-review-alem-da-demonstracao-do-que-foi-feito/"><span style="font-weight: 400;">Sprint Review: in addition to the demonstration of what was done</span></a> <span style="font-weight: 400;">;</span></li>
<li style="font-weight: 400;" aria-level="1"><a href="https://beefor.io/blog/retrospectiva-da-sprint-melhoria-continua-do-seu-time/"><span style="font-weight: 400;">Retrospective: making the continuous improvement of your team</span></a> <span style="font-weight: 400;">;</span></li>
<li style="font-weight: 400;" aria-level="1"><a href="https://beefor.io/blog/sprint-planning-de-resultado/"><span style="font-weight: 400;">Sprint Planning – result and value for the organization</span></a> <span style="font-weight: 400;">;</span></li>
</ul>
<p>O post <a href="https://beefor.io/daily-scrum-five-tips-to-implement-today/">Daily Scrum: Five tips to implement today</a> apareceu primeiro em <a href="https://beefor.io">beefor</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Your Daily is about to change with the beefor!</title>
		<link>https://beefor.io/your-daily-is-about-to-change-with-the-beefor/</link>
					<comments>https://beefor.io/your-daily-is-about-to-change-with-the-beefor/#respond</comments>
		
		<dc:creator><![CDATA[admin@beefor]]></dc:creator>
		<pubDate>Tue, 07 Dec 2021 17:43:33 +0000</pubDate>
				<category><![CDATA[Management]]></category>
		<category><![CDATA[teams]]></category>
		<category><![CDATA[Daily]]></category>
		<guid isPermaLink="false">https://beefor.io/blog/your-daily-is-about-to-change-with-the-beefor/</guid>

					<description><![CDATA[<p>The main result that is aimed at holding the daily [&#8230;]</p>
<p>O post <a href="https://beefor.io/your-daily-is-about-to-change-with-the-beefor/">Your Daily is about to change with the beefor!</a> apareceu primeiro em <a href="https://beefor.io">beefor</a>.</p>
]]></description>
										<content:encoded><![CDATA[<div style="margin-top: 0px; margin-bottom: 0px;" class="sharethis-inline-share-buttons" ></div><p>The main result that is aimed at holding the daily meeting throughout the entire Sprint is to inspect the progress against the Sprint objective, so that if necessary, adapt the Sprint Backlog.</p>
<p>The Daily Scrum has a 15 minute duration limit, where each developer member describes how the progress was in a clear, transparent and objective way.<br />
It&#8217;s about alignment to <em>create advancement plan</em> for the day and <em>not status</em> .</p>
<p><img decoding="async" class=" wp-image-242 aligncenter" src="https://beefor.io/wp-content/uploads/2021/12/Daily-beefor-300x251.png" alt="" width="424" height="355" srcset="https://beefor.io/wp-content/uploads/2021/12/Daily-beefor-300x251.png 300w, https://beefor.io/wp-content/uploads/2021/12/Daily-beefor.png 611w" sizes="(max-width: 424px) 100vw, 424px" /></p>
<p>&nbsp;</p>
<h2>Daily on beefor</h2>
<p>On the beefor platform, Daily is considered as the team&#8217;s fuel to drive them forward. When configuring it, indicating the time, it also starts to score, demonstrating an increase in the maturity of the application of agility.</p>
<p>By carrying out it with constancy, <strong>beefor</strong> through metrics demonstrates the increased maturity of the team.</p>
<p>On the other hand, the team maintains the pace of development on the right path, delivering valued deliveries.</p>
<p>&nbsp;</p>
<h2>How to perform the perfect Daily<strong><br />
</strong></h2>
<p>To realize the perfect Daily it is important that all members of the development team participate and collaborate to re-plan and make decisions, not to solve problems.</p>
<p>In 15 minutes, efforts are focused on solving everything that involves the path towards the sprint goal and managing to generate the expected business value. That&#8217;s what&#8217;s at stake!</p>
<p>By checking progress toward the Sprint Goal and adjusting its plan accordingly, it&#8217;s up to the team to articulate adaptations to be carried out throughout the day.</p>
<p>With a shared vision of what needs to be done, the team is now committed to completing its work before the next meeting.</p>
<p>O post <a href="https://beefor.io/your-daily-is-about-to-change-with-the-beefor/">Your Daily is about to change with the beefor!</a> apareceu primeiro em <a href="https://beefor.io">beefor</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://beefor.io/your-daily-is-about-to-change-with-the-beefor/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
