<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.omnivision.website/index.php?action=history&amp;feed=atom&amp;title=9.2.2_User_Stories%2C_Sprints</id>
	<title>9.2.2 User Stories, Sprints - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.omnivision.website/index.php?action=history&amp;feed=atom&amp;title=9.2.2_User_Stories%2C_Sprints"/>
	<link rel="alternate" type="text/html" href="https://wiki.omnivision.website/index.php?title=9.2.2_User_Stories,_Sprints&amp;action=history"/>
	<updated>2026-06-10T07:06:43Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.43.8</generator>
	<entry>
		<id>https://wiki.omnivision.website/index.php?title=9.2.2_User_Stories,_Sprints&amp;diff=294&amp;oldid=prev</id>
		<title>Mr. Goldstein: Created page with &quot;=== 9.2.2 User Stories, Sprints === Two key ideas in Agile are:  * &#039;&#039;&#039;User Stories:&#039;&#039;&#039; Instead of long, technical documents, Agile teams describe features from the perspective of the person who will use them. A user story sounds like: &quot;As a gamer, I want to be able to jump over obstacles, so I can explore new areas.&quot; or &quot;As a parent, I want to track my child&#039;s homework, so I know what they need to do.&quot; This helps everyone understand &#039;&#039;why&#039;&#039; a feature is important and wha...&quot;</title>
		<link rel="alternate" type="text/html" href="https://wiki.omnivision.website/index.php?title=9.2.2_User_Stories,_Sprints&amp;diff=294&amp;oldid=prev"/>
		<updated>2025-07-10T02:30:33Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;=== 9.2.2 User Stories, Sprints === Two key ideas in Agile are:  * &amp;#039;&amp;#039;&amp;#039;User Stories:&amp;#039;&amp;#039;&amp;#039; Instead of long, technical documents, Agile teams describe features from the perspective of the person who will use them. A user story sounds like: &amp;quot;As a gamer, I want to be able to jump over obstacles, so I can explore new areas.&amp;quot; or &amp;quot;As a parent, I want to track my child&amp;#039;s homework, so I know what they need to do.&amp;quot; This helps everyone understand &amp;#039;&amp;#039;why&amp;#039;&amp;#039; a feature is important and wha...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;=== 9.2.2 User Stories, Sprints ===&lt;br /&gt;
Two key ideas in Agile are:&lt;br /&gt;
&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;User Stories:&amp;#039;&amp;#039;&amp;#039; Instead of long, technical documents, Agile teams describe features from the perspective of the person who will use them. A user story sounds like: &amp;quot;As a gamer, I want to be able to jump over obstacles, so I can explore new areas.&amp;quot; or &amp;quot;As a parent, I want to track my child&amp;#039;s homework, so I know what they need to do.&amp;quot; This helps everyone understand &amp;#039;&amp;#039;why&amp;#039;&amp;#039; a feature is important and what problem it solves for the user.&lt;br /&gt;
* &amp;#039;&amp;#039;&amp;#039;Sprints:&amp;#039;&amp;#039;&amp;#039; As mentioned with Scrum, a sprint is a short, fixed period of time (like 1 to 4 weeks) during which a team works to complete a specific set of user stories. At the end of a sprint, the team should have a working piece of software that can be shown to the people who requested it. It&amp;#039;s like having mini-deadlines to keep everyone focused and motivated.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Bibliography:&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
* Cohn, Mike. &amp;#039;&amp;#039;User Stories Applied: For Agile Software Development&amp;#039;&amp;#039;. Addison-Wesley Professional, 2004.&lt;br /&gt;
* Schwaber, Ken and Sutherland, Jeff. &amp;#039;&amp;#039;Scrum Guide&amp;#039;&amp;#039;. Scrum.org, 2020.&lt;/div&gt;</summary>
		<author><name>Mr. Goldstein</name></author>
	</entry>
</feed>