Scrum isn’t just what you use in the Rugby game  In today’s fast-paced, competitive world, if you are using Scrum at work, business and life, you are more likely to succeed! Learn the principles, practices and techniques in Scrum. Understand the roles and responsibilities, and know how to apply the popular daily Scrum stand-ups, sprint planning, reviews and retrospectives. Learn from the leaders, what makes Scrum the most-sought after agile methodology in big organisations as well as startups! Texavi's Tech Bootcamp will equip you to be job-ready with practical and real-time insights, as well as offering access to our treasure of insightful, high-quality resources and materials. Whether you are a developer or a tester, architect, analyst or a sales person thinking about going agile, the Tech Bootcamp is for you. Check out the presentation for details.

2. 2www.texavi.co.uk
Welcome to Texavi!

3. 3
First thingsfirst!
www.texavi.co.uk
• This is a freecourse, but rememberthereis no freelunch!
• Its completely developed and delivered by Texavi. No sponsors, help us with youractive participation and support!
Texavi, Analyst-Zone, AZcircle, NewAgeAgile Business Analyst* are registered trademarks of Texavi
Texavi,Analyst-Zone,AZcircle,NewAgeAgileBusiness Analyst*areregisteredtrademarksof TexaviInnovative Solutions

4. 4
Please remember!
www.texavi.co.uk
• Attend all sessions without fail. Theyareinter-related, so you can get the best only if youattend eachone of them
• Full attendance will open avenues for you! Eg., prepare youfor that BA job interview, certificates, premiumaccess
to ourdigital platform, mobile app,discount vouchers to our online coursesand manymore…
• Do thetasks, exercises and home works. It’s a good investment for you!
Find us, follow us on all popular social/professional media platforms:
YouTube, Facebook, Instagram, Twitter, LinkedIn & coming soon on WhatsApp

5. 5
Agenda
 Scrum -What,why, when,where…
 Core principles of Scrum
 Scrum roles & responsibilities
 Key features& practicesin Scrum
 Sprint, thespiritof Scrum!
 Scrum ceremonies & activities
 Key artefactsanddeliverables
 Techniques& tools used in Scrum
 Scaling of Scrum
 Summary -Q & A

6. 6
RELEASE
All about Scrum

7. 7
www.texavi.co.uk
Agenda
 Overview andsettingthecontext
 Definitions of agile
 Waterfallvs agilemethods
 Sources & forces of change
 Why to go agile-Benefits & value
 Evolution of agile methodologies
 Stakeholders in agiledevelopment
 Traceabilityin agiledevelopment
 Methods & techniques in agile
 Summary -Q & A

8. www.texavi.co.ukwww.texavi.co.uk 8
Hey…let’s go agile!

9. 9
Agenda
 Overview andsettingthecontext
 TheAgile Manifesto
 Thethreepillars of agile
 Core agileprinciples & concepts
 Engaging keystakeholders in agile
 PDCA and theagiletoolkit
 Time-boxing & planningin agile
 Definition of Done & Definition of Ready
 Softwaretestingin agile
 Summary -Q & A

10. 10

11. 11
Agenda
 Scrum -What, why, when,where
 Core principles of Scrum
 Scrum roles & responsibilities
 Key features& practicesin Scrum
 Sprint, thespiritof Scrum!
 Scrum ceremonies & activities
 Key artefactsanddeliverables
 Techniques& tools used in Scrum
 Scaling of Scrum
 Summary -Q & A

12. 12
Let’s get into a Scrum

13. 13
So,what really is Scrum
A strategy in thegame of Rugby for getting anout-of-play ball back into play

14. 14
So,what really is Scrum
Scrumis an agile methodology
Iterative
Incremental
• Iterativeapproach
• Work together as a whole team
• Focus onbusiness priorities
• Timebox short sprints and releases
• Incrementaldevelopment of the product

15. 15
Difference between agile and Scrum

16. 16
Agile methods and Scrum

17. 17
Agile Scrum
Simple and quick to implement An agile methodology and follows
the fundamental agile principles
Flexible, nimble and suitable for
most types of work
Flexible, but comes with own set of
practices and processes
Difference between agile and Scrum
Agile
Framew
ork
Define
Develop
Release
Evaluate

