ScrumPlus – Why Scrum is not enough for successful delivery?

NAVEEN KUMAR SINGHP R O F E S S I O N A L S C R U M T R A I N E R ( P S T )

NAVEEN KUMAR SINGH

Software Development Coach

Facilitate Scrum.Org (PSM, PSD) and Scrum Alliance (CSD) Training

Teaching and coaching teams on agile and Technical Practices in India, Sri Lanka,

Malaysia, Singapore, Indonesia, Hong Kong, Saudi Arabia, Dubai and Philippines.

Strength – Knowledge about Scrum, Kanban and Scaling Agile (LeSS, Nexus,

Spotify). Hands-on TDD, BDD, CI/CD, DevOps, Emergent Design and Agile

Testing Automation

Weakness – Don’t go by book and don’t like prescriptive frameworks

Agile Approach

“A framework within which people can address

complex and adaptive problems while productively

and creatively delivering products of the highest

possible value”

What is Scrum?

Jeff Sutherland Ken Schwaber

Scrum Framework

Scrum.Org

Scrum Values

OpennessTransparency of our results, problems, strengths, development needs helps us create a culture of openness

CommitmentAs we have greater control over what we do and how we do, we become more committed for success

FocusAs we focus only on few things at a time, we work well together and produce excellent work, we deliver value sooner

RespectAs we work together, sharing success and failure, we respect each other, our agreements and commitments

CourageAs we work together and feel supported, we are courageous to be open and challenge ourselves to go beyond our capabilities.

Collaboration Benefits

But……

• Still we see waterfall in scrum• Developer struggles to meet deadline • BDUF eat most of time so producing poor code• Poor metrics kills developers at the end• Testers don't get enough time to test• Testers busy in logging new defects but not in

closing• Scope changes within Sprint• Requirement is ambiguous• Whole team suffers on the name of agile

Collective Ownership of Delivery

Engineering Practices like TDD, BDD, Pair Programming, CI/CD, Agile Testing and DevOps etc.

Processes Vs Values

Business Failure

Useless Stuff

Business Success

Technical Debts

Technical Practices

Building it Right

Building Right Things

Behavior Driven Development

• Remove ambiguity from requirement• Test First Approach /Executable Specification• Test Automation • Living Documents• Bonus – Splitting complex feature in smaller deliverables

Collaboration between Product Owner and Development Team

Behavior Driven Development

Gherkin

Given “James” want to upload new prescriptionWhen “James” selected “DoctorVisit.jpeg”And Click on “Record” prescriptionThen Prescription should get saved with success messageAnd Prescription should be available on search page

FeatureScenarioScenario OutlineExamplesGivenWhenThenAnd ButBackground

Testing Quadrant

Functional Tests

Story Tests

Prototypes

Simulations

Exploratory Tests

Usability Tests

User Acceptance

Tests (UAT)

Performance Testing

Load Testing

Security testing

NFR Testing

Unit Tests

Component Tests

Integration Tests

Automated

& ManualManual

Automated Tools

Su

pport

ing T

he T

eam C

ritiqu

e P

rodu

ct

Business Facing

Technology Facing

Agile Testing Pyramid

Automated

UI Test

Automated API Test

Automated Service Test

Automated Component Test

Automated Unit Test

Exploratory

Test

70%

20%

10%

Test Driven Development

Write Test

Write CodeRefactor Code

Objective

• Help to stay focus

• Safer refactoring• Fewer bugs• Emergent • Cleaner code

Unit Test vs TDD

• Is writing code first is also TDD?

• What are key differences between Code First Vs Test First?

• When we write code before test?

• How to write TDD for legacy code?

• When Write Test First then how to ensure we have enough test?

• What is Right-BICEP

• B – Boundary Condition• I – Inverse Check• C – Cross Check• E – Error Condition• P – Performance Check

Pair Programming

Objective

• Shared understanding

• Collective code ownership

• Continuous Review and Feedback

• Faster Learning

Source - https://developer.atlassian.com/blog/2015/05/try-pair-programming/

DevOps - Collaboration Between Dev & OPS

DevOps – Amplifying Feedback Loop

Continuous Integration

• Get early feedback about your change

• Keep your code always clean

• Work on mainline

• Continuous Code Review

Continuous Parallel Testing

• Is it possible? Really? How?• What about building

framework using tools like Cucumber and Selenium

• How about testers add scenarios in parallel to coding?

• How about developer and tester pair continuously?

• How about avoiding defect logging as long as possible?

• How about not to start working on new PBI without closing previous one

What Next?

Learn XP Learn DevOps Improve Quality

More…

Learn Professional Scrum from Scrum.Org Learn TDD, BDD, CI/CD,

DevOps and Agile Testing

Join Agile 30 meetup in your City

Scrum Workshops by Scrum.Org

Professional Scrum Foundation (PSF)

Professional Scrum Developer (PSD)

Professional Scrum Master (PSM)

professional Scrum product Owner (PSPO)

Scaled Professional Scrum (SPS)

Agile Technical Workshops

Test Driven Development (TDD) Practitioner

Behavior Driven Development (BDD) Practitioner

Professional Agile Tester

Professional DevOps Consultant

Professional Lean Kanban Consultant

Extreme Programming (XP) Practitioner

T H A N K Y O U !n a v e e n @ a g i l e m a n i a . c o m

+ 9 1 9 8 1 0 5 4 7 5 0 0

@ n a v e e n h o m e