The document outlines the essentials of utilizing Scrum as a project management methodology, highlighting its iterative and incremental approach suitable for software development. It emphasizes using best practices and adapting Scrum principles for varying project sizes, particularly for small teams. Key concepts include roles, meetings, and definitions like the Definition of Done (DoD), along with useful project management tools.

1. Scrum
Essentials
SK
Twitter @krishdpi

2. @Krishdpi
Why Scrum?
A simple project management methodology.
Wikipedia defines as:
Iterative and incremental agile software development
methodology for managing product development.
Scrum can be used for any type of project management.
Ex: Product Marketing

3. @Krishdpi
How best to use Scrum?
Simple answer: Sparingly!
Use the best practices.
Follow common, simple scrum methodology.
For majority of projects there is no need to stick to Scrum book.
Very useful for small teams: 2-20 people.
A good intro here: Link

4. @Krishdpi
Vocabulary
Role
• Scrum Master
• Product Owner
• Team Member
Meetings
• Sprint Planning meeting
• Scrum meeting
• Demo
• BugFest
Ticket
• EPIC
• Story
Ticket Status
• Backlog
• Accepted/In-Progress
• Test/Done
• Completed/Invalid

5. @Krishdpi
DoD – Definition of Done
When a ticket is closed, that ticket is
developed, tested and deployed.
Bugs become another story.
Any new feature obviously a story.

6. @Krishdpi
Sprint
Planning
Meeting
Sprint
Scrum Meeting
Demo
Iterate
Sprint Activities

7. @Krishdpi
Sprint 1 Sprint 2 Sprint 3 Sprint 4
MLP
Strategic
Features
Field
Reqs
Customer
Reqs
MVP
Bugs,
Backlog
Rel ver 1.0
BugFest BugFest
Release Activities

8. @Krishdpi
Useful tools?
Assembla (www.assembla.com)
Pivotal Tracker (www.pivotaltracker.com)
Jira (https://www.atlassian.com/software/jira/)