Practical Scrum Workshop by SEO Rescue. A Practical hands on approach to training. please contact Shaf Cangil on linkedin or www.seorescuenow.co.uk to book a training session.

1. Shaf Cangil

2. Testimonials:
Testimonials
Stuart McLaughlin
The Brittons Academy Essex
"Shaf Cangil came as a consultant to The
Brittons Academy from SEO Rescue when we
desperately needed someone to organise our
Year 11 students to finish off their coursework
for their ICT qualification.
She applied her management system [SCRUM]
to identify each students individual first class
support.
Her technique enabled staff to map and
monitor every student's work against the
specification and then direct them
to what was needed to complete the
course.
Thanks to her support,
a significant number have achieved
a pass or merit on the full course."
Three years coursework sorted and
completed in 15 days.
www.seorescuenow.co.uk
@shafattack
uk.linkedin.com/in/scangil

3. Introducing Practical Scrum
• You should be in teams of 4 or so.
• Get into a circle facing each other.
• One person holds a pen.
• Only the pen holder can talk.
• Introduce yourself (name)
• give your current occupation or skills.
• Pass the pen to someone new.
• That was a scrum meeting practice!
Image courtesy of Rugby Union Scrum Oval Retro by vectorolie at FreeDigitalPhotos.net
Image courtesy of Standing 3d People by David Castillo Dominici at FreeDigitalPhotos.net

4. Introducing Scrum
• You will have exposure to scrum as
we go…
• Work flexibly
• Merge existing and developing skills
on the fly
• Produce a ‘Minimal Viable Product’
of increasing complexity over time
• (Through ‘iterations’)

5. In your groups take 5 minutes to discuss:
What makes a really good team?
• Flexibility
• Dedication
• Compromise
• Speed
• Exchange of ideas without fear
• Good time keeping
• Self-organising
• Open to new ideas/training

6. Open your pack.
• Take 5 minutes to look over the contents.

7. Mnemonic:
I
Am
Doing
Dangerous
Teaching
Everywhere
BAD: Waterfall (Systems Life Cycle)
Problem: Timeframe was over months so original desire
for product died or project overran or end product no
longer fit for purpose etc..
1 year LONG to finished product!

8. Solution:
• Reduce time of the ‘cycle’
• Bi Weekly (With micro
cycles within that!)
• Builds flexibility
• Still same goal in mind
• Allows for adaptation and
emergent benefits
• Take away a finished
product quicker
• Allows for better decisions
(eg: to end the project or
drastic change after each
sprint).
http://www.creative-format.com/processes
Sprint
Iteration

9. GOOD: ‘SPRINTS!!!’
• Smaller Cycles than Waterfall cycles.
• Break down sprints further into iterations!
• Natural SCALEABILITY/FLEXIBILITY
• Get a MINIMAL VIABLE PRODUCT to sell
AFTER THE FIRST SPRINT! (2 weeks).
• Doesn’t RELY ON PROPRIETARY SOFTWARE!
• TEAMS INPUT COUNT OVER PLANS!
(Emergent logic).
2 weeks:
finished
product
2 weeks:
finished
product
2 weeks:
finished
product
2 weeks:
finished
product
Sprints!

10. GOOD: SPRINTS!!!
RULES OF AGILE/SCRUM
1. Individuals and interactions over processes and
tools [DONT RELY ON PROPRIETARY SOFTWARE!]
2. Working software over comprehensive
documentation [TEAMS INPUT COUNT OVER
PLANS!]
3. Customer collaboration over contract
negotiation [BUILD IN SCALEABILITY/FLEXIBILITY]
4. Responding to change over following a
plan[EMERGENT BEHAVIOURS]
• AGILE MANIFESTO.

11. DO NOW:
The project stages: Artefact (ceremonies) Who?
What's the Big plan? Product backlog Product Owner
Pull out a portion to make
in 30 minutes.
Sprint backlog (Sprint
planning)
Team decides (the
discussion about length
and complexity of tasks)
Write down your goals on
post it notes.
User stories and
acceptance criteria (daily
scrum)
Team decides (Team ticks
off stuff done and stuff to
do and what’s stopping
them) Scrummaster sorts.
When done and validated,
move it to done and tick
off of burndown chart.
Burndown chart Team checks off
After 3 cycles, show and
tell by team to everyone.
5 minutes team identifies
best practices.
Sprint review and
retrospective.
Team presents to Product
owner or stakeholders
and then TEAM discusses
how to improve practice.

