Product Owner
Team Member

ScrumMaster - 
	* Removes barriers between development and PO so PO drives
development.
	* Improves lives of development team
	* Improve producvity anywa wya possible
	* Improve engineering practices and tools so each increment is shippable

Sprints are 30 calendar day chunks.  End of 30 days something must be
shippable

Tracer Bullet - small piece of functionality to demonstrate path for
functionality (Ref: Pragmatic Programmer)


Important distinctions: 
 * You're not controlling, you are facilitating development
 * You're not bossing - you are coaching
 * Teams are given enough autonomy to be self organizational - or that's the goal

Product Backlog is created and then priortized based on incremental
functionality AND Return on investment

Team sizes ~ 7

Sprints:
* Sprint must contain all analysis, design, coding, testing, documentation and
  represent the complete slice of the project.  No skimping!
  "Sashimi rule"
* Sprint Backlog must correspond to reality.  In order for that to work
  Developers must keep daily backlogs of current sprint.
* Unthought, didn't get to items, "harder than we thought", did not TEST items
  must be put into the sprint backlog.
* At end of sprint, the product backlog is reworked to take the sprint backlog into
  acount.

Burndown Log:
* Chart of features burned down during successive sprints

* Visibility, visbility, visibility. This whole thing doesn't work if the
  backlogs aren't clear and visible to stakeholders

Daily Scrum:
* What have I done since the last Daily Scrum?
* What am I going to do between now and the next Daily Scrum?
* What is preventing me from doing my work?

Scrum Planning Process:
* For the funders what can they expect to have changed at end of project?
* What progress will have been made by end of each sprint?
* Why is the project a viable investment?

Lay out product backlog, and plan for first sprint.  Product backlog
represents functional and non-functional requirements to deliver the vision,
prioritized and estimated.

Remember: Each sprint must be presentable in 30 days.

------------------------------------------------------------------------------

Questions:
* How do you sprint a DB design?
* How do you breakdown a sprint with huge pieces?  Conversely how do you
  ensure your sprints will be enough to reach the finish line with a set date?
* Can Scrum work for a small team of 4?  Hmmm I think so.


Resources:
http://en.wikipedia.org/wiki/Scrum_(development)
http://www.scrumalliance.org/courses/trainers
http://www.agilealliance.org

Software:
http://www.versionone.com/training.asp

This of course goes against SCRUM to a certain extent in a more formal process
Capability Maturity Model