Managing requirements and collaboration in Jira with BDD
•Download as PPTX, PDF•
0 likes•351 views
This document discusses managing requirements and collaboration in Jira using behavior-driven development (BDD). It outlines how BDD in Jira allows for formulation, automation, and discovery of requirements through examples mapped to scenarios. Examples of system behavior are documented using business terminology to create shared understanding. This living documentation is then automated and can be navigated. The document also discusses how Cucumber allows teams to deploy software 10 times per day through a model of independent microteams using BDD and test-driven development for 100% automated testing and a continuous integration/delivery pipeline.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Managing requirements and collaboration in Jira with BDD
Similar to Managing requirements and collaboration in Jira with BDD (20)
More from Laurent PY
More from Laurent PY (11)
Recently uploaded
Recently uploaded (20)
Managing requirements and collaboration in Jira with BDD
- 1. Managing requirements and collaboration in Jira with BDD
- 2. Proprietary & Confidential 2 Presented by Laurent Py @py_laurent VP of Products - SmartBear
- 3. Proprietary & Confidential 3 Agenda | Software Development becomes continuous | BDD in Jira | Cucumber for Jira: Deploying 10x / day | Q&A
- 4. Proprietary & Confidential 4 Software Development becomes continuous
- 5. Proprietary & Confidential 5 Race to accelerate • 3 months release cycle: Test Complete, SoapUI, RAPI, Zephyr Enterprise • 2 weeks release cycle: Zephyr for Jira, SwaggerHub • Continuous deployment: Cucumber, TM4J, CBT, LoadNinja
- 6. Proprietary & Confidential 6 Strategic goal: accelerate product cycles Why? More development done?
- 7. Proprietary & Confidential 7 Strategic goal: accelerate product cycles Ideas Build Code Measur e Data Learn Speed of learning Innovation
- 8. Proprietary & Confidential 8 Test management vanishes Test management is the process of taking your project's requirements, building a test plan, writing the tests, planning the test activities and capturing the results. In Cucumber & LoadNinja product teams we have no testers, no test plans, no manual tests
- 9. Proprietary & Confidential 9 Job to be done From assessing the release readiness to… …build, deploy and maintain the right software
- 10. Proprietary & Confidential 10 BDD in Jira
- 11. Proprietary & Confidential 11 Formulation, Automation and Discovery | The documentation is automated, creating living documentation that verifies the system’s behaviour | Examples of system behaviour are documented using business terminology | Create a shared understanding of the requirements through collaboration, typically achieved through a structured conversation centered on rules and examples
- 12. Proprietary & Confidential 12 Start with our Jira Board
- 13. Proprietary & Confidential 13 Discovery With Example Mapping
- 15. Proprietary & Confidential 15 Automation of Living documentation
- 16. Proprietary & Confidential 16 Automation of Living documentation
- 17. Proprietary & Confidential 17 Navigate the Living documentation
- 18. Proprietary & Confidential 18 Cucumber: Deploying 10x / day
- 19. Proprietary & Confidential 19 Operational model • 4 Independent micro teams, no testers • No gatekeeper between developers and production • Driven by OKR • Using BDD and TDD to drive development (100% of automation) • 5/10 deployments/day • Insight from production
- 20. Proprietary & Confidential 20 Definition of done • Acceptance tests (all automated) • Unit test • Refactoring legacy code • Implementation of the behavior • Integration tests • Exploratory testing done • Deployed in production
- 21. Proprietary & Confidential 21 Technical discipline • 235 End To End • 424 FrontEnd acceptance tests • 481 FrontEnd integration tests • 878 FrontEnd Unit tests • 5824 Backend tests
- 22. Proprietary & Confidential 22 Learning loop Discover Example Mapping Formulate BDD scenarios Automate Cucumber, Rspec… Test and deploy CI/CD Publish Living Documentation Develop TDD Build 1 2 3 4 5 6 Define in collaboration
- 23. Proprietary & Confidential 23 Resources • Kick Start and Scale Behavior Driven Development | https://cucumber.io/resources/ebooks/kick-start-and-scale-behavior-driven-development/ • BDD is not test automation | https://cucumber.io/blog/bdd/bdd-is-not-test-automation/ • Introduction to example mapping | https://cucumber.io/blog/bdd/example-mapping-introduction/ • Who writes the scenarios? | https://cucumber.io/blog/bdd/who-writes-the-cucumber-scenarios/
- 24. Proprietary & Confidential 24 24 Making something nobody want The biggest risk
Editor's Notes
- TC: Our biggest transition is release cadence from 4 months to 1 month, and QA cycle reduce from 4 weeks to 1 week -> TC and SoapUI Dev and QA teams both use Git Code review process is in place (to help catch bugs early in the cycle) Test case prioritization is done. We do not execute all tests all the time. One development team in TC writes their own tests before passing it on to QA Zephyr: Z4J SwaggerHub: biggest and fastest growing product. Agile, release end of the sprint. SwaggerHub, Cucumber Cucumber some of the tools we use: Cucumber Open, Cucumber Studio, Cucumber For Jira, SwaggerHub When you shoot every day a rocket to the moon then launch is no more a big deal, going to the moon is no more a big deal, that s an habib, part of your daily life. The only downside is that we don’t celebrate any more. No champagne.
- Know your customers, accelerate product cycles, innovate That’s also our mission in this world : We accelerate the development of high-quality, open software for people, teams, and organizations everywhere, transforming big ideas into sustainable realities.
- Example of ESP
- Example Mapping is one of the most popular methods of capturing details about a User Story under development. CucumberStudio will soon include tooling to facilitate Discovery sessions using Example Mapping.
- Example Mapping is one of the most popular methods of capturing details about a User Story under development. CucumberStudio will soon include tooling to facilitate Discovery sessions using Example Mapping.
- Example Mapping is one of the most popular methods of capturing details about a User Story under development. CucumberStudio will soon include tooling to facilitate Discovery sessions using Example Mapping.
- Example Mapping is one of the most popular methods of capturing details about a User Story under development. CucumberStudio will soon include tooling to facilitate Discovery sessions using Example Mapping.
- Example Mapping is one of the most popular methods of capturing details about a User Story under development. CucumberStudio will soon include tooling to facilitate Discovery sessions using Example Mapping.
- Example Mapping is one of the most popular methods of capturing details about a User Story under development. CucumberStudio will soon include tooling to facilitate Discovery sessions using Example Mapping.
- TC: Our biggest transition is release cadence from 4 months to 1 month, and QA cycle reduce from 4 weeks to 1 week -> TC and SoapUI Zephyr: Z4J SwaggerHub: biggest and fastest growing product. Agile, release end of the sprint. SwaggerHub, Cucumber Cucumber some of the tools we use: Cucumber Open, Cucumber Studio, Cucumber For Jira, SwaggerHub When you shoot every day a rocket to the moon then launch is no more a big deal, going to the moon is no more a big deal, that s an habib, part of your daily life. The only downside is that we don’t celebrate any more. No champagne.