<?xml version="1.0"?>
<rss version="2.0"><channel><title>Stories: Stories</title><link>https://beta.jimiwikman.se/resources/stories/professional/714_ways-of-working/management/agile/?d=32</link><description>Stories: Stories</description><language>en</language><item><title>Mastering Agile: Core Principles That Power The Framework</title><link>https://beta.jimiwikman.se/resources/stories/professional/714_ways-of-working/management/agile/mastering-agile-core-principles-that-power-the-framework-r2226/</link><description><![CDATA[<p dir="ltr">
	<span>If you loved the <a href="https://community.atlassian.com/t5/Agile-articles-archived/Key-Agile-Frameworks-Scrum-Kanban-and-Beyond/ba-p/2818956?utm_campaign=kudos_article&amp;utm_content=topic&amp;utm_medium=email&amp;utm_source=atlcomm" target="_blank" rel="external nofollow">last article</a> on </span><span>Scrum and Kanban</span><span>, you're in for a treat. Today, we’ll be digging deeper into the </span><span>principles that power Agile</span><span>. While frameworks like Scrum and Kanban are the practical side of things, the principles are the underlying philosophy. They’re the secret sauce that makes Agile so flexible and effective. Ready? Let’s dive in!</span>
</p>
]]></description><guid isPermaLink="false">2226</guid><pubDate>Sat, 19 Oct 2024 08:48:06 +0000</pubDate></item><item><title>Making The Case for Replacing Story Points With Ideal Days</title><link>https://beta.jimiwikman.se/resources/stories/professional/714_ways-of-working/management/agile/making-the-case-for-replacing-story-points-with-ideal-days-r2223/</link><description><![CDATA[<p>
	Story Points started out as Ideal Days multiplied by three. In the words of Story Point inventor Ron Jeffries:
</p>

<blockquote class="ipsQuote" data-gramm="false" data-ipsquote="">
	<div class="ipsQuote_citation">
		Quote
	</div>

	<div class="ipsQuote_contents ipsClearfix" data-gramm="false">
		<p>
			“In XP, stories were originally estimated in time: the time it would take to implement the story. We quickly went to what we called “Ideal Days”, which was informally described as how long it would take a pair to do it if the bastards would just leave you alone. We multiplied Ideal Days by a “load factor” to convert to actual implementation time. Load factor tended to be about three: three real days to get an Ideal Day’s work done.” - Ron Jeffries, Story Points Revisited
		</p>
	</div>
</blockquote>

<p>
	Besides not leaving you alone, ‘the bastards’ didn’t understand the concept of Ideal Days either:
</p>

<blockquote class="ipsQuote" data-gramm="false" data-ipsquote="">
	<div class="ipsQuote_citation">
		Quote
	</div>

	<div class="ipsQuote_contents ipsClearfix" data-gramm="false">
		<p>
			“We spoke of our estimates in days, usually leaving “ideal” out. The result was that our stakeholders were often confused by how it could keep taking three days to get a day’s work done, or, looking at the other side of the coin, why we couldn’t do 50 “days” of work in three weeks.” - Ron Jeffries, Story Points Revisited
		</p>
	</div>
</blockquote>

<p>
	To fix this, they started calling their ‘Ideal Days’ just ‘Points’. Problem solved, right?
</p>

<p>
	<strong>Wrong.</strong>
</p>

<p>
	That’s where all the problems started. We replaced a slight problem with a string of bigger and worse problems.
</p>
]]></description><guid isPermaLink="false">2223</guid><pubDate>Fri, 18 Oct 2024 08:31:02 +0000</pubDate></item><item><title>The Progressing Landscape of Agile Practices Current Trends and Insights</title><link>https://beta.jimiwikman.se/resources/stories/professional/714_ways-of-working/management/agile/the-progressing-landscape-of-agile-practices-current-trends-and-insights-r2183/</link><description><![CDATA[<p>
	Agile methodologies have come a long way since their initiation, continuously adapting to meet the needs of teams across various industries. In this article, we will explore the latest trends in Agile practices, particularly within the Atlassian ecosystem, shedding light on how simplicity, cross-industry adoption, and remote collaboration are shaping the future of Agile.
</p>

<p>
	The Rise of Simplicity in Agile Practices
</p>

<p>
	In recent years, there has been a noticeable shift towards simplifying Agile practices. Teams are increasingly returning to the core principles that made Agile successful in the first place.
</p>
]]></description><guid isPermaLink="false">2183</guid><pubDate>Sun, 13 Oct 2024 11:50:00 +0000</pubDate></item><item><title>Conduct effective sprint retros using Confluence and Jira</title><link>https://beta.jimiwikman.se/resources/stories/professional/714_ways-of-working/management/agile/conduct-effective-sprint-retros-using-confluence-and-jira-r2180/</link><description><![CDATA[<p>
	<a href="https://www.atlassian.com/team-playbook/plays/retrospective" rel="external nofollow"><u>Sprint retrospectives</u></a> are a crucial part of the <a href="https://www.atlassian.com/agile" rel="external nofollow"><u>Agile</u></a> process, offering teams a chance to reflect on what went well, what didn’t, and how to improve future sprints. However, these retros can easily become disjointed when feedback is stored separately from sprint data, action items are forgotten, or retros are treated as a formality rather than an opportunity for meaningful change. 
</p>

<p>
	By integrating Confluence and Jira, you can streamline your retros, turning them into a productive part of your workflow– rather than an afterthought. 
</p>

<p>
	In this installment of our <em>Better Together</em> series, <strong>we’ll explore how using Confluence and Jira together can improve the efficiency and outcomes of your sprint retrospectives</strong>
</p>
]]></description><guid isPermaLink="false">2180</guid><pubDate>Sat, 12 Oct 2024 09:49:40 +0000</pubDate></item></channel></rss>
