LogoLogo
  • About SimplifyQA
  • Get Started with SimplifyQA
    • Agile & Non-Agile Framework
    • OS Support
    • SimplifyQA Hosting
      • On-premise Installation Guide
        • Pre-requisites
        • Installation Guide
      • Support and Resources
      • Training and Onboarding
    • Explore SimplifyQA for your Application Lifecycle Management
  • SimplifyQA Installation & Setup
    • Setup QAWizard
    • Register QAWizard
    • Setup Android Device
      • How to enable settings in android device?
      • How to register android device?
      • Setup emulators on Android Studio for automation in SimplifyQA
    • Setup iOS Device
      • How to setup iOS device in Apple Developer Account?
      • How to register iOS device?
  • Get to know your Workspace
    • Blueprint of SimplifyQA
    • Key Terminologies
    • Search/Global Search
      • How to use global search?
      • How to use advance search?
      • How to use column sort?
      • How to use column filters?
      • Add or remove columns
    • Rich Text Editor
    • Import & Export
    • Add Attachments
    • Add Linkages
    • Add Comments
    • Manage Cards in board view
    • Configure Watchlist
    • Track Edit History
    • Hierarchy Tree
  • Admin Controls & Configurations
    • Manage Projects & Users
      • Create Project and Invite Users
      • Project Settings
        • Create and Manage Custom Fields
      • Grant Admin Privilege to User
      • Invite/Add Users to Team
      • User Directory and Access Control
      • Configure Page Layout
      • Manage Roles and Privileges
      • Configure Auto-logging of Defects
    • Configure your clients
    • Password settings
  • Release & Sprints
    • Introduction to Releases
    • Create & Manage Release & Sprint
    • Start & Close a Sprint
  • Create and Manage your Requirements
    • Introduction to Requirement Management
    • Create & Manage Epic
    • Create & Manage Features
    • Create & Manage User Stories
  • Introduction to Test Management in SimplifyQA
    • Create a Manual Test Case in SimplifyQA
    • Create an Automation Test Case in SimplifyQA
    • Learn API Testing in SimplifyQA
      • Create an API Test Case in SimplifyQA
      • Quick Test the API
      • Validating API Responses
      • Understanding API Parameterisation
      • Save API Response Data
      • Achieve Data flow for E2E Testing
    • Create Hybrid Test Case in SimplifyQA
    • Leverage Re-usability in your Tests
    • Organise your Test Cases
    • Linking a Test Case to User Story
    • Linking a Test Case to Defect
    • Version Control your Test Case
    • Create a Copy of your Test Case
    • Copy Test Case to different Project
    • Conditional Statements
      • Decision Making Statement
      • Looping Statement
      • BREAK & CONTINUE Statement
    • Supported Actions
    • Utilising Mobile Inspector in SimplifyQA
  • Introduction to Script-less Recording of Test Case
    • Record a Web Test Case in SimplifyQA
    • Record an Android Test Case in SimplifyQA
      • Record an Android Test Case
    • Record Functions in SimplifyQA
    • Understand Object Recognition Mechanism & Self Healing in SimplifyQA
  • Test Data Management
    • Work with the Formulas to Optimise Test Data
    • Import and Export Test Data Sets
  • Introduction to Object Repository
    • Capture Objects for your Tests
    • Organise your Test Objects
    • Parameterise your Test Object Properties
  • Introduction to Parameters
    • Various Types of Parameters
    • Create and Utilise Parameters in your Test Case
    • Understanding Runtime Parameters
  • Defect Management
  • Marketplace
    • Integration with Project Management Tools
      • Integrating SimplifyQA with Jira
        • Configure Web-hooks
        • SimplifyQA Setup for Integration
          • Setup your Account for Jira Integration
          • Configuration in SimplifyQA Admin
          • Steps to Generate a Jira API Token
          • Steps to create SimplifyQA token
          • Steps to get Jira Account ID
          • Synchronisation Functionality Between SimplifyQA and Jira
          • Analyse Logs for Data Synchronisation
        • Mapping Fields for Issue Types
        • Viewing SimplifyQA Test Cases in Jira
  • Legal Documents
    • End-User License Agreement
Powered by GitBook
On this page
  • Creating a New Release
  • Creating a New Sprint
  • Plan your Sprint
  • Start the Sprint
  • Sprint states in SimplifyQA
  • Close the Sprint
  1. Release & Sprints

Create & Manage Release & Sprint

PreviousIntroduction to ReleasesNextStart & Close a Sprint

Last updated 1 month ago

