[UNDER CONSTRUCTION]

Notes from Essential Scrum: A Practical Guide to the Most Popular Agile Process.

Create a product backlog, “a prioritized list of features and other capablities needed to develop a successful product.” Work on highest-priority items first. “When you run out of resources (such as time)”, any items left in the priority queue will (obviously) be of lower priority than those items which have been completed.

Work is usually performed in week- or month-long iterations by a cross-functional team (designing, building, testing). At the start of each iteration, teams select a high-priority subset from the product backlog. At the end of an iteration, a potentially shippable/releasable increment of the product should be ready. The the team reviews completed features with stakeholders and requests feedback. Based on feedback, the product owner and team modifies the product backlog accordingly.

Scrum is appropriate for complex domains (e.g., innovative new-product development).

Some domains where scrum is likely inappropriate: complicated domains (e.g., performance optimization), simple domains (e.g., reproducing same product repeatedly), chaotic domains (e.g., product algorithm is producing erroneous results), disorder (e.g., when no one knows what domain you are in), or interrupt-driven work (e.g., managing customer support activities).

####Scrum Framework Practices #####Roles (in each Scrum team) - Product owner - ScrumMaster - Development team

#####Activities - Sprint - Sprint planning - Daily scrum - Sprint execution - Sprint review - Sprint retrospective - Product backlog grooming

#####Artifacts - Product backlog - Sprint backlog - Potentially shippable product increment

#####Rules