3. Scrum practice
Sprint Planning
Sprint
Daily scrum meeting
Sprint review
Retrospective
Product backlog Team structure
and capabilities Bussiness condition
sprint backlog Sprint burndown
chart 30 days plan
Daily 15 min status meeting
Task discussion and
implement Decision making
Information setup as and
when required
30 days plan
Review meeting
Process improvement Scrum master responsibility
Priortization and
task discussion
4. Agile testing Strategies
Initiate Project
Constructive iteration
Release end game
Production
Iteration0
Initiate the project
Constructive Iteration
Delivering work system
that meets the
changing needs of
stakeholder
Release[End
Game]
Deploy release X
into production
Production
operate and
support release
X
Start work on
release x+1
5. Iteration0
Establishing business Case
Establishing Boundary Condition
Outlining Key Requirement
Outlining one or more Condition architecture
Identifying the risk
Cost Estimation and prepare preliminary project
6. Construction Iterations
This phase observed as set of iteration to build and increment of the solution.
Each iteration, team uses hybrid of practice like XP, Scrum, Agile modelling
etc.
Team follows prioritized requirement practice, most essential remains from
work item stack.
Construction Iteration classified into two
1.Confirmatory Testing
2.Investigation Testing
7. Confirmatory Testing
Verifying that the system fulfils intent of the stake holders as
described to the team to date
It has two aspect
1.Development Testing
It is a mixer of unit testing and traditional service integration
testing
2.Agile Acceptance Testing
Traditional functional testing and acceptance testing
8. Investigation Testing
It deals with common issue like Integration testing and load/Stress Testing
and Security Testing
9. Release End Game or Transition Phase
Goal is to deploy your system successfully into production activity.
Include training of end Users, support people and operational people.
It include full System Testing and acceptance Testing.
Testing without any obstacle, full testing in construction iteration.
Tester will be working in its defect stories.
12. Roles--
Product owner
1.Decide product features
2.Priortized feature according to market value
3.Responsible for profitability
Scrum master
1.Maintain blacklist and remove barrier
2.Manage team and work for productivity
Team
1.Team organize and schedule there work by own
2.Has right to do everything within boundary of project to meet sprint goal
13. process
User Stories
short explanation of functionality of system under test
Product Backlog
Collection of user stories
Release Backlog
Release is a small time frame in which number of iteration is completed. Scrum Master decide stories should be
targeted for a release
Sprint
Decide by product owner and developer team, set of period of time to complete the user stories 2-4 weeks
Sprint Backlog
list of task to be completed in sprint
Block list
Iist of blocks and unmade decision owned by scrum master and updated daily
Burn Down Chart
It represent overall progress of WIP. And work complete through out the process
14. Ceremonies
Sprint Planning
Importing stories from the release backlog, hosted by scrum master
Daily Scrum
Daily 15 minutes
Discussion of work completed previous day, planned work for next day and issue
Sprint Review/Retrospectives
2-4 hours
Discussion of what team has accomplished in the last sprint and lesson learn
Editor's Notes
What is Agile
Agile is methodologies, that promote Continuous Iteration of Development and Testing throughout the software Development life Cycle of project.
Scrum
Crystal methodologies
Dynamic s/w Development method
Feature Driven Development
Lean Software Development
Extreme Programming
Agile testing life span through four stages
Iteration 0 or initiate the project
Performing initiatial setup task
Identify people for testing, installing testing tools, scheduling resource(usability testing lab)
Majority of testing occurs during this phase
Team identify potential problem in the form of defect stories
