Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
SlideShare a Scribd company logo

Scrum Testing Methodology

•Download as PPT, PDF•
•
G
Gaya1985

The document provides an overview of agile scrum testing methodology. It describes agile testing as testing practices that follow the agile manifesto and treat development as the customer of testing. It then outlines the key aspects of scrum testing including product backlogs, sprints, daily standup meetings, sprint planning and retrospectives. It also discusses the proposed scrum testing process of identifying test scenarios, writing test cases per sprint, delayed execution, and inclusion of defects in the product backlog.

1 of 11
Agile Scrum Testing Methodology– an Overview - Gayathri
Agile Testing - Overview What is Agile Testing? Agile Testing can be defined as a Testing practice that follows the agile manifesto, treating development as the customer of testing Testing practice for projects using agile methodologies.
Agile Testing - Overview Process in Scrum Testing A Product Backlog of prioritized work to be done The entire product backlog items are split into a fixed set of items called Sprints A daily Scrum Meeting is organized where the team discusses three question. What have you done since the last daily meeting? What will you be doing until the next daily meeting? What impediments, if any, are in your way? A Sprint Planning session where the Sprint Backlog items are split with the team members A Sprint Retrospective session where the team member would put forward the best practice they followed or introduce a process would need to implement for a successful Sprint. All the meetings will be facilitated by the Scrum Master.
Characteristics of Scrum Testing
Agile Testing – Process proposed Scrum Testing process workflow Identify the Test Scenarios based on the BRD document Obtain sign-off of the Test Scenario document from the respective Business Owners Test Cases will be written for Sprint by Sprint basics Execution will be done by delaying a Sprint (When Sprint 2 items are developed we will be executing Sprint 1 functionality) A change in a requirement or a defect will be added to the product backlog A constant regression bed is identified for all the completed Sprints Since delaying the testing by a Sprint may provide a gap between the development team and the testing team, we will have a pre deployment in each Sprint which helps us to address the major issues pro actively.
Agile Testing – Process proposed Testing process workflow
Sprint Schedule with QA Tasks
Agile Testing – Process proposed Scrum Terminology Scrum Master: The person or persons in charge of the tracking and the daily updates for the scrum (equivalent to a project manager). Sometimes referred to as a Scrum Facilitator. Scrum Team: A cross-functional team (developers, B.A.s, DBAs, and testers) responsible for developing the product. Product Owner: The person responsible for maintaining the Product Backlog via continuous interaction with Clients and Stakeholders. Story: A customer focused description of valued functionality. Product Backlog: The stories to be completed. Sprint: A time period (usually 2 to 4 weeks) in which development occurs on a set of stories that the Team has committed to. Sprint Backlog: The Team's interpretation of the product backlog containing concrete tasks that will be done during the next sprint to implement some of the top items in the Product Backlog.
Agile Testing – Process proposed Scrum - FAQ’s What happens if you don’t finish on time? Scrum does not allow a delivery date to be altered! If you are behind, you delete items in the Scrum Team’s Sprint Backlog and if you are ahead you can ask the Product Owner for more tasks. Can Scrum only be used for smaller projects? No, the method can be up-scaled by putting together several smaller projects to form one larger. A so-called Scrum of Scrums can include hundred of programmers, organized in dozens of Scrum Teams. Where does the word Scrum come from? Scrum is a rugby term for the close-knit shoulder-to-shoulder formation a rugby team forms to jointly move the ball forward. The word was first used by Takeuchi and Nonaka in a famous article published in the Harvard Business Review in which they described the most successful product development projects in Japan.
Agile Testing - Overview How can Testers prove their value Demonstrate a helpful perspective in defining software expectations Provide information. Don’t act like a gatekeeper. Adapt to changing project goals. Work with what you have, ask for what you need to know, document what you can.
Thank You!!!

More Related Content

Scrum Testing Methodology

  • 1. Agile Scrum Testing Methodology– an Overview - Gayathri
  • 2. Agile Testing - Overview What is Agile Testing? Agile Testing can be defined as a Testing practice that follows the agile manifesto, treating development as the customer of testing Testing practice for projects using agile methodologies.
  • 3. Agile Testing - Overview Process in Scrum Testing A Product Backlog of prioritized work to be done The entire product backlog items are split into a fixed set of items called Sprints A daily Scrum Meeting is organized where the team discusses three question. What have you done since the last daily meeting? What will you be doing until the next daily meeting? What impediments, if any, are in your way? A Sprint Planning session where the Sprint Backlog items are split with the team members A Sprint Retrospective session where the team member would put forward the best practice they followed or introduce a process would need to implement for a successful Sprint. All the meetings will be facilitated by the Scrum Master.
  • 5. Agile Testing – Process proposed Scrum Testing process workflow Identify the Test Scenarios based on the BRD document Obtain sign-off of the Test Scenario document from the respective Business Owners Test Cases will be written for Sprint by Sprint basics Execution will be done by delaying a Sprint (When Sprint 2 items are developed we will be executing Sprint 1 functionality) A change in a requirement or a defect will be added to the product backlog A constant regression bed is identified for all the completed Sprints Since delaying the testing by a Sprint may provide a gap between the development team and the testing team, we will have a pre deployment in each Sprint which helps us to address the major issues pro actively.
  • 6. Agile Testing – Process proposed Testing process workflow
  • 8. Agile Testing – Process proposed Scrum Terminology Scrum Master: The person or persons in charge of the tracking and the daily updates for the scrum (equivalent to a project manager). Sometimes referred to as a Scrum Facilitator. Scrum Team: A cross-functional team (developers, B.A.s, DBAs, and testers) responsible for developing the product. Product Owner: The person responsible for maintaining the Product Backlog via continuous interaction with Clients and Stakeholders. Story: A customer focused description of valued functionality. Product Backlog: The stories to be completed. Sprint: A time period (usually 2 to 4 weeks) in which development occurs on a set of stories that the Team has committed to. Sprint Backlog: The Team's interpretation of the product backlog containing concrete tasks that will be done during the next sprint to implement some of the top items in the Product Backlog.
  • 9. Agile Testing – Process proposed Scrum - FAQ’s What happens if you don’t finish on time? Scrum does not allow a delivery date to be altered! If you are behind, you delete items in the Scrum Team’s Sprint Backlog and if you are ahead you can ask the Product Owner for more tasks. Can Scrum only be used for smaller projects? No, the method can be up-scaled by putting together several smaller projects to form one larger. A so-called Scrum of Scrums can include hundred of programmers, organized in dozens of Scrum Teams. Where does the word Scrum come from? Scrum is a rugby term for the close-knit shoulder-to-shoulder formation a rugby team forms to jointly move the ball forward. The word was first used by Takeuchi and Nonaka in a famous article published in the Harvard Business Review in which they described the most successful product development projects in Japan.
  • 10. Agile Testing - Overview How can Testers prove their value Demonstrate a helpful perspective in defining software expectations Provide information. Don’t act like a gatekeeper. Adapt to changing project goals. Work with what you have, ask for what you need to know, document what you can.