Loading presentation...

Present Remotely

Send the link below via email or IM


Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.


Scrum 101 (Version 1.0)

Agile Project Management

Sarah Chun

on 19 July 2014

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Scrum 101 (Version 1.0)

Sarah Chun
Agile Project Management
is a
group activity designed to produce
product, service or result.
Project management
is the application of knowledge, skills and
techniques to execute projects effectively and efficiently.
What is
? Able to move quickly and easily. Characterized by
quickness, lightness, and ease of movement.
What is Agile Project Management?
What is
Agile Project Management
Agile Approach
How is Agile different?
How this came about?
Agile Manifesto (Statement of Values)
What is Scrum?
Scrum Framework
Scrum Team and their Roles
Scrum Events
Scrum Artifacts
Agile project management is an
approach to planning and guiding project processes.
Agile project management focuses on continuous improvement, scope flexibility, team input, and delivering essential quality products.
Agile Approach
Traditional Method: Linear (Waterfall) Approach
Project Initiation
Req't Analysis
Acceptance Testing
Project Closure
Easily controlled, especially for large complex groups
Process standardization
Up-front detailed design and thorough requirements analysis and review reduce the risk of missing a key element of the solution
Benefits of Linear Method
Client doesn't always know what they want up-front
Communication issue (too rely on documentation, no useful feedback mechanism)
Huge effort during the planning phase
Disadvantages of Linear Method
Source: http://www.dummies.com/how-to/content/agile-project-management-for-dummies-cheat-sheet.html
Agile Approach
Agile Manifesto
Scrum Framework
Individuals and interactions
over processes and tools
Working software
over comprehensive documentation
Customer collaboration
over contract negotiation
Responding to change
over following a plan
(Statement of Values)
"We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:"
How is Agile Approach different?
"That is, while there is a value in the items on the right, we value the items on the left more."
Starts with a vague idea and
what we choose to build gradually emerges as we iterate the process.

In software development, we build a prototype that would validate the rough idea. Then review to see if it would meet the requirements. We adjust and make changes iteratively until its good enough.

We iterate to find the right solution!
Incremental means increasing gradually by regular degrees or additions.
"Building a little at a time"
In software development, we gradually build up and incrementally adding more functionality and release what we've incrementally built so far.
Until people start using the software we are building, there is no really return on investment and not adding any business value.
Month 1
Month 2
Month 3
Reference: Kevin Aguano: http://agilepm.com/
Jeff Patton http://www.stickyminds.com/s.asp?F=S13178_COL_2
Jeff Patton http://www.stickyminds.com/s.asp?F=S13178_COL_2
How is Agile Approach different?
How this came about?
In 2001, 17 software developers met to discuss whether there was a common, underlying basis for their work in the 1990s around what
had been referred to as “light-weight processes.” None of them liked
the term “light-weight”, feeling it was a reaction against something, instead of something to stand for.
Keeping code simple - Testing often - Delivering functional bits of
the application as soon as they're ready
Extreme Programming (XP)
Dynamic Systems Development Method (DSDM)
Feature-Driven Development
Adaptive Software Development
Pragmatic Programming
.. and more
Agile Approach
What is Scrum?
What does "Scrum" mean?
"Scrum" is a term used in rugby, when the forwards
from each side bind with their teammates and
crash head-on into their opponents, to gain possession
of the ball that's rolled between them.
Iterative and incremental agile software development framework
for managing software projects and product or application development.
Focus on a flexible, holistic product development strategy where a
development team works as a unit to reach a common goal
as opposed to a "traditional, sequential waterfall approach".
Focus on delivering the highest business value in the shortest time
using many short deliveries (1 to 4 weeks)
Business sets priorities.
The team self-organizes to determine the best way to deliver the highest priorities.
Consists of the following:
Scrum team and their roles
Scrum Framework
Scrum team
and their roles
A Product Owner
A Scrum Master
The Development Team
Product Owner
Has the vision for the project
Ensuring the value of the work the Development Team performs
Gathers input from end-users, customers, team and other stakeholders
Responsible for prioritizing the
Product Backlog
as needed

