This document provides an overview of Agile project management and the Scrum framework. It discusses key Agile concepts like user stories, estimation, prioritization, and sprints. It also contrasts aspects of the Scrum framework compared to traditional waterfall approaches, such as using shorter 1-2 week sprints instead of long phases, and allowing flexibility in priorities and engineering practices within each sprint. The document concludes with a section on frequently asked questions about Agile and Scrum.

2. 1. Introduction
2. Waterfall vs Agile
3. Agile - General Concepts
4. Agile - Scrum vs XP vs Lean Methods
5. Agile - Estimation & Planning
6. Agile - Best Practices
7. Top 5 Concepts
8. Q & A

3. Agile PM / SCRUM Master
•16+ years experience in IT industry
• 3 years Developer – Banking - Italy
• 6 years Developer, SW Integrator &
Test Manager – Automotive - Germany
• 4.5 years PM – Telecom – Romania
• 2.5 years Agile PM / Scrum Master –
Client Apps (web, standalone, mobile) -
IBM Romania

6. PRODUCT
Backlog
User Stories
Estimation Priority

13. REQUIREMENTS
DESIGN
DEVELOPMENT
TESTING
SUPPORT
Scrum
Master
Product
Owner
Scrum Team
Dev+Test+BA
BACKLOG /
USER STORIES
FUNCTIONALITIES
ROADMAP
PRIORITIZATION
RETROSPECTIVE
DEMO
SPRINTS
LESSONS LEARNED
FEEDBACK
Passion
Flexibility
Technology
Motivation

17.  SW Engineering vs Project Management
 1 week vs 2 weeks sprints
 Change vs No-change during the sprint
 Strict vs Flexible priority order
 Prescribed vs Free to choose engineering practices
(e.g. test-driven dev., automated testing, pair
programming, simple design, refactoring)