18. 18
Why Scrum – Benefitsand value-add
• Product is broken down into smaller chunks  manageable
• All of theteam understand everything  improved communication
• Project delivered to customers early/ontime  feedback on operational
effectiveness of the product
• Requirements which are not clear do not hold up the progress of the project
• Collaborative development by customers and developers trust
• A positive environment  Project gets completed successfully
Scrumworks wonders with teams, customers, users! Win/Win!

19. 19
Whendid Scrum start
Early 1990s:
• Ken Schwaber uses Scrum-like approach at Advanced Dev Methods
• Jeff Sutherland develops similar approach at Easel Corp.
1995:
• Schwaber andSutherland present Scrum at OOPSLA95
2002:
• Ken Schwaber andMike Beedle publish Agile SoftwareDevelopment with Scrum
• Schwaber founds the Scrum Alliance
2009:
• Schwaber departs Scrum Alliance andfounds Scrum.Org
• Sutherland founds Scrum Foundation

20. 20
Where can youuse Scrum

21. 21
Agenda
 Scrum -What,why, where…
 Core principles of Scrum
 Scrum roles & responsibilities
 Key features& practicesin Scrum
 Sprint, thespiritof Scrum!
 Scrum ceremonies & activities
 Key artefactsanddeliverables
 Techniques& tools used in Scrum
 Scaling of Scrum
 Summary -Q & A

22. 22
Scrum principles
RELEAS
E

23. 23
Agenda
 Scrum -What,why, where…
 Core principles of Scrum
 Scrum roles & responsibilities
 Key features& practicesin Scrum
 Sprint, thespiritof Scrum!
 Scrum ceremonies & activities
 Key artefactsanddeliverables
 Techniques& tools used in Scrum
 Scaling of Scrum
 Summary -Q & A

24. 24
Scrum roles
RELEAS
E

25. 25
Product Owner (PO)
Provides the roadmap for the product, refines the backlog, identifies and prioritises
features
• Helps team with clarifications, reviews the product, participates in sprint reviews and showcases
• Scopes and prioritises the product roadmap

26. 26
Scrum Master (SM)
Facilitator who enables and provides services to the team
• Facilitates meetings, assists the Product Owner in refining backlogs, and removes the obstacles and
impediments of team
• Ensuresthat the team implements Scrum methodology
**Doesn’t exercise authority over team

27. 27
Scrum DevelopmentTeam (SDT)
Estimatecomplexityand sizeofwork
Determinetechnical designandarchitecture
Committoworkto accomplishaniteration
Implementand testthefunctionality
Deployfunctionality to productionandstaging
Supportautomationtobuild continuous pipelinefor delivery
Improvetheprocessescontinuously
Team estimate, commit, implement, test &deploy product!

28. 28
Agenda
 Scrum -What,why, where…
 Core principles of Scrum
 Roles & responsibilities
 Key features & practices
 Sprint, thespiritof Scrum!
 Scrum ceremonies & activities
 Key artefacts& workproducts
 Techniques& tools used in Scrum
 Scaling of Scrum
 Summary -Q & A

29. 29
Scrum delivers!
Worktogether as a team
• Focus onbusiness priorities
• Timebox short sprints and releases
• Improvethe development environment
• Reduce organisational overheads
• Ensureiterative deliverables match customer/user requirements

30. 30
Scrum delivers!

31. 31
Agenda
 Scrum -What,why, where…
 Core principles of Scrum
 Roles & responsibilities
 Key features& practices
 Sprint, the spirit of Scrum!
 Scrum ceremonies & activities
 Key artefactsanddeliverables
 Techniques& tools used in Scrum
 Scaling of Scrum
 Summary -Q & A

32. 32
Sprint is the spirit of Scrum!
Scrumprojects take an incremental approach, makingprogress in a series of iterations
called ‘sprints’
• Typical duration of a sprint is 2-4weeks
• Regularityof their duration gives the process a ‘rhythm’that makesit easier to plan and
manage
RELEAS
E

