Introductory Deck used to present Agile framework - Mostly Scrum - to graduate students at Nova Southeastern University. I was invited as a guest lecturer several times and this is the deck used.

1.
Why Scrum
Alex Kanaan
Jul 2016

2. Connect with Alex!
Click Button
For Direct Access
More about Me http://www.alexkanaan.com
Read My Blog http://www.alexkanaan.com/#latestnews
Contact Me http://www.alexkanaan.com/#contact
Follow my Tweets @AlexKanDu
Connect on LinkedIn https://www.linkedin.com/in/arkanaan
My Work on Slideshare http://www.slideshare.net/arkanaan

3. About Alex

4. About Alex
4

5. The Forest vs. The Trees
5

6. “INDIVIUALS
AND
INTERACTIONS
PROCESSES
OVER
AND
TOOLS”
“WORKING
SOFTWARE
COMPREHENSIVE
OVER
DOCUMENTATION”
“RESPONDING
TO
CHANGE
FOLLOWING
OVER
A
PLAN”
“CUSTOMER
CONTRACT
OVER
NEGOTIATION”
COLLABORATION
Layman’s Overview
The Agile Manifesto

7. Layman’s Overview
“Why Agile?!”
7
AgileW/O Agile
The right
features sooner!!

8. Gains from Scrum
10,000 Team Data
8
2x
50%
faster
Balance
Teams
250% better
Quality!
© data analytics by Rally Software https://www.rallydev.com/finally-get-real-data-about-benefits-adopting-agile?nid=6201

9. Gains from Scrum
Innovation!
9

10. Layman’s Overview
Agile Umbrella
10
SCRUM
Kanban
eXtreme Programming
LEAN

11. Characteristics of Scrum?
Teams:
– Dedicated collaborative self-organizing
– Communicate using various ceremonies
– Evolve using Inspect and Adapt
– Team wins/loses together
11
X

12. Characteristics of Scrum?
• Iterative Development
• Sustainable pace
• Servant-Leadership
• No hard-defined requirements
12

13. Characteristics of Scrum
Incremental vs. Iterative
➢ Defined Scope
➢ Fully formed
Idea delivered
one bit at a time
7/13/16 13
© Jeff Patton, all rights reserved, www.AgileProductDesign.com
➢ Vague Scope
➢ Start with a rough
version and build-
up by validating
vs.
Incremental Iterative

14. Incremental Approach
© Jeff Patton, all rights reserved, www.AgileProductDesign.com
1 2 3 4 5
• Build one bit at a time

15. Iterative Approach
© Jeff Patton, all rights reserved, www.AgileProductDesign.com
• Build a rough version,
validate it, then slowly
builds up quality
1 2 3 4 5

16. Growing Pains
Hang in There
• Usually takes between 3-5 sprints to
get a sustainable velocity
• Fail often, fail fast
• Don’t give up if you don’t get it right,
no one gets it right on the first try
• Teams have to ‘gel’ together
7/13/16 16

17. Scrum Mechanics
17

18. Scrum Machine

19. Scrum Machine
Roles
Ceremonies
Artifacts

20. 20
Product Owner

21. The Product Owner
• Product expert
• From the Business
• Represents interests of stakeholders, business
customers and users
• Responsible for value!
• He or she gets to decide which features get to
be delivered and when
• Keeps features in Product Backlog and decides
on priority sequence
• Accepts or rejects the work

22. Product Backlog
Order User Story Size
1 As a student I want class
ratings to make better class
selections
40
pts
2 As an administrator, I want
to update class ratings to
reflect latest survey
5 pts
3 As a professor, I want to
view my class ratings for
feedback
8 pts
4 As a professor, I want to
get an alert when my class
rating changes >10% for
feedback
20
pts
…. As a user, I want
something, for a benefit
xx pts
22
Product Owner
• List of Stories and epics
(requirements from the user
perspective)
• Prioritized in value order
• Owned by Product Owner
• What the team pulls from to
work, in each Sprint
Value

23. 23
Scrum Master

24. The Scrum Master
• Servant leader
• Empowers team to self-
organize
• Facilitates removal of
impediments
• Responsible for Scrum
ceremonies
• Ensures team focus and
protects team against
external disruptions
• Does not direct the
team
• Does not assign work
• Does not size or set
delivery dates
• Is not a PM
DO’S DON’TS

25. 25
Team!

26. The Team
• Cross functional team
• Self-organizing
• Delivers working code every sprint
• Sizes the work
• Plans the Sprint plans
• Commits to the Sprint plan
• Ideal size is 5-9 members – 2 pizza rule
• Fully allocated members
• Accountable
• Collaborate with each other and the Product Owner
Always includes:
Developers
Testers
Sometimes
includes:
BA’s
Architect
UX
DBA
Other tech SMEs

27. Scrum Machine
Roles
Ceremonies
Artifacts

28. 28

29. Sprint Backlog
User Story Pts Tasks Hrs Owner
As an administrator, I
want to update class
ratings to reflect latest
survey
5 Task – Design entry Screen
Task – Build entry Screen
Task - Retrieve rating value
Task – Update class table
Task – Functional test
Task – Integration test
Task – update user manual
8
6
2
6
12
8
2
Jim
John
Jen
Janet
Jack
Jessa
James
User story2 X Task a, Task b, Task c….. xx names
29
Team
• List of stories team commits to, the upcoming sprint
• Broken down to tasks that are estimated in hours
• Team self assigns tasks
• Stories = Points, Tasks = Hours
Sprint n Plan

30. Sprint Planning
30
• A ceremony at the beginning of each Sprint
• Team pulls the prioritized story on top of the
backlog
• Team decomposes this story to tasks
1. Teams pulls next prioritized story
2. Team continues to pull and decompose into
tasks, UNTIL the sprint capacity is met!
3. Team Commits to the sprint plan!
Prior to Sprint Planning, Backlog refined and
prioritized. Stories must meet Definition of Ready!

31. Daily Standup
31
• Attended by entire team
• Same time everyday
• 15 minutes MAX
• 3 Questions:
− What I did yesterday
− What I will work on today
− Any Impediments
• Not a status report
• Only team members speak
Who are they giving the updates to?

32. Sprint Review/Demo
32
• A ceremony at the end of each Sprint
1. Team demonstrates the accepted stories, potentially
shippable increment
Sprint Retrospective
• A ceremony at the end of each Sprint
1. Team identifies opportunities for improvement
2. What went well, what we need to improve

33. 33

34. Summary
• Scrum is really a mindset
• An approach to getting work done
• Quick delivery of quality products
• Responsive to change (agile, iterative)
• Respectful of the people doing the work
• Scrum is SIMPLE but its not EASY!

35. Scrum Reading List
• The Scrum Guide (from scrum.org)
– Ken Schwaber and Jeff Sutherland
• Essential Scrum
– Kenneth Rubin
• Succeeding with Agile, User Stories
Applied
– Mike Cohn
• Agile Retrospectives
– Esther Derby and Diana Larsen

36. Other Resources
Web sites
Scrum.org
www.scrumalliance.org (info, classes, events)
www.mountaingoatsoftware.com/scrum
www.controlchaos.com
South Florida Agile Association (SFAA)
Southfaa.com

37. Stay in Touch
Click Button
For Direct Access
More about Me http://www.alexkanaan.com
Read My Blog http://www.alexkanaan.com/#latestnews
Contact Me http://www.alexkanaan.com/#contact
Follow my Tweets @AlexKanDu
Connect on LinkedIn https://www.linkedin.com/in/arkanaan
My Work on Slideshare http://www.slideshare.net/arkanaan