Scrum Master
Responsible for the Scrum process, making sure it's used correctly & maximizes it benefits.
Clearly communicating vision, goals, and Product Backlog items to the Development Team.
Facilitates the
Daily Scrum Meetings
and becomes responsible for removing any obstacles (
) that are brought up by the team during those meetings.
Protects the team by making sure they do not over-commit themselves to what they can achieve during a
The Development Team
group of people responsible for managing itself to develop the product.
Teams are
; organize and manage their own work.
Everyone on the project
works together
to complete the set of work they have collectively committed to complete within a Sprint. Accountability belongs to the Development Team as a whole.
Membership should only change between sprints, not during.
Scrum Framework
Scrum team and
Product Owner (accountable, verifier)
Scrum Master (responsible)
Development Team (responsible)
Committed to:
Adhering to the Scrum Process
Collaboration to get work done
"having their bacon on the line"
Business Owner (accountable)
End-users, Customers
Consulting Experts
Everyone else who is involved, engaged
consulted and interested in the project.
Scrum Framework

Sprint (Iteration)
Planning Meeting
Daily Scrums / Standups
Sprint (Iteration)
Review Meeting
Sprint (Iteration)
Scrum Framework
Sprint (Iteration) Planning Meeting
Evaluation of the
Product Backlog
Select a Sprint(Iteration) Goal
Plan how to achieve the
Sprint Goal
Sprint(Iteration) Backlog
tasks from prioritized Product Backlog items
Sprint Backlog tasks in hours
Image: http://uni4.com.br/blog/2011/scrum-sprint-planning-meeting/
Scrum Meeting
(Daily Standup)
Release: working
of Software
Sprint (Iteration) Review Meeting
Presentation of accomplishments from the Sprint
Typical format is demonstration of the new features by the Development team
Informal meeting – 2hrs preparation maximum
Whole team participates
Open invitation
Image reference http://comm-press.de/en/blog/code-sprint-turned-support-sprint-review-views-sprint
Sprint (Iteration) Retrospective
Follows every Sprint
Team participation (Chickens not generally invited)
What worked well?
What didn’t work well?

What can we improve upon for next time?
Image reference http://www.planetgeek.ch/2011/01/27/presentation-scrum-at-bbv-software-services-ag/
Product Backlog
Sprint (Iteration) Backlog
Sprint (Iteration) Burndown Chart
Team board
Artifacts represent work or value in various ways that are useful in providing transparency of key information needed to ensure the Scrum Team is successful in delivering working increment of software.
Pigs = Scrum team!
Scrum roles are often referred to as Chickens and Pigs.
Meeting starts on time
Chickens are welcome, but only Pigs may speak
All attendees should stand
During the meeting, each team member answers three questions:
What have you done since yesterday?
What are you planning to do by tomorrow?
Do you have any problems preventing you from accomplishing your goal?
NOT a status update to the Scrum Master
(1-4 weeks)
A time-box of 1 month or less during which a “Done”, useable, and potentially releasable product
is created by the development team.
During the Sprint:
No changes are made that would affect the Sprint Goal;
No changes to the Development team members;
Quality goals do not decrease; and,
Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned.
(iteration) contains and consists of the Sprint
Daily Scrums
the development work
, the Sprint
Meeting, and the Sprint
Product Backlog
A master list of high level requirements prioritized by the Product Owner.
A living document which is maintained and posted visibly.
When a project is initiated there is no comprehensive, time-consuming effort to write down all foreseeable tasks.
The Product Backlog evolves as the product and the environment in which it will be used evolves.
The Product Backlog is dynamic; it constantly changes to identify what the product needs to be appropriate, competitive, and useful.
Re-prioritized at the start of each Sprint.

Sprint (Iteration) Backlog
A list of tasks to be completed during the Sprint.
This list is determined in the Iteration/Sprint Planning meeting.
Any team member can add, delete or change the Sprint Backlog.
If work is unclear, define a Sprint Backlog with a larger amount of time, then break it down later.
Team is self organizing - team members sign up for tasks, tasks aren’t assigned.
Each task identifies who is responsible for doing the work and the estimated amount of work remaining on the task on any given day during the Sprint.

Sprint (Iteration) Burndown Chart
A burn down chart is a graphical representation of work left to do versus time.
Daily progress for a Sprint over the sprint's length.

Team / Task Board
Not technically a Scrum artifact but its critical.
It allows the team to be transparent with its progress. It creates a focal point for the team.

Development work
in progress...
Full transcript