33. 33
33
Sprint
Planning
Sprint Execution
Sprint
Review
Sprint Review
Acceptance sign-off
Sprint Retrospective
Weekly Showcase
Sprint Planning Meeting

34. 34
Agenda
 Scrum -What,why, where…
 Core principles of Scrum
 Roles & responsibilities
 Key features& practices
 Sprint, thespiritof Scrum!
 Scrum ceremonies & activities
 Key artefactsanddeliverables
 Techniques& tools used in Scrum
 Scaling of Scrum
 Summary -Q & A

35. 35
Scrum ceremonies and activities
RELEAS
E

36. 36
15minutes stand-up (respective locations)
• Participants: ScrumTeam and ScrumMaster
Scrum meeting(aka dailystand-up)
Everyoneupdates on:
• What did I do yesterday
• What am I doing today
• Blockers, issues, impediments if any?

37. 37
INPUTS
> Duringsprintnochangein scope/duration
>PO -RegularupdateinPB
>BA- AdditionalUSCready
>IdentificationofUATteam
OUTPUTS
> ReleasePlan- PO
> UpdatedProduct Backlog - PO
> UserStoryCard- BA
ACTIVITIES
UserStoryFamiliarisation
TaskBreakdown/Estimation/Allocation
SprintBacklog
SprintBacklog–Dev.Team>
SprintBacklogSign-off– PO >
BurndownChart– SM >
UATTeamList– PO >
ENABLERS
BA:BusinessAnalyst
PB:ProductBacklog
PM:ProjectManager
PO:ProductOwner
SM: Scrum Master
TA:TechnicalArchitect
UAT:UserAcceptanceTesting
USC:UserStoryCard
> HighLevelDesign- TA
Sprint Planning

38. 38
INPUTS
> Duringsprintnochangein scope/duration
>PO – Feedbackonweeklyshowcase
>Majorchangessuggested- listedin PB
OUTPUTS
> SBupdates– DevTeam
> UI(HTML/CSS)– Web Team
> UserStoryCard- BA
ACTIVITIES
LowLevelDesign
ScriptingSystem& IntegrationTestCases
UserStory- Coding& UnitTesting
SITTestCases– Testers>
UnitTestedSourceCode– Developers>
TrackedBurnDownChart– SM >
USCfornextsprint-BA >
ENABLERS
BA:BusinessAnalyst
PB:ProductBacklog
PO:ProductOwner
SB:SprintBacklog
SIT:System& Integration Testing
SM: Scrum Master
UI:UserInterface
USC:UserStoryCard
Sprint Execution

39. 39
Sprint Review
INPUTS
>Duringsprintnochange inscope/duration
>Devteamtointegratepreviousbuild
andconductregressiontesting
>PO &end userstoperformUAT
>Scrumteamtofixissues/add toPB
OUTPUTS
>SITTestCases- Testers
>UnitTestedSourceCode - Developers
>BuilddeploymentforUAT – ACSTech Team
ACTIVITIES
CodeIntegration
SIT/Rework SprintReview(Demo)
FinalBuild - DevTeam>
Potentiallydemonstrableproduct -DevTeam>
>Sprintsign-off- PO/PM>
ENABLERS
BA:BusinessAnalyst
PB:ProductBacklog
PM:ProjectManager
PO:ProductOwner
SIT:System& Integration Testing
SM: Scrum Master
UAT:UserAcceptanceTesting
USC:UserStoryCard
>Insights- DevTeam/PO/SM
SprintRetrospectiveUAT

40. 40
Sprint Retrospective
1-2hours of discussion
• Participants: ScrumTeam and ScrumMaster
Discuss the following:
• What went well inthe sprint
• What did not go well in the sprint
• Areas of improvement, anynewactions from the next sprint

41. 41
Agenda
 Scrum -What,why, where…
 Core principles of Scrum
 Roles & responsibilities
 Key features& practices
 Sprint, thespiritof Scrum!
 Scrum ceremonies & activities
 Key artefacts & work products
 Techniques& tools used in Scrum
 Scaling of Scrum
 Summary -Q & A

42. 42
Key artefacts, deliverablesand work products
RELEAS
E

