2. What is the role of QA ?

3. Change
Request/BRD
Requirement
Analysis
Development
UAT testing Deployment
QA analyze the
Requirements

4. Change
Request/BRD
Requirement
Analysis
Development
UAT testing Deployment
QA analyze the
Requirements
Test Case
Writing
QA ROLE

5. Change
Request/BRD
Requirement
Analysis
Development
UAT testing Deployment
QA analyze the
Requirements
Test Case
Writing
System
/Integration
testing
QA ROLE

6.  A software development lifecycle is essentially a series of
steps, or phases, that provide a model for the
development and lifecycle management of an application
or piece of software
Phases
 Requirements
 Design
 Development
 Testing
 Deployment

8.  Once an application is in the testing stage, it is
very difficult to go back and change something
that was not well-thought out in the concept
stage.
 No working software is produced until late during
the life cycle.
 High amounts of risk and uncertainty.
 Poor model for long and ongoing projects.
 Not suitable for the projects where requirements
are at a moderate to high risk of changing.

9. Incremental framework for software project
development.
Introduced to accommodate rapid product
changes.
Frequent releases in short development
cycles (sprints)
Minimal Documentation.

12. Traditional software development models
 Pre-defined set of features
 Delivering large piece of software or entire Product
 Long Development
 Less Stability
Agile software development model
 Prioritized set of features
 Delivering small pieces of software one by one
 Shorter development
 More stability

13. What is Scrum ?
 Scrum is one of the verities of Agile
 Incremental framework of software engineering

14. Why people do Scrum ?
 To maximize teams ability to deliver quickly and respond
to evolving and changing requirements.
 To develop functionality in smaller and stable
increments(as opposite to one large unstable bundle) –
have potentially deliverable product in shorter periods of
time.

15. Form a Scrum Team
 Scrum Master (Maintains the process)
 Product owner (Represents the stakeholders and
business)
 Team (Dev , QA, Analysts, tech writers)
 Team size 5-9
 If need to scale – Add more scrum teams

16.  Leads the team
 Helps removing obstacles
 Safeguards the process
 Can be anyone with necessary skills

17.  Defines Requirements (Product Backlog)
 Prioritizes features
 Owns Release dates
 Open to negotiations with the team (Dev,QA)
 Can be Product/Project/Marketing Manager

18.  Developers , QA’s, Analysts, Tech Writers
 Actually does the work
 Responsible for estimates and planning the work

19.  Basic unit of development in Scrum
 Team decides the duration(Based on Requirements)
 Story Writing
 Typically 1-4 weeks
 Before Sprint – Sprint Planning
 After Sprint –Review demo and retrospective

20. Sprint Planning:
 Conducted by Developers and QA’s
 Estimations (Based on daily working hours of each resource)
 Time Duration (2 to 2.5 days) if a 2/3 week sprint
Sprint Execution
 Developers start development
 QA Starts test case writing
 QA Executes Tests and report bugs
 Developers fix bugs
 Daily Scrum (Resources will explain (Yesterday/Today work and impediments)
 Daily Scrum Stand-ups (Resources will explain what they have assigned and what they have
completed)
 Daily Status(sent to Manager’s)
 Weekly Status(Sent to PO, Scrum Master and Managers)
Sprint Completion
 Make sure no open bugs
 Stories should be closed
 Sprint Demo and Retrospective

21. At the end of the sprint team conduct sprint
retrospective for future improvements
 What made this sprint Successful or worked well for the
team ?
 How would we improve this further?
 What made this sprint less than successful/needs to be
improved?
 What would you recommend the team to improve this?
 Anyone deserves special recognition during this sprint?

23. Management Perspectives
 Resource Management (Enables project managers to
track what their resources are doing)
 Disciplines the team
 Each Individual is responsible of its work
 Awareness

24. Software Management
 JIRA
 TFS by Microsoft
 Orange Scrum
 Yodix
Bug Tracking
 Mantis
 Pivotal Tracker