3. Epics: Large user stories that are often used as placeholders for new ideas that
have not been thought out fully
INCEPTION
4. 01. SHOW NOW
SHOWING SCREEN
02 SHOWING LIST OF
MOVIES
03 FETCHINGMOVIE
DETAILS
04 NOW SHOWING UI
5. Iteration - 0
LANGUAGE DATABASE
ANALYSIS ON
STORIES
PERFORMANC
E TESTING
TEAM
COMPOSITION
AUTOMATION
STATERGY
UNDERSTANDIN
G BACKEND
GOOGLE
ANALYTICS
UI DECISION
INTEGRATION
WITH
BACKEND
SPIKES
SCENARIOS
ON STORIES
6. ANALYSIS :
Ø List of movies should be displayed
Ø Should display effect details
Ø Max number of movies that should be accommodated
Ø Movies should be displayed in ascending or descending
order of names
Ø Subtitle information should be displayed
• If more than one movie with same name how should
application behave
• Since showtimes view is in list view what is use of having
one more list view in now showing screen
SCENARIOS:
7. PRE IPM
vGetting information for movie, effect and language
comes from same table
vEstimate based on spike, task, backend
understanding
ITERATION PLANNING MEETING
v Based on team composition,pick set of stories that could be
finished within iteration
02 SHOWING LIST OF
MOVIES
03 FETCHINGMOVIE
DETAILS
8. KICKOFF
q Effects should be displayed only once <effects stored in one
column comma separated resulted in separate story>
q If movie name is too big how should the application display
movie name
9. ü Volleyball
ü Manual Testing
ü Defect : Movie for which all sessions done by morning keep
displaying till end of day
ü Check for automation
ü Functional automation
ü NFR Testing
ü Manual scenarios not automated
ü Showcase
ü Bug bash
10. QA Areas of Interest:
Ø Scenario Analysis of future iteration
Ø kick off, volleyball and Dev huddles of current iteration
Ø More scenarios based on kick off and volleyball
Ø Current and past iteration story testing
Ø Bugs testing
Ø Automation coverage
Ø Regression testing scenario
Ø Watch on pipeline
Ø Track bugs