This presentation will address the foundation and cornerstone of agile development mindset. We start with the agile manifesto, and then move on to the 3-pillars of agile, and the mantras behind the successful agile methodologies. We will study the important aspects of Definition of Done and Definition of Ready, and look at the engagement of key internal and external stakeholders as we work on the agile development mode. Also we will look at the concepts of time-boxing and software testing practices in agile development. 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.

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,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
 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

6. 6
Agenda
 Recap from the previoussession
 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

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
Waterfall vs.Agile

9. www.texavi.co.ukwww.texavi.co.uk
9
Agenda
 Overview and settingthe context
 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
Hey…let’s go agile!

11. 11

12. www.texavi.co.ukwww.texavi.co.uk
12
Agenda
 Overview andsettingthecontext
 The Agile 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

13. www.texavi.co.ukwww.texavi.co.uk 13

14. www.texavi.co.ukwww.texavi.co.uk
14
Agenda
 Overview andsettingthecontext
 TheAgile Manifesto
 The three pillarsof 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

15. 15
Empirical WoW (waysof
working)
Transparency Inspection Adaptation
Beingopen about:
Status,Progress,Problems,
why& how
Testand review:
Productsprocesses&
practices
Adjust& Accept: changes
due tounpredictability
The 3 pillars of Agile

16. 16
Agile core values

17. 17
Agile core values

18. 18
Agile core values

19. 19
Agile core values

20. 20
Agile core values

21. 21
Agile core values

22. 22
Agile core values

23. 23
Agile core values

24. 24
Agile core values

25. 25
Agile core values

26. 26
Agile core values

27. 27
Agile core values

28. 28
Agile core values

29. www.texavi.co.ukwww.texavi.co.uk
29
Agenda
 Overview andsettingthecontext
 TheAgile Manifesto
 Thethreepillars of agile
 Core agile principles & concepts
 Engaging keystakeholders in agile
 PDCA and theagiletoolkit
 Time-boxing & planningin agile
 Definition of Done & Definition of Ready
 Softwaretestingin agile
 Summary -Q & A

30. 3030
Core principles in agile methodologies

31. 3131
Core principles in agile methodologies

32. 3232
Core principles in agile methodologies

33. 3333
Core principles in agile methodologies

34. 34
Core principles in agile methodologies

35. 3535
Core principles in agile methodologies

36. 3636
Core principles in agile methodologies

37. 3737
Core principles in agile methodologies

38. 3838
Core principles in agile methodologies

39. 3939
Core principles in agile methodologies

40. 4040
Core principles in agile methodologies

41. 4141
Core principles in agile methodologies

42. 4242
Core principles in agile methodologies

43. www.texavi.co.ukwww.texavi.co.uk
43
Agenda
 Overview andsettingthecontext
 TheAgile Manifesto
 Thethreepillars of agile
 Core agileprinciples & concepts
 Engagingkey stakeholders in agile
 PDCA and theagiletoolkit
 Time-boxing & planningin agile
 Definition of Done & Definition of Ready
 Softwaretestingin agile
 Summary -Q & A

44. 44
Stakeholders

45. www.texavi.co.ukwww.texavi.co.uk
45
Agenda
 Overview andsettingthecontext
 TheAgile Manifesto
 Thethreepillars of agile
 Core agileprinciples & concepts
 Engaging keystakeholders in agile
 PDCA and the agiletoolkit
 Time-boxing & planningin agile
 Definition of Done & Definition of Ready
 Softwaretestingin agile
 Summary -Q & A

46. www.texavi.co.ukwww.texavi.co.uk 46
PDCA

47. 47
Agile Toolkit

48. 48
Agile Toolkit

49. 49
Agile Toolkit

50. 50
Agile Toolkit

51. 51
Agile Toolkit

52. 52
Agile Toolkit

53. 53
Agile Toolkit

54. 54
Agile Toolkit

55. 55
Agile Toolkit

56. 56
Agile Toolkit

57. 57
Agile Toolkit

58. www.texavi.co.ukwww.texavi.co.uk
58
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

59. 59
How planning works inAgile

