Scrum plus – why scrum is not enough for successful delivery
Download as PPTX, PDF•1 like•407 views
The document discusses the limitations of the Scrum framework and advocates for integrating additional engineering practices like TDD, BDD, and DevOps to enhance delivery success. It emphasizes collaboration, addressing common issues like ambiguous requirements and ineffective metrics, and suggests evolving Scrum into a more comprehensive agile approach. It also promotes continuous learning through workshops and practical experiences in Agile methodologies.
Scrum plus – why scrum is not enough for successful delivery
- 1. ScrumPlus – Why Scrum is not enough for successful delivery? NAVEEN KUMAR SINGH P 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 )
- 2. 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
- 4. “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
- 6. Scrum Values Openness Transparency of our results, problems, strengths, development needs helps us create a culture of openness Commitment As we have greater control over what we do and how we do, we become more committed for success Focus As we focus only on few things at a time, we work well together and produce excellent work, we deliver value sooner Respect As we work together, sharing success and failure, we respect each other, our agreements and commitments Courage As we work together and feel supported, we are courageous to be open and challenge ourselves to go beyond our capabilities.
- 8. 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
- 9. Collective Ownership of Delivery Engineering Practices like TDD, BDD, Pair Programming, CI/CD, Agile Testing and DevOps etc.
- 10. Processes Vs Values Business Failure Useless Stuff Business Success Technical Debts Technical Practices Building it Right Building Right Things
- 11. 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
- 12. Behavior Driven Development Gherkin Given “James” want to upload new prescription When “James” selected “DoctorVisit.jpeg” And Click on “Record” prescription Then Prescription should get saved with success message And Prescription should be available on search page Feature Scenario Scenario Outline Examples Given When Then And But Background
- 13. 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 & Manual Manual Automated Tools SupportingTheTeam CritiqueProduct Business Facing Technology Facing
- 14. Agile Testing Pyramid Automated UI Test Automated API Test Automated Service Test Automated Component Test Automated Unit Test Exploratory Test 70% 20% 10%
- 15. Test Driven Development Write Test Write CodeRefactor Code Objective • Help to stay focus • Safer refactoring • Fewer bugs • Emergent • Cleaner code
- 16. 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
- 17. 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/
- 18. DevOps - Collaboration Between Dev & OPS
- 19. DevOps – Amplifying Feedback Loop
- 20. Continuous Integration • Get early feedback about your change • Keep your code always clean • Work on mainline • Continuous Code Review
- 21. 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
- 22. What Next? Learn XP Learn DevOps Improve Quality More… Learn Professiona l Scrum from Scrum.Org Learn TDD, BDD, CI/CD, DevOps and Agile Testing Join Agile 30 meetup in your City
- 23. 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)
- 24. 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
- 25. THANK YOU! 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