Agile Test Management Using Jira and Zephyr

Agile Test Management Using Jira and Zephyr w/ Philip Lew and Chris Bland #AgileTesting #AgileJira

XBOSoft Dedicated to Software Quality Improvement Founded in 2006 Speeding products to market with our expert: • Software QA consulting • Software testing Global team with offices in San Francisco & Beijing © XBOSoft, Inc. 2020 All Rights Reserved

BDQ Delivering Digital Transformation Founded in 2002 UK Atlassian Solution Partner • Agile and Jira implementation experts • Atlassian Approved Training Partner • Atlassian tool consulting and training services • Agile and DevOps (Azure, AWS, CI/CD implementations) © XBOSoft, Inc. 2020 All Rights Reserved

House Rules ▪ Ask questions in the GoToWebinar/Zoom control panel on the right side of your screen or through Twitter @XBOSoft or @BDQ ▪ Questions may be asked throughout the webinar - we’ll try to answer them at the end ▪ You’ll receive info on recording after the webinar ▪ Ask questions and participate - we may ask questions too☺ ▪ Webinar Hashtags: #AgileJira #AgileTesting #AgileZephyr © XBOSoft, Inc. 2020 All Rights Reserved

Meet Our Speakers Philip Lew CEO and Founder, XBOSoft •Relevant specialties and passions o Software quality process, evaluation, measurement and improvement o Software quality in use / UX design o Mobile User Experience and usability o Cycling and travel © XBOSoft, Inc. 2020 All Rights Reserved

Meet Our Special Guest Speaker Chris Bland CEO and co founder, BDQ •Relevant specialties and passions o Test planning, setting up QA processes, procedures and tools, defect tracking and analysis, and test reporting. o Wealth of experience in working with both Waterfall and Agile development methodologies o Development and architecture o Atlassian Certified JIRA Administrator (GURU) o Sailing and owning a Bullmastiff © XBOSoft, Inc. 2020 All Rights Reserved

Where’s the Beef? • “Satisfy the customer” • “Valuable software” • “Changing requirements” • “Face to face conversation” • “Motivated individuals” • “Technical excellence” • “Regular intervals” Where’s the Quality in Agile? © XBOSoft, Inc. 2020 All Rights Reserved

Common Agile Test Management Problems • To Test Case or Not to Test Case • Requirements and test cases aren’t linked • Representing test cycles in Jira • Reporting on testing • Linking defects through to test cycles • Integrating testing into Sprints © XBOSoft, Inc. 2020 All Rights Reserved

PUTTING QUALITY INTO AGILE IMPLEMENTING AGILE REQUIREMENTS “Valuable software” achieved through “Satisfying the customer” “Changing requirements” facilitated by “Regular intervals” © XBOSoft, Inc. 2020 All Rights Reserved

Epics and Stories • An Epic is a high level requirement that may contain several User stories • User story needs to be broken down smaller pieces – These smaller pieces represent work that needs to get done. – Called tasks with details on feature description • Sub tasks can be used to define further • Enter a work estimate for user story or for task • Let’s look at one user story in detail © XBOSoft, Inc. 2020 All Rights Reserved

Representing Requirements: User Stories ● From the user's perspective, avoid use of technical terms and implementation details. ● General form of a user story: ○ As a < role>, I want <goal/desire> so that <value / benefit>. ○ Role is the user class of people who will be doing the task (eg: accountant, receptionist, bank teller) ○ Action explains the specific outcome. (eg: log in to my email, pull up a patient’s X-ray, sell shares of stock) ● Value or benefit is explained from the user’s point of view.

Building User Stories Examples of Value/Benefit ● As a shareholder, I want to sell 50 shares of stock so that I can get the money in my account. ● As a webmaster, I want to count how many people visit my site every day so that my sponsors will know the popularity of my site. ● The value is specific, but we may not know what happens after, nor the larger objective.

User Stories Cannot “Shelter at Home” • Description of an objective that a user should be able to achieve, or a feature that a user should be able to utilize, when using a software application. – As an Administrator, I want to be able to create User Accounts so that I can grant users access to the system. • User Stories cannot stand alone in isolation! • Must be accompanied by Acceptance Criteria with Acceptance Tests. © XBOSoft, Inc. 2020 All Rights Reserved

User Stories and Acceptance Tests Should Reside in the Same Household • User stories MUST be coupled with acceptance tests to ensure traceability. – "We write the acceptance tests with the requirements and keep them with story card for the lifecycle of the requirements.” – “Requirements are what you’re building and Acceptance tests help you measure what you built.” – “Acceptance test is the condition which your customer will accept the product you built. ” © XBOSoft, Inc. 2020 All Rights Reserved

Acceptance Criteria Should Include • Functional Criteria: Identify specific user tasks, functions or business processes that must be in place. Example: – “A user is able to access a list of available reports.” • Non-functional Criteria: Identify specific non-functional conditions the implementation must meet, such as design elements. Example: – “Edit buttons and Workflow buttons comply with the Site Button Design.” • Performance Criteria: Sometimes performance is critical to the acceptance of a user story and should therefore be included. Example: – Measured as a response time, spelled out as a threshold such as within 2 seconds. © XBOSoft, Inc. 2020 All Rights Reserved

Acceptance Criteria • Set of statements, each with a clear pass/fail result, that specify both functional (e.g., minimal marketable functionality) and non-functional (e.g., minimal quality) requirements applicable at the current stage of the project. • Represent “conditions of satisfaction” with no partial acceptance: Yes or No, Met or Not or Not Met • Define the boundaries and parameters of a User Story/feature and determine when a story is completed and working as expected. • Purpose is to add certainty to what the team is building. © XBOSoft, Inc. 2020 All Rights Reserved