12. The Daily Universe Newspaper
(No affiliation to The Daily Planet).
What's the Big plan?
Take 5 minutes to pull out a portion to make in 30 minutes.
Write each single little task on a post it note.
Leave on the table
ANYONE CAN DO ANY TASK- DON’T DECIDE WHO DOES WHAT YET!

13. Scrum Meeting
• Get into a circle facing each other.
• One person holds a pen.
• Only the pen holder can talk.
• What have you done so far?
• Suggest a post it note that you might complete.
• Take it to the TO DO column.
• What might be a problem for you?
• Who will help solve that? (Scrummaster)
• Pass the pen to someone new.
• [Repeat]
• (all post it notes must end up on the board TO DO).
• NB: ANYONE MAY TAKE ANY TASK (Flexibility)
• May work in twos.Image courtesy of Business People Talking by Ambro at FreeDigitalPhotos.net"

14. Acceptance criteria /User stories.
Image courtesy of Colorful Paper Notes On Wood Texture by KROMKRATHOG at FreeDigitalPhotos.net

15. Start Your ‘Iteration’.
• Usually 1 day
• 10 days = 1 Sprint
• ALWAYS have daily scrum meeting (15 mins) before iteration
• Do not usually add post it notes. Just at beginning.
• The aim’s to GET AS MANY POST IT NOTES done.
• This time it’s 30 mins to Complete an Iteration.
• Start now.
"Image courtesy of A Male Athlete Ready To Run The Race by stockimagesat FreeDigitalPhotos.net"

16. No specialist software.

17. No specialist software.
• When you have one task
finished. Hands up.
• I will assess
• (Continuous Integration
Whitebox testing)
• You get paid.
• Move task to DONE
• Update Burndown chart.
• You don’t have to finish all post
it notes in one iteration.
• You do for one sprint..

18. FIRST ITERATION DONE.
• Normally 1 iteration == 1 day.
• 10 days == 10 daily scrum meetings
& daily iterations/loops of work

19. Take a break to think about your work…
Then back to Slide 11…
• Expand your existing product
further…
Image courtesy of 3d Man Running Inside Recycle Sign by David Castillo Dominici at FreeDigitalPhotos.net

20. Finished the last Iteration…
• FIRST SPRINT DONE!
• What team has the most
money?
• What does that tell us?
• Take a few minutes to
congratulate yourselves…
• What did you do?
• How did SCRUM help?
• Benefits and limitations?
Image courtesy of Excellent Tick Represents Fineness Excelling And Confirmed by Stuart Miles at FreeDigitalPhotos.net
Image courtesy of Young Male With Thumbs Up by imagerymajestic at FreeDigitalPhotos.net

21. Sprint review and retrospective.
(Show and tell).
• Did you make a Minimal Viable Product?
• Explain to the audience.
• ---------------------------------------------------
• Take 5 minutes to discuss procedures with
your team and how you all might improve.
Image courtesy of Business Training by jscreationzs at FreeDigitalPhotos.net

22. RECAP
• Scrum ceremonies (italics):
• Scrum Artefacts: (BOLD)
• Team ownership (Sharing ideas)
• Iterations (Repeating processes)
• Continuous integration (Testing)
• Systems life cycle/Waterfall
The project stages: Artefact (ceremonies)
What's the Big plan? Product backlog
Pull out a portion to make
in 30 minutes.
Sprint backlog (Sprint
planning)
Write down your goals on
post it notes.
User stories and
acceptance criteria (daily
scrum)
When done and validated,
move it to done and tick
off of burndown chart.
Burndown chart
After 3 cycles, show and
tell by team to everyone.
5 minutes team identifies
best practices.
Sprint review and
retrospective.

23. How did you find the experience
of ‘Practical Scrum?’
Many thanks for participating:
The books are available on
Amazon and the winners today
are:
Look out for The ‘Scrummasters
Guide to Sanity’ Coming soon!
(Limited editions)
• Hope you enjoyed the experience!
• If not, tell us, if so…
• Tell your friends!
• SEO RESCUE
• Shaf Cangil
• www.seorescuenow.co.uk
• @shafattack
• contactus@seorescuenow.co.uk
• uk.linkedin.com/in/scangil