60. 60
Timebox= fixed duration event which must not be extended
• InScrum, sprint is an example for timebox
– 2 to 4 weeks period fixed for a sprint
Time-boxing
• Anywork that is not completed at the end of the timebox/sprint is considered ‘notdelivered’
• Thoseitems DO NOTautomatically pass to the next sprint. Theyget back into the product backlog and re-
prioritised by Product owner.
• Sprints areof short duration, so planningand estimates are likely tohold good. Not delivering something is
perhaps not usual!

61. 61
• Product Owner refines the backlog items and prioritises
what needs to be done in the upcomingsprints
Time-boxing
• Before sprint execution, Development Teamdoes estimation
and planning
• Some items can be dropped from the sprint’s scope, if necessary

62. 62
Structuring ateam in Agile

63. 63
Structuring ateam in Agile

64. 64
Structuring ateam in Agile

65. 65
Structuring ateam in Agile

66. 66
Structuring ateam in Agile

67. 67
Structuring ateam in Agile

68. www.texavi.co.ukwww.texavi.co.uk
68
Agenda
 Overview andsettingthecontext
 TheAgile Manifesto
 Thethreepillars of agile
 Core agileprinciples & concepts
 Engaging keystakeholders in agile
 PDCA and theagiletoolkit
 Time-boxing & planningin agile
 Definitionof Done & Defn.ofReady
 Softwaretestingin agile
 Summary -Q & A

69. 69
Inagile, “Done” = Development Team completed everything
they need to do
• A feature is designed, coded, tested, integrated and
(is ready to be) delivered
• Definition of Done is agreed uponand decided before sprint execution
Definitionof Done (DoD)
Example: ‘Done’ could mean
1) Thecode has been written and tested by Development Team members
2) (1) + Thecode has passed acceptance testing (with bug fixes supplied by theDev Team)
3) (2) + Thecode has been signed-off by review/compliance team

70. 70
DoDcriteria:
• Thestory is development complete
• Testing/Quality Assurance complete
• Thestory meets and satisfies theacceptance criteria
• Regression aroundthe story is complete
• Thefeature (associated with story) is eligible to be deployed inproduction
Definitionof Done (DoD)
Thedifferent definitions will affect the estimates and thenworkin the Sprint plan
Usually the ScrumTeam works together (in Sprint Planning) to define and commit the
Definition of Done

71. 71
Readiness to be prioritised and moved into aniteration/sprint
• Not as popular as the Definition of Done but its veryuseful
Defines what a piece of workneeds to havein place before workcan start onimplementing it
Example: DoRfor a story
• Acceptancecriteria agreed
• Test cases created
• Estimates agreed
• + Wireframes (if requiredfor story) are created
Definitionof Ready (DoR)

72. 72
DoRcriteria
• Userstories haveto satisfy some conditions
• Before prioritising it for a sprint i.e., story is in the ‘ready’ state
Theconditions essential for development of story will specify…
• If story is ready to develop
or
• else groom and refineit enoughto be ‘readyto develop’
Definitionof Ready (DoR)

73. www.texavi.co.ukwww.texavi.co.uk
73
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 & Defn.of Ready
 Software testingin agile
 Summary -Q & A

74. 74
• Testing is a significant activity inSoftware Development Lifecycle(SDLC)
• Fundamentally about assessing thevalidation and verification of the
feature(s)
In essence:
• Validation = Build the rightthing
• Verification = Build things right
Software Testing

75. 75
Type of Testing Description
Functional Testing Tests the functionality that state how the product/system must perform functions
(eg.,,CRUD–create, read, update, delete)
Integration Testing Conducted toexpose defects within an interface
Non-functional Testing Testing the attributes ofa system that does not relate tofunctionality (eg., performance,
security, usability)
Quality Assurance Concerned with customer confidence andquality requirements
Differenttypes of testing

76. 76
Type of Testing Description
Adhoc Testing Informal Testing (alsoreferred toas sanity testing)
Beta Testing Testing conducted by afinite set of(off-site) end-users
Black-Box Testing Testing asystem with noreference tothe internal structure (as opposed towhite-
box testing)
Differenttypes of testing

77. 77
The V Model - V for Validation& V for Verification

78. 78
Inverted V Model

79. www.texavi.co.ukwww.texavi.co.uk
79
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 & Defn.of Ready
 Softwaretestingin agile
 Summary- Q & A

80. 80
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