Documente Academic
Documente Profesional
Documente Cultură
2
Course Content
3
What is an Agile Project?
All projects are “agile”, but some agile projects
are more agile than others
5
What is Scrum?
Scrum in 100 words
• Scrum is an agile process that allows us to focus on
delivering the highest business value in the shortest
time.
• It allows us to rapidly and repeatedly inspect actual
working software (every two weeks to one month).
• The business sets the priorities. Teams self-organize to
determine the best way to deliver the highest priority
features.
• Every two weeks to a month anyone can see real
working software and decide to release it as is or
continue to enhance it for another sprint.
6
What is Scrum? - Principles
9 Scrum principles
Scrum contains sets of principles (some of them
required while others are optional) and
predefined roles
(1)Demo
(2)Sit together
(3)Daily Scrum
(4)Retrospective
(5)Sprint backlog
(6)Product Backlog
(7)Sprint planning meetings
(8)Time-boxed iterations
(9)Definition of Done 7
What is Kanban?
Kanban in 100 words
Visualize the workflow
Split the work into pieces, write each item on a card and put on
the wall.
Use named columns to illustrate where each item is in the
workflow..
Limit Work In Progress (WIP) – assign explicit limits to how many
items may be in progress at each workflow state
Measure the lead time (average time to complete one item,
sometimes called “cycle time”), optimize the process to make
lead time as small and predictable as possible
8
Kanban vs Scrum Board
Kanban and Scrum Board
V.S.
V.S.
10
What is Scrum process?
Scrum Roles Key Artifacts Ceremonies Process
Sprint planning
Product Backlog • Hosted by Scrum Master Product
• Requirements – user stories • Pick highest priority items in Backlog
• Desired work Product backlog and the team turns
• Prioritized by Product Owner the items into Sprint Backlog
• Anybody can add to it
Product Owner • Estimate sprint backlog in hours Sprint – 2-4 weeks
• Work breakdown
Sprint Goal Sprint Planning Sprint Goal
• Summary of focused work in • Declare Sprint Goal
sprint Daily Scrum Sprint
• Declared by Product Owner
• Accepted by team • Hosted by Scrum Master Daily Scrum Backlog
• 15 minutes - same time every day
Scrum Master Blocks
Sprint Backlog • Not for problem solving
• Team signs up for work of • 3 questions in meeting: (1) What Daily Work
their own – work never Product
did you do? (2) What will you do?
assigned (3) What’s in your way?
• Owned/managed by the team
• Estimated work remaining is • Team updates sprint backlog
updated daily Sprint Review/
Sprint Review
Blocks List • Hosted by Scrum Master – 2-4 hours Retrospective
Scrum Team • List of blocks & unmade • Accomplishments
decisions • Whole team participants
(max – 9) • Owned by Scrum Master
• Updated daily • Take form of demo for features
Product
Sprint Retrospective
Burndown chart Backlog
• Hosted by SM – 15-30 minutes
• Effort spent over period
• Stories/ features completed • Discuss on “Start doing”, “Continue 11
doing” and “Stop doing”
What are roles in Scrum?
14
What are roles of tester in Scrum? (cont.)
• Participant in Release/ Sprint
Planning
• Support developers in Unit Testing
– say them about testing view instead
of development view
• Test User Story when completed,
last gate to confirm testing
completeness
• Collaborate with customer and
Product Owner to define acceptance
criteria
• Provide positive feedback to
customer
• Develop automation testing
15
Testing Activity
in Scrum &
Kaban Process
16
What are Testing Activities in Scrum Process?
Process Tester must know what model of cadence used
Product
cadence
Backlog
single
Sprint – 2-4 weeks
cadence
Three
Sprint Planning Sprint Goal
Sprint
Daily Scrum Backlog
Blocks
Driven
Daily Work
Product event
Product •As a tester, he/she says how many hours should have
Backlog to complete testing for each of selected User Stories
•As a tester, he/she must understand what sprint goals
• As a tester, involves into the prioritizing process17
What are Testing Activities …? – estimate effort
Effort Estimate techniques:
Heuristic (expert judgment based) Parametric (calculation based)
Comparison to similar systems Function Points
Expert Judgment Use Case Points
Activity Based (top down) User Story Points
Task Based (bottom up)
Three-point estimate
50/90 estimate
18
What are Testing Activities …? – 50/90 estimate
50/90 Estimation
Worst case: number of hours (cost) in the worse-case scenario
Most -likely: number of hours (cost) in the Most -likely scenario
19
What are Testing Activities …? – 3-point estimate
20
What are Testing Activities …? – User Story Points
User Story points (USP)
Story points are a unit of measure for expressing the overall size of a
user story, feature, or other piece of work
The raw values assigned are unimportant
Image a story with 2 USP(s) will 2 times bigger than 1-USP one
Two estimation scales or or
Velocity is a measure of a team’s rate of progress – Ideal Time
21
What are Testing Activities in Scrum Process?
Process
Product
Backlog
22
What are Testing Activities in Scrum Process?
Process
Product
Backlog
25
What are Testing Activities in Scrum Process?
Process
Product
Backlog
27
What are Testing Activities in Kanban Process?
Kanban is less prescriptive than Scrum
All testing activities are similar with Scrum
28
What are Testing Activities in Kanban Process?
An Example of Managing Tasks/ Work Item
1. Backlog: state all work items/ user stories translated into
tasks - As a characteristic of Backlog may be limited
number of items
2. Ready: List of work items that ready for executing
3. Specifics: Identify what criteria to confirm work item
completeness
4. Execute: Work Item in executing
Tuan completed work item - Next, he moves another work He also moves another work
testing for “Sorting Items”. He item – testing for “Filter Items” item from Backlog as a
reviews and confirms that it from ready to “execute” to pipeline item.
satisfied criteria state. He moves start new work
29
this item to “Done”
What are Testing Activities in Product Development?
Testing against Testing in live
user story environment - UAT
Non-functional
Unit Testing
testing/ confirms
Integration Test
story is met
Non-functional
Unit Testing
testing/ confirms
Integration Test
story is met
34
How to track bugs in Agile Process?
Do or Do Not need Bug Tracking.
No bug Tracking is still working well when testers perform their tests
in Dev environment
36
What are Agile Testing Techniques? Quadrants
Automation &
Business Facing Manual
Manual Test Test
Exploratory Testing
Functional Testing
Scenario Test
Story Test
Usability Test
Prototypes Test
Support the team
Critique Product
User Acceptance Test
39
References
Testing Experience
http://www.testingexperience.com/
40
Recommended useful tool for Agile Team
- the ultimate screenshot capture software designed specifically for
testers that:
- Snap a single screenshot or record a sequence of screens
- Automatically generate intelligent step-by-step narration (defect report)
- Auto submit tickets to defect tracking and ALM systems
Agile 3
Testing
Others 4
42