1. What is Agile?
Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change

2. What is Scrum?
SCRUM is one of many Agile process frameworks that allows us to focus on delivering the highest business value in the shortest time.
It allows us to rapidly and repeatedly inspect actual working software (every two weeks to one month).
The business sets the priorities. Teams self-organize to determine the best way to deliver the highest priority features.
Every two weeks to a month anyone can see real working software and decide to release it as is or continue to enhance it for another sprint.

4. Scrum framework Roles Ceremonies Artifacts Product owner ScrumMaster
Team
Roles
Sprint planning
Sprint review
Sprint retrospective
Daily scrum meeting
Ceremonies
Product backlog
Sprint backlog
Burndown charts
Artifacts

5. Roles Product Owner Scrum Master Team
Defines the features of the product, decides on release data and content
Is responsible for the profitability of the product (ROI)
Prioritizes features according to market value
Can change features and priority every 30 days
Accepts or rejects work results
Scrum Master
Ensures that the team is fully functional and productive
Enables close cooperation across all roles and functions and removes barriers
Shields the team from external interferences
Ensure that the process is followed: Invites to daily scrum, iteration review and planning meetings
Team
Cross-functional, seven plus/minus two members
Selects the iteration goal and specifies work results
Has to the right to do everything within the boundaries of the project guidelines to reach the iteration goal
Organizes itself and its work
Demos work results to the Product Owner

6. Ceremonies Sprint Planning Sprint Review Sprint Retrospective
Team selects items from the product backlog they can commit to completing
Sprint backlog is created
High-level design is considered
Sprint Review
Team presents what it accomplished during the sprint
Typically takes the form of a demo of new features or underlying architecture
Informal
Whole team participates
Invite the world
Sprint Retrospective
Periodically take a look at what is and is not working
Typically 15–30 minutes
Done after every sprint
Daily Scrum Meeting
Daily 15 minute meetings
Not for problem solving
Whole world is invited
Only team members, ScrumMaster, product owner, can talk
Everyone answers three questions (What did I do yesterday, What will I do today, Is anything in my way)
These are not status meetings for the ScrumMaster, they are commitments to your peers

7. Artifacts Product Backlog The requirements
A list of all desired work on the project
Ideally expressed such that each item has value to the users or customers of the product
Prioritized by the product owner
Reprioritized at the start of each sprint
Sprint Backlog
Created during sprint planning meeting and is the list of stories identified by the team for the Sprint
Typically the list contains the tasks associated with each story and hours or points to complete the task
List is updated daily by the team to reflect what has been completed
Burndown Charts
Estimated work remaining in the sprint is calculated and graphed by the ScrumMaster
Used to manage Sprint goal

8. Differences between Scrum and current Waterfall method
Product Centric; you won’t hear the word project
Product Owner leads by conveying the vision and represents the stakeholders
Product Backlog is full or enhancement requests and defects; some of which may never be addressed
No project manager; Dev Team plans their own work and plans can change every sprint
Scrum Master is responsible for team following the process (not responsible for planning or acquiring resources)
Sprints result in work that is “Potentially Shippable Software”

9. Scrum in real life Need premise buy-in: Product owner is critical
Some things sooner better than everything later
90% accurate in 1 month better than 100% in 3
Product owner is critical
Resource intense
“Refactoring” part of the process
Reporting entirely different
Get developers involved in stories early

10. Jira/Greenhopper

12. Discussion Points Resourcing product lines and managing capacity
Who takes on the role of product manager and manages customer expectations
How do you know whether to use waterfall or agile?
Project selection vs product management
Taking on different roles – no more project managers, self-managed teams, where does the scrum master come from?

13. References