The document provides an introduction to the Agile SCRUM process. It explains that SCRUM aims to address disadvantages of classical software development methods like long planning phases and clients having to wait until the end to see results. SCRUM delivers working functionality in small iterations to allow for adaptation, customer involvement, and prioritized delivery of the most important requirements first. It also enables visible progress and focus through daily standup meetings, tracking user stories and tasks on a whiteboard, and using burn down charts to monitor work completion.

1. Introduction to Agile SCRUM Process

2. Agenda Why Scrum ? How Scrum works ? Scrum Meeting Whiteboard and Post-It’s Burn Down Charts

3. Why SCRUM? Classical methods of software development have many disadvantages: huge effort during the planning phase poor requirements conversion in a rapid changing environment client have to wait till end to get the feel of the product

4. Contd… How SCRUM methodology helps: Frequent deliveries of completed functionality Small iterations = easier to adapt to change Customer involvement => customer satisfaction Deliver business value - Most important requirements are done first, prioritized frequently Visible progress = predictable progress Helps focus and motivate team

5. How SCRUM works?

6. SCRUM Meetings daily standup meetings same time, same location Questions What have you done yesterday? What will you do today? Do you have any problems preventing you from accomplishing your goal? (ScrumMaster to remove impediments) not a progress report, not to be addressed to scrum master, but to inform each other

7. Whiteboard and Post-It’s User Story Tasks In progress In QA Done User story Design the… (2) Code the… (3) Code the… (5) Test the… (1) Document the… (1) … User story 2

8. Burn Down Charts

9. Thank You