Agile can be either Scrum or KanBan

Scrum:

1. Built from the perspective of the end user.

2. Features User Storys:  User storys describe what the user wants.
	All the user stories are in the Product Backlog
	Product Backlog is the Users Wish list... 
	
	So - the Product backlog lists all the User Stories.
	
3. Product owner choses which stories are in the Prodcuct baclklog. 

4. scrum master Monitors and facilitates (he is the project manager).

5. Release backlog - this is the estimate of the duraton of developement of each story - estimate teh story points. 

6. Release backlog gets broken up into Sprints
	Sprints are prioritized user stories
	Estimates for the work - duration..
	
Now you plan the sprint with short term milestones

7. Burndown - Productivity Measure - update work completed every day.

8.  Scrum meetings keep everyone updated.

Product backlog => release Backlog => Sprints.

============================================================================

Agile:

The Board:   To Do - In Progress - Done..  They can be more complex with more columns.. 
Organized as:  Scrum or KanBan

Scrum has sprints: A predetermined amount of time where thteams determine what wil lbe dine in the sprint, say 2 weeks.  And every 2 weeks is the meeting.  WHat we discuss:
	1. What went well inthe last sprint, and what did not?
	2. What are the priorities over the next two weeks - the next sprint..?
	3. Drag stuff from left to right, and have few things "In Progress".

Kanban:  Projects are ongoing and added to the board anytime.

Agile terms:

User stories:  As a . I want  for 
Thisi s how developers berak up their work. 

Epics:
Too big for a story.  Its much bigger,and will be broken down into multiple user stories. 

Issues and Projects
Issues have fields which hold all your data.  Issues are containers for fields
Projects are containers for Issues.