This document provides instructions on how to create a new release and sprint in SimplifyQA.

Creating a New Release

  1. Access the Release Creation Page:

    • Navigate to the Releases section from the left menu.

    • Click the "Create" button.

    • Select 'Release' option from the dropdown.

  1. Enter Release Details:

  • Name: Provide a clear and concise name for the release.

  • Owner: Select the project owner responsible for the release.

  • Projects: Associate the release with the relevant projects.

  • Planned Start Date: Set the planned start date for the release.

  • Planned End Date: Set the planned end date for the release.

  • Estimated Effort: Estimate the total effort required for the release (in hours or story points).

  • Description: Provide a brief description of the release's goals and objectives.

  1. Save the Release:

  • Click the "Create" button to save the new release.

  • Click the 'Save & Create Sprint' to save the new release and create sprint.

Creating a New Sprint

  1. Sprint Creation Page:

    • Navigate to the Sprints section from the left menu.

    • Click the "Create Sprint" button.

  2. Enter Sprint Details:

    • Name: Provide a clear and concise name for the sprint.

    • Owner: Select the project owner responsible for the sprint.

    • Start Date: Set the start date for the sprint.

    • End Date: Set the end date for the sprint.

    • Release: Select the release to which the sprint belongs.

    • Description: Provide a brief description of the sprint's goals and objectives.

  1. Save the Sprint:

  • Click the "Create" button to save the new sprint.

Plan your Sprint

Once a release and sprint have been created, start planning the work for your team.

To add stories, tasks and defects to your sprint:

  • Navigate to sprint plan.

  • Drag and drop the items in the designated sprint

Note: Create and plan sprints for the future to align with the product roadmap.

Start the Sprint

  • Navigate to the Sprint: Open the specific sprint you want to start.

  • Check Sprint Details: Verify the sprint details and the tasks, defects or user stories assigned to it.

  • Confirm: Click on 'Confirm' to start the sprint.

Sprint states in SimplifyQA

You come across 2 different sprint states in SimplifyQA:

  1. New

  2. In-progress

  3. Completed

  • New: A newly created sprint that has not yet begun and means that

    • No work has started.

    • The sprint backlog is being defined or refined.

    • The team is preparing for the sprint planning meeting.

    • What are the next steps to start the sprint?

      • Define the sprint goal.

      • Select backlog items to be included in the sprint.

      • Break down tasks and estimate effort.

      • Assign tasks to team members.

  • In-Progress: A sprint that is currently underway & active and means that

    • The sprint planning meeting has been completed.

    • The team is actively working on tasks and user stories.

    • Daily stand-ups are conducted to track progress and address issues.

    • Regular reviews and retrospectives are scheduled.

    • What actions need to be taken to ensure the sprint is goal is achieved?

      • Daily stand-ups to track progress and address impediments.

      • Work on assigned tasks and user stories.

      • Collaborate with team members to resolve issues.

      • Conduct regular code reviews and testing.

  • Completed: A sprint that has been finished and all its tasks have been completed and means that

    • The sprint review and retrospective meetings have been conducted.

    • The team has delivered the planned work.

    • The sprint backlog has been updated to reflect the completed work.

    • The team is ready to start the next sprint.

    • Before closing the sprint, you need to ensure,

      • Conduct a sprint review to demonstrate completed work.

      • Hold a retrospective meeting to identify lessons learned and areas for improvement.

      • Update the product backlog with completed and remaining items.

      • Prepare for the next sprint planning meeting.

Close the Sprint

  • Navigate to the Sprint: Open the specific sprint you want to close.

  • Close the Sprint: Click on the "Close Sprint" button. This action officially close the sprint.

  • Verify Sprint Completion: Ensure all tasks and user stories within the sprint are marked as "completed." Review the sprint backlog to confirm that all planned work has been finished.

  • Confirm: Click on 'Confirm' to close the sprint.

Additional Tips

  • Break Down Work into Tasks: Within each sprint, create tasks to break down the work into smaller, manageable chunks.

  • Estimate Task Effort: Assign estimated effort (in hours or story points) to each task which gives you visibility on the capacity of the team.

  • Assign Tasks to Team Members: Assign tasks to the appropriate team members, ensure to tag multiple teams if there are stories which requires cross functional team to be involved.

  • Track Sprint Progress: Monitor the progress of each sprint and make adjustments as needed.

  • Review and Reflect: After each sprint, conduct a retrospective meeting to review what went well, what didn't, and what can be improved in future sprints.

: Click on the "Start Sprint" button. This action officially initiates the sprint.

Start the Sprint