43. Case Study: Our eCommerce Web site sellingMobile accessories
Sprint
Beta launch
Sprint Sprint Sprint Sprint Sprint Sprint Sprint Sprint Sprint Sprint
Incremental releases
Start of development
Sprint
Project end???
Naah
…
R1 (Initial) R2 (minor) R3 (minor) R4* (MAJOR)

44. 44
Agenda
 Scrum -What,why, where…
 Core principles of Scrum
 Roles & responsibilities
 Key features& practices
 Sprint, thespiritof Scrum!
 Scrum ceremonies & activities
 Key artefacts & work products
 Techniques& tools used in Scrum
 Scaling of Scrum
 Summary -Q & A

45. 45

46. 46
Product Backlog

47. 47
User Stories

48. 48
Definitionof Done
Code complete
Code reviewed
Unit tests written and executed
Integration tested
Documented
No P1 or P2 defects

49. 49
Sprint Burndown Chart
TotalHoursofWorkLefttoDo
Initial
Estimate
Day 1 Day 2
35
40
45
50
55
60
5
10
15
20
25
30
65
70
75
0
Day 3 … Day n

50. 50
Agenda
 Scrum -What,why, where…
 Core principles of Scrum
 Roles & responsibilities
 Key features& practices
 Sprint, thespiritof Scrum!
 Scrum ceremonies & activities
 Key artefacts& workproducts
 Techniques & tools in Scrum
 Scaling of Scrum
 Summary -Q & A

51. 51
Continuous Development  Continuous Integration  Continuous Delivery

52. 52
Product Backlog ReleaseBacklog SprintBacklog

53. 53
Epic  stories  Tasks  Sub-tasks

54. 54
MoSCoW

55. 55
PlanningPoker , Tee-shirt sizing

56. 56
Team board (aka Kanban board)

57. 57
BDD Acceptance Test Cases

58. 58
Agenda
 Scrum -What,why, where…
 Core principles of Scrum
 Roles & responsibilities
 Key features& practices
 Sprint, thespiritof Scrum!
 Scrum ceremonies & activities
 Key artefacts& workproducts
 Techniques& tools in Scrum
 Scalingof Scrum
 Summary -Q & A

59. 59
Practical team size for Scrum
Scrumworks best with team size between 7 and 10
Scaling = Implementation of Scrumwheremultiple Scrumteams [collaboratively] build
a product/set of features in one ormore Sprints
Scrumdoes not scale well with…
• Largerteams
• Largelydiverse cross-discipline teams
• Compliance regime projects

60. 60
Scalingof Scrum
• Scaling Scrum requires a “Scrum of Scrums”aka
Nexusapproach
• Support above the teams to map and seek out
dependencies, eliminate them, and create continuous integration
• Scrumis not a typical project management methodology
• Needs support inscaling up to larger, diversified &multiple teams
• So scaling Scrumworks better with control frameworks such as:
• Scrumof Scrums
• SAFe(Scaled Agile Framework)
• DSDM (Dynamic Systems Development Model)
• Prince2/Agile

61. 61
Agenda
 Scrum -What,why, where…
 Core principles of Scrum
 Roles & responsibilities
 Key features& practices
 Sprint, thespiritof Scrum!
 Scrum ceremonies & activities
 Key artefacts& workproducts
 Techniques& tools in Scrum
 Scaling of Scrum
 Summary- Q & A

62. 62
Summary
 Scrum -What,why, where…
 Core principles of Scrum
 Roles & responsibilities
 Key features& practices
 Sprint, thespiritof Scrum!
 Scrum ceremonies & activities
 Key artefacts& workproducts
 Techniques& tools in Scrum
 Scaling of Scrum

63. Thank you!
Texavi Innovative Solutions
The new age people for new age solutions!
Consulting | Training | Solutions
Regd. Office
Texavi Innovative Solutions (UK) Ltd
36 Glebe Road
Finchley
London N3 2AX
Email: connect@texavi.co.uk
training@texavi.co.uk
connect@analyst-zone.com
Connect with Texavi
www.texavi.co.uk
https://analyst-zone.com
www.facebook.com/texavi
Twitter @pardhas
LinkedIn Texavi
Blog www.texavi.com/blog