<commit_before># Backlog

The Product Owner is responsible for creating a list of things he/she wants done, called a backlog.  They have exclusive rights to prioritize this backlog of work.

---

# Sprint Planning Meeting

* timeboxed to 4 hrs
* this meeting is a _conversation_ between the Product Owner and the team.
* the team has the power to push back and voice concerns or impediments.
* definition of 'done'

---

> At this point, the Product Owner is typically asked to leave while the team decomposes the sprint backlog items into tasks.

---

> While the Product Owner is asked to leave so that the team can candidly discuss the work, he or she is still expected to be “on call” to answer questions

---

#Story Pointing

---

The general characteristics of story points include:

* Story points represent the total amount of work required to fully implement a user story.
* The stories are estimated independently by team members and the team drives toward a consensus opinion.

---

* If a user story is too large to be implemented in one iteration it needs to be broken down into two or more smaller stories.
* Many of the estimating models are designed as games that are interesting and engaging for the project team.

---

#Lets Do It!

###Tools
* Trello
* Google Hangout Video<commit_msg>cleaned up Day1-Part3, added Pivotal Tracker as a possibility for story pointing<commit_after># Agile Howto

---

# Backlog

The Product Owner is responsible for creating a list of things he/she wants done, called a backlog.  They have exclusive rights to prioritize this backlog of work.

---

# Sprint Planning Meeting

* Timeboxed to 4 hrs
* This meeting is a _conversation_ between the Product Owner and the team
* The team has the power to push back and voice concerns or impediments
* Definition of 'done'

---

## At this point, the Product Owner is typically asked to leave while the team decomposes the sprint backlog items into tasks

---

## While the Product Owner is asked to leave so that the team can candidly discuss the work, he or she is still expected to be “on call” to answer questions

---

# Story Pointing
###The general characteristics of story points include:

* Story points represent the total amount of work required to fully implement a user story
* The stories are estimated independently by team members and the team drives toward a consensus opinion

---

# Story Pointing (cont)

* If a user story is too large to be implemented in one iteration it needs to be broken down into two or more smaller stories
* Many of the estimating models are designed as games that are interesting and engaging for the project team

---

#Lets Do It!

###Tools
* Trello
* Google Hangout Video
* (Pivotal Tracker)
{'fraction_non_alphanumeric': 0.047932674716428834, 'fraction_numerical': 0.0014635931211123307, 'mean_word_length': 3.813380281690141, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6257894', 'n_tokens_mistral': 696, 'n_tokens_neox': 674, 'n_words': 429}