Check out this brief introduction of Scrum, the Agile Software Development Framework. This is just a high level introduction that is why there are only 10 slides. Please like and share if you find it useful.

1. Scrum
An Agile Software Development Framework
A Brief Introduction
Waqas Akram

2. Agile Methods Require An Iterative Approach Whereas Non-Agile
Methods Advocate A Step-by-step Approach
Non-Agile
Agile
A collaborative approach
where a team works on all
phases of the project
right from the start
A project is broken down
into feature lists (user
stories). For each user
story, tasks are defined
and assigned that are
completed in a fixed block
of time
At the end of each block,
teams share their output
(working software) with
the customer. The
feedback (change) is
incorporated in the next
block of time
Assumption
Requirements
Requirements
Design
Code
Test
Customer requirements
will be changed
significantly throughout
the project lifecycle
Vs
Design
Code
Test
A sequential process
where a project goes
through different phases
step by step just like a
“Waterfall”
As a result a lot of time is
spent in the requirements
and design phase. All
milestones, deadlines,
outputs etc. are decided
before the coding
It is very costly to
implement change
because it may require rework of design and coding
Customer requirements
will NOT be changed
significantly throughout
the project lifecycle
2

3. Agile Projects Are 3 Times More Successful Than Non-Agile Projects
Successful – A completed project that has achieved the set milestones
Challenged – An incomplete project that is facing problems due to any reason
Failed – A challenged project that has been shelved or stopped
Source: The CHAOS Manifesto (2012), The Standish Group
3

4. Agile Methods Stress on Adaptability and Frequent Customer
Collaboration
According to Agile Manifesto, followers of Agile value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Which means
Responding to change over following a plan
That is, while there is value in the items on
the right, we value the items on the left more.
• Self-organization and motivation of team is important
• Teams must interact more often e.g. pair programming
• In the meetings, present a working software to the clients
rather than the documents
• Regularly interact with customer because requirements can be
changed throughout the software development lifecycle
• The essence of Agile development is to quickly respond to the
change
Source: www.agilemanifesto.org
4

5. Scrum Is The Most Widely Used Agile Methodology
There are many Agile methods in practice today. According to an annual survey, with 4,048 respondents from
Software development communities, Scrum is the most widely used Agile Technology
Source: 7th Annual State of Agile Development Survey (2013), Versionone.com
5

6. Scrum Is Easy To Understand But Difficult To Master
User Story
Product
User Story
User Story
1. Product Owner is the voice of the
3. Product Owner plans and starts the development phase known as Sprint
customer who writes the Product
features that are known as
User Stories.
which has a fixed time duration of 2-4 weeks. During this phase
Development Team completes the tasks that are part of Sprint Backlog
4. During Sprint, there is a Stand up meeting every day in which everyone
2. These user stories are then
prioritized and added to the Product
Backlog
Roles
Artifacts
Events
Source: The Scrum Guide, Scrum.org
answers 3 questions; i) What they did yesterday? ii) What they will today?
iii) Is there anything stopping them?
5. At the end of the Sprint, there is a Sprint Review Meeting in which
completed work is presented. Non-completed work is added to the Sprint
Backlog
6. A Scrum Master overlooks the whole process and enforces the Scrum
rules and regulations
6

7. Scrum Has Well Defined Roles And Events
Roles
Scrum Master
• Facilitates Scrum
• Removes impediments
• Chairs key meetings
Event
Sprint Planning Meeting
Events
Daily Scrum Meeting
(Stand Up)
Sprint Review Meeting
Sprint Retrospective
Source: The Scrum Guide, Scrum.org
Product Owner
• Responsible for the
outcome of the project
• Manages the Product
Backlog
Development Team
• Responsible for delivering the
product at the end of each
Sprint
• Self-organizing and crossfunctional team of 3-9
individuals
Activities
Duration
• Select the work to be done
• Agree on Sprint Backlog
8 hours limit
• Everyone answers 3 questions
a) What have you done since yesterday?
b) What are you planning to do today?
c) Any impediment?
15 minutes
• Review the work that has been completed
• Present the completed work
4 hours limit
• Scrum Master facilitates this meeting
• Two questions are asked
a) What went well during the Sprint?
b) How can we make next Sprint better?
3 hours limit
7

8. Velocity and Burn Down Chart Provide Useful Information For
Sprint Planning
Performance of the team can be tracked through a Burn Down Chart. It also shows the capability of the
Development Team. This capability is called “Velocity”. The Velocity in past Sprint is used to estimate the
amount of work that the team is expected to deliver in future Sprints.
8

9. VersionOne, JIRA And LeanKit Are The Most Recommended Agile Tools
Personal Recommendation
Source: 7th Annual State of Agile Development Survey (2013), Versionone.com
9

10. Useful Learning Resources
www.Scrumalliance.org
www.Scrum.org
www.agilemanifesto.org
http://www.infoq.com/minibooks/scrum-xp-from-the-trenches (Free eBook)
10