rmw · May 9, 2014 22:14 · Aug 10, 2013 · Aug 10, 2013 · Aug 10, 2013 · Aug 10, 2013
diff --git a/scrum.md b/scrum.md
@@ -32,6 +32,7 @@ Some of its fundamental goals include:
 
 
 #### More reading:
+- [What's in a story?](http://dannorth.net/whats-in-a-story/)
 - [Splitting stories into tasks – when, why and how (or not)](http://lizkeogh.com/2011/08/23/splitting-stories-into-tasks-when-why-and-how-or-not/)
 - [Splitting Up Stories](http://lizkeogh.com/2008/09/11/splitting-up-stories/)
 - [MountainGoat Software's Scrum Guide](http://www.mountaingoatsoftware.com/topics/scrum)

diff --git a/scrum.md b/scrum.md
@@ -18,7 +18,7 @@ Some of its fundamental goals include:
 
 #### SCRUM definitions:
 
-- **user story** - A [user story](http://en.wikipedia.org/wiki/User_story) describes functionality of a system that will be valuable to a Non Development Team (NDT) stakeholder of a system or software (eg. "As a user, I want to login"). A user story should have business value, be testable, and be small enough to complete in one iteration. Typically, groups of user stories make up features.
+- **user story** - A [user story](http://en.wikipedia.org/wiki/User_story) describes functionality of a system that will be valuable to a Non Development Team (NDT) stakeholder of a system or software (eg. "As a user, I want to login"). A user story should have business value, be testable, and be small enough to complete in one iteration.
 - **story point** - A story point is an relative estimation unit used by Scrum teams. This is used to measure the complexity of implementing a story. Points have several advantages over estimating tasks using time -- for one, estimating development tasks is *really* hard! Using the story point abstraction takes the focus off of the actual time in hours or days and instead puts the focus on describing the relative expense and complexity of a task as compared to other tasks. Humans/developers are better at that.
 - **product backlog** - An never-ending list of all product requirements
 - **product owner** - prioritizes backlog

diff --git a/scrum.md b/scrum.md
@@ -18,7 +18,7 @@ Some of its fundamental goals include:
 
 #### SCRUM definitions:
 
-- **user story** - A [user story](http://en.wikipedia.org/wiki/User_story) describes functionality of a system that will be valuable to a Non Development Team (NDT) stakeholder of a system or software (eg. "As a user, I want to login"). A user story should have business value, be testable, and be small enough to complete in one iteration. Groups of user stories make up features.
+- **user story** - A [user story](http://en.wikipedia.org/wiki/User_story) describes functionality of a system that will be valuable to a Non Development Team (NDT) stakeholder of a system or software (eg. "As a user, I want to login"). A user story should have business value, be testable, and be small enough to complete in one iteration. Typically, groups of user stories make up features.
 - **story point** - A story point is an relative estimation unit used by Scrum teams. This is used to measure the complexity of implementing a story. Points have several advantages over estimating tasks using time -- for one, estimating development tasks is *really* hard! Using the story point abstraction takes the focus off of the actual time in hours or days and instead puts the focus on describing the relative expense and complexity of a task as compared to other tasks. Humans/developers are better at that.
 - **product backlog** - An never-ending list of all product requirements
 - **product owner** - prioritizes backlog

diff --git a/scrum.md b/scrum.md
@@ -18,7 +18,7 @@ Some of its fundamental goals include:
 
 #### SCRUM definitions:
 
-- **user story** - A [user story](http://en.wikipedia.org/wiki/User_story) describes functionality of a system that will be valuable to a Non Development Team (NDT) stakeholder of a system or software (eg. "As a user, I want to login"). A user story should have business value, be testable, and be small enough to complete in one iteration.
+- **user story** - A [user story](http://en.wikipedia.org/wiki/User_story) describes functionality of a system that will be valuable to a Non Development Team (NDT) stakeholder of a system or software (eg. "As a user, I want to login"). A user story should have business value, be testable, and be small enough to complete in one iteration. Groups of user stories make up features.
 - **story point** - A story point is an relative estimation unit used by Scrum teams. This is used to measure the complexity of implementing a story. Points have several advantages over estimating tasks using time -- for one, estimating development tasks is *really* hard! Using the story point abstraction takes the focus off of the actual time in hours or days and instead puts the focus on describing the relative expense and complexity of a task as compared to other tasks. Humans/developers are better at that.
 - **product backlog** - An never-ending list of all product requirements
 - **product owner** - prioritizes backlog

diff --git a/scrum.md b/scrum.md
@@ -35,4 +35,5 @@ Some of its fundamental goals include:
 - [Splitting stories into tasks – when, why and how (or not)](http://lizkeogh.com/2011/08/23/splitting-stories-into-tasks-when-why-and-how-or-not/)
 - [Splitting Up Stories](http://lizkeogh.com/2008/09/11/splitting-up-stories/)
 - [MountainGoat Software's Scrum Guide](http://www.mountaingoatsoftware.com/topics/scrum)
-- [*Agile Development with Scrum*](http://www.amazon.com/Agile-Software-Development-Scrum-Series/dp/0130676349)
+- [*Agile Development with Scrum*](http://www.amazon.com/Agile-Software-Development-Scrum-Series/dp/0130676349)
+- [Handling technical stories](http://lizkeogh.com/2008/09/10/feature-injection-and-handling-technical-stories/)
diff --git a/scrum.md b/scrum.md
@@ -32,5 +32,7 @@ Some of its fundamental goals include:
 
 
 #### More reading:
+- [Splitting stories into tasks – when, why and how (or not)](http://lizkeogh.com/2011/08/23/splitting-stories-into-tasks-when-why-and-how-or-not/)
+- [Splitting Up Stories](http://lizkeogh.com/2008/09/11/splitting-up-stories/)
 - [MountainGoat Software's Scrum Guide](http://www.mountaingoatsoftware.com/topics/scrum)
 - [*Agile Development with Scrum*](http://www.amazon.com/Agile-Software-Development-Scrum-Series/dp/0130676349)
diff --git a/scrum.md b/scrum.md
@@ -18,7 +18,7 @@ Some of its fundamental goals include:
 
 #### SCRUM definitions:
 
-- **user story** - A [user story](http://en.wikipedia.org/wiki/User_story) describes functionality of a system that will be valuable to a Non Development Team (NDT) stakeholder of a system or software (eg. "As a user, I want to login"). 
+- **user story** - A [user story](http://en.wikipedia.org/wiki/User_story) describes functionality of a system that will be valuable to a Non Development Team (NDT) stakeholder of a system or software (eg. "As a user, I want to login"). A user story should have business value, be testable, and be small enough to complete in one iteration.
 - **story point** - A story point is an relative estimation unit used by Scrum teams. This is used to measure the complexity of implementing a story. Points have several advantages over estimating tasks using time -- for one, estimating development tasks is *really* hard! Using the story point abstraction takes the focus off of the actual time in hours or days and instead puts the focus on describing the relative expense and complexity of a task as compared to other tasks. Humans/developers are better at that.
 - **product backlog** - An never-ending list of all product requirements
 - **product owner** - prioritizes backlog

diff --git a/scrum.md b/scrum.md
@@ -18,9 +18,8 @@ Some of its fundamental goals include:
 
 #### SCRUM definitions:
 
-- **user story** - A [user story](http://en.wikipedia.org/wiki/User_story) describes functionality of a system that will be valuable to a Non Development Team (NDT) stakeholder of a system or software (eg. "As a user, I want to login"). Should be as abstract and non-technical as possible while still representing an interation of work and allowing you to assign points to it. It's OK to split a card into smaller cards so you can assign points to it
-- **story point** - A story point is a arbitrary measure used by Scrum teams. This is used to measure the effort required to implement a story.
-Points have many advantages over estimating tasks with actual time -- for one, estimating development tasks is *really* hard! Using the story point abstraction takes the focus off of the actual time in hours or days and instead puts the focus on describing the relative expense and complexity of a task as compared to other tasks. Humans/developers are better at that.
+- **user story** - A [user story](http://en.wikipedia.org/wiki/User_story) describes functionality of a system that will be valuable to a Non Development Team (NDT) stakeholder of a system or software (eg. "As a user, I want to login"). 
+- **story point** - A story point is an relative estimation unit used by Scrum teams. This is used to measure the complexity of implementing a story. Points have several advantages over estimating tasks using time -- for one, estimating development tasks is *really* hard! Using the story point abstraction takes the focus off of the actual time in hours or days and instead puts the focus on describing the relative expense and complexity of a task as compared to other tasks. Humans/developers are better at that.
 - **product backlog** - An never-ending list of all product requirements
 - **product owner** - prioritizes backlog
 - **sprint planning** - meeting to decide sprint goal and sprint backlog

diff --git a/scrum.md b/scrum.md
@@ -18,7 +18,7 @@ Some of its fundamental goals include:
 
 #### SCRUM definitions:
 
-- **user story** - A user story describes functionality of a system that will be valuable to a Non Development Team (NDT) stakeholder of a system or software (eg. "User can login"). Should be as abstract and non-technical as possible while still allowing you to assign points to it. If you need to it's OK to split a card into smaller cards (technical if need be) so you can assign points to it
+- **user story** - A [user story](http://en.wikipedia.org/wiki/User_story) describes functionality of a system that will be valuable to a Non Development Team (NDT) stakeholder of a system or software (eg. "As a user, I want to login"). Should be as abstract and non-technical as possible while still representing an interation of work and allowing you to assign points to it. It's OK to split a card into smaller cards so you can assign points to it
 - **story point** - A story point is a arbitrary measure used by Scrum teams. This is used to measure the effort required to implement a story.
 Points have many advantages over estimating tasks with actual time -- for one, estimating development tasks is *really* hard! Using the story point abstraction takes the focus off of the actual time in hours or days and instead puts the focus on describing the relative expense and complexity of a task as compared to other tasks. Humans/developers are better at that.
 - **product backlog** - An never-ending list of all product requirements

diff --git a/scrum.md b/scrum.md
@@ -1,6 +1,6 @@
 # Agile Software Development
 
-[Agile](http://agilemanifesto.org) is a general philosophy describing a set of guiding principles for building software through iterative development. Agile development is really about providing a framework that allows developers to build something useful for real world users and deal with the realities of interruptions, timelines, and technical requirements that disrupt an ideal development cycle. In other words, Agile development helps developers deal with reality.
+[Agile](http://agilemanifesto.org) is a general philosophy describing a set of guiding principles for building software through iterative development. Agile development is about providing a framework that allows developers to build something useful for real world users and deal with the realities of interruptions, timelines, and technical requirements that disrupt an ideal development cycle. In other words, Agile development helps developers deal with reality.
 
 SCRUM is a methodology -- in another words, an implementation -- pertaining specifically to project management. Other "Agile" methodologies inclue extreme programming, kanban.
 
@@ -19,6 +19,8 @@ Some of its fundamental goals include:
 #### SCRUM definitions:
 
 - **user story** - A user story describes functionality of a system that will be valuable to a Non Development Team (NDT) stakeholder of a system or software (eg. "User can login"). Should be as abstract and non-technical as possible while still allowing you to assign points to it. If you need to it's OK to split a card into smaller cards (technical if need be) so you can assign points to it
+- **story point** - A story point is a arbitrary measure used by Scrum teams. This is used to measure the effort required to implement a story.
+Points have many advantages over estimating tasks with actual time -- for one, estimating development tasks is *really* hard! Using the story point abstraction takes the focus off of the actual time in hours or days and instead puts the focus on describing the relative expense and complexity of a task as compared to other tasks. Humans/developers are better at that.
 - **product backlog** - An never-ending list of all product requirements
 - **product owner** - prioritizes backlog
 - **sprint planning** - meeting to decide sprint goal and sprint backlog

diff --git a/scrum.md b/scrum.md
@@ -1,12 +1,12 @@
 # Agile Software Development
 
-[Agile](http://agilemanifesto.org) is a general philosophy describing a set of guiding principles for building software through iterative development. SCRUM is a methodology -- in another words, an implementation -- pertaining specifically to project management. Other methodologies inclue extreme programming, kanban.
+[Agile](http://agilemanifesto.org) is a general philosophy describing a set of guiding principles for building software through iterative development. Agile development is really about providing a framework that allows developers to build something useful for real world users and deal with the realities of interruptions, timelines, and technical requirements that disrupt an ideal development cycle. In other words, Agile development helps developers deal with reality.
+
+SCRUM is a methodology -- in another words, an implementation -- pertaining specifically to project management. Other "Agile" methodologies inclue extreme programming, kanban.
 
 ### SCRUM history:
 Scrum was a term first used in 1987 to describe hyper-productive product development in Japan. The word Scrum comes from rugby, where scrum refers to the strategy used for getting an out-of-play ball back into play. The name Scrum stuck because of the similarities between the game of rugby and the type of product development proscribed by Scrum -- both are adaptive, quick, and self-organizing.
 
-Agile development is really about providing a framework that allows developers to build something useful for real world users and deal with the realities of interruptions, timelines, and technical requirements that disrupt an ideal development cycle. In other words, Agile development helps developers deal with reality.
-
 Some of its fundamental goals include:
 
 - self-organization

diff --git a/scrum.md b/scrum.md
@@ -18,7 +18,7 @@ Some of its fundamental goals include:
 
 #### SCRUM definitions:
 
-- **user story** - A user story describes functionality of a system that will be valuable to a Non Development Team (NDT) stakeholder of a system or software. Should be as abstract and non-technical as possible while still allowing you to assign points to it. If you need to it's OK to split a card into smaller cards (technical if need be) so you can assign points to it
+- **user story** - A user story describes functionality of a system that will be valuable to a Non Development Team (NDT) stakeholder of a system or software (eg. "User can login"). Should be as abstract and non-technical as possible while still allowing you to assign points to it. If you need to it's OK to split a card into smaller cards (technical if need be) so you can assign points to it
 - **product backlog** - An never-ending list of all product requirements
 - **product owner** - prioritizes backlog
 - **sprint planning** - meeting to decide sprint goal and sprint backlog

diff --git a/scrum.md b/scrum.md
@@ -18,7 +18,7 @@ Some of its fundamental goals include:
 
 #### SCRUM definitions:
 
-- **user story** - A user story describes functionality of a system that will be valuable to a Non Development Team (NDT) stakeholder of a system or software. Should be the as non-technical and high-level as possible while still allowing you to assign points to it. If you need to it's OK to split a card into smaller cards (technical if need be) so you can assign points to it
+- **user story** - A user story describes functionality of a system that will be valuable to a Non Development Team (NDT) stakeholder of a system or software. Should be as abstract and non-technical as possible while still allowing you to assign points to it. If you need to it's OK to split a card into smaller cards (technical if need be) so you can assign points to it
 - **product backlog** - An never-ending list of all product requirements
 - **product owner** - prioritizes backlog
 - **sprint planning** - meeting to decide sprint goal and sprint backlog

diff --git a/scrum.md b/scrum.md
@@ -18,7 +18,7 @@ Some of its fundamental goals include:
 
 #### SCRUM definitions:
 
-- **user story** - A user story describes functionality of a system that will be valuable to a Non Development Team (NDT) stakeholder of a system or software
+- **user story** - A user story describes functionality of a system that will be valuable to a Non Development Team (NDT) stakeholder of a system or software. Should be the as non-technical and high-level as possible while still allowing you to assign points to it. If you need to it's OK to split a card into smaller cards (technical if need be) so you can assign points to it
 - **product backlog** - An never-ending list of all product requirements
 - **product owner** - prioritizes backlog
 - **sprint planning** - meeting to decide sprint goal and sprint backlog

diff --git a/scrum.md b/scrum.md
@@ -0,0 +1,35 @@
+# Agile Software Development
+
+[Agile](http://agilemanifesto.org) is a general philosophy describing a set of guiding principles for building software through iterative development. SCRUM is a methodology -- in another words, an implementation -- pertaining specifically to project management. Other methodologies inclue extreme programming, kanban.
+
+### SCRUM history:
+Scrum was a term first used in 1987 to describe hyper-productive product development in Japan. The word Scrum comes from rugby, where scrum refers to the strategy used for getting an out-of-play ball back into play. The name Scrum stuck because of the similarities between the game of rugby and the type of product development proscribed by Scrum -- both are adaptive, quick, and self-organizing.
+
+Agile development is really about providing a framework that allows developers to build something useful for real world users and deal with the realities of interruptions, timelines, and technical requirements that disrupt an ideal development cycle. In other words, Agile development helps developers deal with reality.
+
+Some of its fundamental goals include:
+
+- self-organization
+- minimize meetings
+- prevent interruptions
+- incremental product delivery
+- visibility
+
+
+#### SCRUM definitions:
+
+- **user story** - A user story describes functionality of a system that will be valuable to a Non Development Team (NDT) stakeholder of a system or software
+- **product backlog** - An never-ending list of all product requirements
+- **product owner** - prioritizes backlog
+- **sprint planning** - meeting to decide sprint goal and sprint backlog
+- **sprint** - an iteration of defined length (eg. 30 days, 1 week) where scrum teams work through a sprint backlog undisturbed by new requirements
+- **sprint goal** - a high-level, non-technical description of what is to be accomplished in a sprint
+- **sprint backlog** - the list of tasks needed to achieve the. sprint goal. is updated as items are completed. serves as a highly visible, real-time picture of the work the team plans on accomplishing during the sprint
+- **daily scrum ("standup")** - 15 minute status meeting where each scrum team member shares 1) what they've accomplished since the last meeting 2) what they plan on accomplishing by the next meeting 3) any obstacles in their way. Topics requiring follow-up are deferred to after the standup so they don't take up everyone's time.
+- **sprint review meeting** - a check-in to review progress up to that point and decide whether to keep it or throw it away
+- **sprint retrospective** - A brief, dedicated period at the end of each sprint to deliberately reflect on how they are doing and to find ways to improve, eg. what should we start doing? what should we stop doing? what should we continue doing?
+
+
+#### More reading:
+- [MountainGoat Software's Scrum Guide](http://www.mountaingoatsoftware.com/topics/scrum)
+- [*Agile Development with Scrum*](http://www.amazon.com/Agile-Software-Development-Scrum-Series/dp/0130676349)