This document provides an overview of Agile project management processes. It defines Agile as an iterative process that values frequent inspection and adaptation, teamwork, self-organization, accountability, and rapid delivery of high-quality software that is aligned with customer needs. Scrum is described as an Agile software development method that uses sprints, product backlogs, and roles like Scrum Master and Product Owner. The document outlines the sprint planning process and different types of backlogs used in Agile. It also discusses retrospective meetings held after each sprint to inspect and improve methods and teamwork.

1. ARE YOU AGILE?

2. What is Agile?

3. What is it really?
 PROJECT MANAGEMENT PROCESS
 Frequent Inspection
 Adapt or Die
 LEADERSHIP PHILOSOPHY
 Teamwork!!
 Self-organization
 Accountability
 SET OF ENGINEERING BEST PRACTICES
 Rapid delivery of high quality software
 BUSINESS APPROACH
 Alignment of development with customer needs and company goals

4. The difference between “old” and “new”…
WATERFALL AGILE

5. How To SCRUM
 SCRUM is an iterative process of development used with agile software
development.
 The roles in Scrum are the ScrumMaster, the Product Owner and the Team.
 During each sprint the team creates an increment of viable product. The set of
features that go into each sprint come from the product backlog. Which
backlog items go into the sprint is determined during the sprint planning
meeting.
 The team then determines how much of this they can commit to complete
during the next sprint. During the sprint, no one is able to change the sprint
backlog.

6. WHO IS PART OF THE TEAM?

7. The People
 THE AGILE TEAM
 Tech Archs -> Server peeps
 Developers (Front and Back)
 Analysts
 Designers
 Tech Writers
 QA, Testers
 Product Owners / Customer Representatives / Account Managers
 Project Managers / SCRUM Masters

8. SPRINT PLANNING!!!

9. A sprint is only a smaller piece of a
marathon…
 Beginning of iteration
 Review vision and roadmap
 Review development status, architecture and previous iterations
 Determine velocity
 Review team availability & capacity
 Review definition of done
 Review product backlog & select items for iteration / sprint
 Identify tasks & estimates
 Identify challenges & risks
 Review capacity required
 COMMIT (planning not over until entire team commits to sprint plan)

10. What is a Backlog?
 A Product Backlog is the master list of all functionality for the product
 Features
 Epics
 Bugs
 The Sprint Backlog is the list of functionality that the team is committing that they
will complete in the current iteration
 Stories
 Requirements
 Bugs

11. RETROSPECTIVE
 Meeting after an increment of work to inspect and adapt their methods and
teamwork
 What went well
 What could be improved
 Team learning
 Catalyst for change
 Generate action
 This is done after the Sprint REVIEW; where every feature that has been
complete is presented to the greater team