Status
colour Yellow title DRAFT

...

We want our stories to be assessed against I-N-V-E-S-T criteria for quality:

•  Independent (of all others)
•  Negotiableegotiable (not a specific contract for features)
•  Valuable (producing value for the product owner, or is providing incremental vertical improvements)
•  Estimatiblestimatible (to a good approximation)
•  Small  Testablemall (so as to fit within an iteration)
•  Testable (in principle, even if there isn't a test for it yet)

see https://www.agilealliance.org/glossary/invest/ & https://www.scrumalliance.org/community/articles/2014/january/the-invest-scale for more info

Planning Poker

1. The ScrumMaster presents the top item in the product backlog to the team.

2. The team discusses what the story is.

3. The product owner clarifies questions, assumptions, and unknowns—as well as acceptance criteria.

4. Each team member privately decides how big this story is relative to a reference story, a series of reference stories, or all of the stories on the product backlog.

5. At the count of three, everyone shows his or her chosen "card" simultaneously (story point value).

...

This is an example sprint schedule in 2 week iterations 

[we will need to groom the backlog as part of the first sprint planning to kick this off]

• SPRINT PLANNING 1 + 2 (Wed)
• STANDUPs will occur Tues + Thurs (15m)
• BACKLOG GROOMING meeting the second Mon (before the sprint end)
• PRODUCT DEMO at sprint end, includes stakeholders
• RETROSPECTIVE at sprint end
  
  

...

Resources

• Agile Manifesto Principles: http://agilemanifesto.org/principles.html
• High level explanation of Agile/Scrum terminology: http://www.mitchlacey.com/intro-to-agile/scrum
• MSDN Application Lifecycle Management whitepapers:
  1. Estimating  http://msdn.microsoft.com/en-us/library/hh765979.aspx
  2. Prioritization http://msdn.microsoft.com/en-us/library/hh765981.aspx