<?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>user stories | Scrum Agile Project Management Expert</title>
	<atom:link href="https://www.scrumexpert.com/tag/user-stories/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.scrumexpert.com</link>
	<description></description>
	<lastBuildDate>Fri, 10 Jan 2025 16:20:00 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://www.scrumexpert.com/wp-content/uploads/favicon.png</url>
	<title>user stories | Scrum Agile Project Management Expert</title>
	<link>https://www.scrumexpert.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Requirement Specification vs User Stories</title>
		<link>https://www.scrumexpert.com/videos/requirement-specification-vs-user-stories/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 09 Dec 2024 17:44:39 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[requirements]]></category>
		<category><![CDATA[user stories]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=8168</guid>

					<description><![CDATA[This video explores what makes good requirements and how agile user stories help to improve the quality of requirements, whatever the nature of our software development. What are software requirements and how do they relate to the Scrum user stories? Is it requirement vs user story, or user story as requirement? An important part of agile software development is its user or customer focus. Our aim as software developers is to deliver outcomes that our users want or need. To do that it is vital to focus our work on the outcomes that matter to our users. Actually, this is true of any software development, agile or not. Requirements are often used to define the steps to deliver a solution, this is a big mistake. Deciding what our system needs to do is a difficult problem. Designing software well is a difficult problem too. We should avoid trying to solve these two difficult problems together in a single step, by conflating requirements with design. Video producer: https://gotocon.com/]]></description>
		
		
		
			</item>
		<item>
		<title>Your User Stories Are Too Big</title>
		<link>https://www.scrumexpert.com/videos/your-user-stories-are-too-big/</link>
					<comments>https://www.scrumexpert.com/videos/your-user-stories-are-too-big/#comments</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Fri, 15 Mar 2024 18:18:03 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[user stories]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=7813</guid>

					<description><![CDATA[Product owners often struggle to translate their big ideas into small user stories that the team can deliver in a sprint. When a user story is too big, it is harder to understand, estimate, and implement successfully. Some teams break the ‘business story’ into ‘technical stories’ but this doesn’t solve the problem because most or all of the technical stories need to be completed before there is anything meaningful for the stakeholders. This video presents you four simple, yet powerful techniques to break big stories into smaller stories that are meaningful to stakeholders and deliver business value. Video producer: https://agileleanireland.org/]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/videos/your-user-stories-are-too-big/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>Technical User Stories Don&#8217;t Work</title>
		<link>https://www.scrumexpert.com/videos/technical-user-stories-dont-work/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Tue, 10 Oct 2023 21:46:42 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[requirements]]></category>
		<category><![CDATA[user stories]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=7666</guid>

					<description><![CDATA[How do you organize the technical parts of your Agile software development work? Do you create Technical Stories or Technical User Stories alongside your User Stories? If so, we think that you are probably storing up some problems. This presentation talks about what are technical stories, and the use of technical stories vs user stories and describes why technical stories don’t work as a useful means of talking about, and planning our work. In Agile software development how we plan, organize and prioritize our work has a big impact on its quality. This video explores why that is the case, and how to do a better job. Video producer: https://gotocon.com/]]></description>
		
		
		
			</item>
		<item>
		<title>Driving Stakeholders Engagement with User Stories</title>
		<link>https://www.scrumexpert.com/videos/driving-stakeholders-engagement-with-user-stories/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Wed, 31 May 2023 14:27:08 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[requirements]]></category>
		<category><![CDATA[user stories]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=7534</guid>

					<description><![CDATA[The presenter designed this workshop during COVID times to engage stakeholders better by using User Stories more efficiently. The idea of the workshop is to help people move away from the notion that User Stories are merely a &#8220;As a .. I want .. so that&#8221; writing template. They can be a full-fledged way of engaging with every stakeholder involved during an Agile product&#8217;s lifecycle. The topics covered in this presentation about user stories include myth busters around user stories, 3 amigos, specs by examples, BDD, ATDD, Zero defect policies, etc. Video producer: https://agileindia.org]]></description>
		
		
		
			</item>
		<item>
		<title>Advanced User Story Mapping</title>
		<link>https://www.scrumexpert.com/videos/advanced-user-story-mapping/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Wed, 29 Dec 2021 17:50:33 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[user stories]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=6856</guid>

					<description><![CDATA[User Story Mapping is one of the most powerful collaboration tools for planning complex development activities. However, what are the differences between a good story map and a great one? How does one design and lead a great mapping session? In this presentation, Kevin Callahan shares three proven ways to make Story Mapping efforts great! In this video you will see all three in action and be introduced to using them in your own mapping sessions. Video producer: https://www.adventureswithagile.com/]]></description>
		
		
		
			</item>
		<item>
		<title>Executable Specifications with Scrum</title>
		<link>https://www.scrumexpert.com/knowledge/executable-specifications-with-scrum/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Tue, 23 Nov 2021 17:27:58 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Books]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[requirements]]></category>
		<category><![CDATA[user stories]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=6824</guid>

					<description><![CDATA[The book Executable Specifications with Scrum by Mario Cardinal starts with a strong statement: “This book aims to solve the recurring challenge encountered by many software development teams: They do not build the right software.” This is an ambitious goal, especially when you want to achieve it in a little bit more than 100 pages. The structure of the book follows the requirements&#8217; life cycle. It starts with the elicitation of the requirements, continue with their expression with user stories and ends with their confirmation with acceptance tests. Even if it provides a lot of valuable information, I am a little disappointed with this book, because it is neither a complete book on agile requirements as it focuses mainly on the user stories level and because it doesn’t explore enough on the xDD (Behavior Driven Development BDD, Acceptance Testing Driven Development ATDD) side to justify the executable title for me. Only two chapters (40 pages) on the total volume of the book are dedicated to scenarios and automated acceptance tests. This is however something that is also understandable because there are so many different tools available. The book will also have benefited from a use case that would have show the reader how to implement its concept in a practical example. I would however recommend reading Executable Specifications with Scrum, because it provides an interesting and original point of view about agile requirements and user stories. The book is very easy and enjoyable to read and with a good level <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/executable-specifications-with-scrum/" title="Executable Specifications with Scrum">[...]</a>]]></description>
		
		
		
			</item>
		<item>
		<title>How to Value User Stories?</title>
		<link>https://www.scrumexpert.com/videos/how-to-value-user-stories/</link>
					<comments>https://www.scrumexpert.com/videos/how-to-value-user-stories/#comments</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 19 Jul 2021 14:01:50 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[requirements]]></category>
		<category><![CDATA[user stories]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=6715</guid>

					<description><![CDATA[Business value, business value, business value. This presentation from Allan Kelly explores how to put a value on stories in a backlog while uncovering new requirements, elaborating specifications and valuable opportunities. We have it drummed into us: order work by business value, “do the most valuable stuff first.” But how many of us put a value on the work we are doing? How many of us attach business value to stories? Why not? Because it is damn difficult. It is far easier to use effort cost estimates (even if they are unreliable.) Video producer: https://www.agileonthebeach.co.uk/]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/videos/how-to-value-user-stories/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>Deliver Customer Value Instead of Story Points</title>
		<link>https://www.scrumexpert.com/videos/deliver-customer-value-instead-of-story-points/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 06 May 2019 14:06:09 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[user stories]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=5719</guid>

					<description><![CDATA[Are you sick of seeing your Scrum team treated as a sausage machine for turning user stories into code? Can your software developers only talk about how long something will take, or how exactly it will be built? This talk explores how to get your team focused on delivering customer value instead by * Asking questions that refine stories to deliver value more effectively, rather than estimating story points and technical tasks. * Building and refining backlogs around customer journeys, rather than breaking down epics into prioritized lists of stories. * Creating a culture of continuous discovery and experimentation, rather than delivering a fixed roadmap of features. Video producer: http://aceconf.com/]]></description>
		
		
		
			</item>
		<item>
		<title>Fifty Quick Ideas to Improve your User Stories</title>
		<link>https://www.scrumexpert.com/knowledge/fifty-quick-ideas-to-improve-your-user-stories/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 07 Jan 2019 14:28:07 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Books]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[requirements]]></category>
		<category><![CDATA[user stories]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=5508</guid>

					<description><![CDATA[Fifty Quick Ideas to Improve your User Stories is another book from Gojko Adzic, a consultant and author that already produced some very good books on Agile requirements like Impact Mapping and Specification by Example. It goal is to help people involved with Agile requirements to improve their discussion with the stakeholders and the planning activities associated with user stories. This is clearly not a book for beginners on how to write user stories. Fifty Quick Ideas to Improve your User Stories is structured around five user stories main activities: create, plan, discuss, split and manage iterative delivery. For each of the fifty tips about user stories contained in this book, there is an initial discussion about the concept, often with real life experience report. It is followed by two sections explaining the key benefits of the idea and how to make it work in practice. The book is easy to read as each idea is developed on 3-4 pages and mix user stories concepts with a practical vision gained from the authors&#8217; extensive consulting experience in Agile software development projects. You can read this book sequentially or explore the ideas that are more appropriate for your current situation. Fifty Quick Ideas to Improve your User Stories is a book that I will recommend to every software developer that has to elicit and manage requirements, whether they are user stories or not. The philosophy and the ideas contained in the book have value that goes far behind Agile software development. <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/fifty-quick-ideas-to-improve-your-user-stories/" title="Fifty Quick Ideas to Improve your User Stories">[...]</a>]]></description>
		
		
		
			</item>
		<item>
		<title>Death by User Stories</title>
		<link>https://www.scrumexpert.com/videos/death-by-user-stories/</link>
					<comments>https://www.scrumexpert.com/videos/death-by-user-stories/#comments</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Tue, 18 Sep 2018 15:15:53 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[user stories]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=5322</guid>

					<description><![CDATA[Do you find that user stories grow and multiply until you can’t fit them in your Scrum sprints? Are you struggling to see the big picture? Are you lost in user story hell? This presentation examines the OOPSI (Outcome, Output, Process, Scenarios, Inputs) technique and demonstrates how it accelerates delivery by ensuring that you are always working on the right thing and can see the bigger picture. OOPSI will give you a narrative and context for your analysis artifacts and the examples that support them. The OOPSI mapping technique can be used to help structure the discovery process, to help ensure that we’re always focusing on the most important thing and to avoid analysis paralysis. Similar to Matt Wynne’s Example Mapping, this technique can be done collaboratively using post-it notes in small teams. The 3 Amigos (domain expert, test expert and technical expert) follow the OOPSI process using different colored post-it notes to explore the business requirements and work towards some implementation examples. If you are using Impact Mapping, Story Mapping, Event Storming or Behavior-Driven Development (BDD) you will find that this fits in really neatly with those activities. https://vimeo.com/275530193 Video producer: http://ncrafts.io/ Read more about OOPSI on https://jennyjmar.com/2016/04/16/bdd-discovery-and-oopsi/]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/videos/death-by-user-stories/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
	</channel>
</rss>