Acceptance Criteria • Acceptance Criteria should state intent, but not a solution –“A manager can approve or disapprove an audit form” –“A manager can click an ‘Approve/Disapprove’ radio button to approve an audit form” • Criteria should be independent of the implementation and platform © XBOSoft, Inc. 2020 All Rights Reserved

● Start with basic examples, then expand through exploration. ● Use “Given - when - then” language to give the tests a consistent form. ● Stay focused on the story - avoid expanding the scope. ● Functional Acceptance Tests vs User Acceptance Testing (UAT) ○ Functional testing means the implementation meets the stated requirements (user stories). ○ UAT is about the intent of the requirements, and how it works in conjunction with the rest of the system to satisfy the user’s goals. ● Both functional testing and UAT can be included in the Definition of Done Writing Acceptance Criteria

Agile Requirements/Acceptance Model Example Team defines acceptance criteria to exit the sprint. ____ ties acceptance tests to criteria. Acceptance testing is done by ______. Acceptance by Whom? • User stories determined for the iteration. • User stories have associated acceptance criteria. • Acceptance criteria have associated tests. • In addition to the product owner, “Acceptance by whom” sometimes is just as important as the word “testing”. © XBOSoft, Inc. 2020 All Rights Reserved

User Stories with Tests • Test description (test objective) –Acceptance Criteria • Test steps • Expected results • Associated requirement (User Story) for traceability • Test Plan – Execution History © XBOSoft, Inc. 2020 All Rights Reserved

Linking requirements and tests

“One More Thing” on Acceptance Tests • Reusable and independent whenever possible • Design from the start with reusability and automation in mind for the sustainability of the product – (white box-static, API and UI) © XBOSoft, Inc. 2020 All Rights Reserved “We don't have automated acceptance tests which would be nice. At one time I was working toward that, but that was deprioritized by management.” @xbosoft @philiplew © XBOSoft, Inc. 2019 All Rights Reserved

MANAGING REQUIREMENTS - They’re always changing, Agile encourages change for the better... Using Jira with Zephyr – Demonstration on Managing Requirements with Chris Bland © XBOSoft, Inc. 2020 All Rights Reserved

Managing Requirements Baseline • Decide for a set of requirements to be implemented in a specific sprint • You don’t want changes in requirements for future to influence the current development iteration • Snapshot the set of requirements for developers to work on while product managers or product owners may be refining or changing the story. © XBOSoft, Inc. 2020 All Rights Reserved

Agile Requirements • Requirements are negotiable by the team during sprint planning – Team breaks the requirements into tasks – Team can negotiate decomposing large stories into smaller ones • During the project you generally stick to quality and timeline as the two fixed points, and features are the flexible post of the project. – Product owner / customer / team work together to negotiate quality and timeline © XBOSoft, Inc. 2020 All Rights Reserved

Managing Requirements Keep It Short Term (accurate) • Agile requirements need an agile process • The refining process happens regularly and accurately •Backlog not refined too far out (2-3 sprints) •Stories with Acceptance criteria not too far out (less than 3 sprints, maybe even current sprint) • People don't remember discussions after about 2 or 3 weeks. • Anything agreed to in a big spec, or future story far out is lost – forgotten • Hassle to maintain long specs over time. You have to keep returning to the spec & tweaking it, etc. © XBOSoft, Inc. 2020 All Rights Reserved

Traceability • Create tests from requirements (user stories) • Track defects from requirements • Find covered requirements from test cases • Find impacted requirements from defects • Traceability matrix report © XBOSoft, Inc. 2020 All Rights Reserved

Test Planning • Create a test plan • Input requirements (user stories) into the test plan • Accounting for configurations and platforms, test env. • Test assignment and execution • Report defects if found © XBOSoft, Inc. 2020 All Rights Reserved

Agile Still Needs Testing - How? Use today’s concepts supercharge your Agile Test Management Process 1. Users •Get users involved in helping to develop user stories and criteria 2. Developers work with Testers to: •Write clear acceptance criteria that are yes/no pass/fail •Develop common understanding TOGETHER 3. Testers • Plan and work within the Sprint Cadence • Document as necessary for communication, not CYA © XBOSoft, Inc. 2020 All Rights Reserved

• Don’t plan too far out • Multiple people reviewing / refining stories (product owner + QA + dev) – Makes the stories testable before any dev occurs – Identify unknowns in stories / tasks – Link requirements to defects for full transparency and traceability • Today we’ve shown how to do this with Jira and Zephyr, but there are many options Agile Test Management Requires Agility with Traceability © XBOSoft, Inc. 2020 All Rights Reserved

Post your webinar questions on Twitter @XBOSoft or @BDQTweets Registrants will receive an email with information on where to view the recording and slides from today’s webinar. Join us to keep updated on all our webinars, reports and white papers: facebook.com/xbosoft https://www.facebook.com/BDQ.cloud/ linkedin.com/company/xbosoft https://www.linkedin.com/company/bdq Check out our blogs: http://xbosoft.com/blog/ https://www.bdq.cloud/blog Download our free white papers: https://xbosoft.com/resources/white-papers/ Email us with ideas for future webinars or questions regarding our services! services@xbosoft.com enquiries@bdq.cloud Q&A www.xbosoft.com @xbosoft @philiplew @BDQTweets © XBOSoft, Inc. 2020 All Rights Reserved www.bdq.cloud

Agile Test Management Using Jira and Zephyr

More Related Content

What's hot

Similar to Agile Test Management Using Jira and Zephyr

More from XBOSoft

Recently uploaded

Agile Test Management Using Jira and Zephyr