AGILE FRAMEWORKS
IMPLEMENTATION ON
MOBILE PROJECTS. QA
ROLE IN AGILE
Artem Bykovets
(CSM, CSPO, CSP, Agile coach, founder and
CEO at StartIT)
Slide 2
Slide 2 text
• CEO and coach/mentor at "StartIT”
• Certified Scrum Master, Certified Product Owner, Certified Scrum Professional
by Scrum Alliance
• Certified Kanban System Design (KMP I) by LKU.
• Agile Consultant at Competera.
• Best Quality Assurance specialist of Ukraine by
IT Awards 2015.
• Judge and Expert at UA Web Challenge.
• Speaker at least 25 conferences (in 2015)
Few words about myself
Slide 3
Slide 3 text
METHODOLOGY OR MINDSET?
Slide 4
Slide 4 text
WARM-UP QUESTIONS
• Agile Teams do very little planning
• Agile is not suited for fixed bid projects
• Classical models like PMI are more suited to high-
risk projects than Agile
• Developers do not have the people skills needed
to talk to customers
• Agile teams don’t create documentation
• Some people need to be told what to do
WOULDN'T IT BE NICE?
Sorry....
1. Customers and users know what they want.
2. It can be described with words and images.
3. Engineers know how to build it in advance.
4. Nothing changes.
Slide 8
Slide 8 text
BUT WHY SO?
Slide 9
Slide 9 text
UNDERSTANDING GROWS CONSTANTLY
Slide 10
Slide 10 text
REVERSING IRON TRIANGLE
Slide 11
Slide 11 text
SCRUM IS:
A framework within which
people can address complex
adaptive problems, while
productively and creatively
delivering products of the
highest possible value.
Scrum is:
• Lightweight
• Simple to understand
• Difficult to master
Slide 12
Slide 12 text
EMPIRICAL PROCESS CONTROL
Slide 13
Slide 13 text
No content
Slide 14
Slide 14 text
AGILE TESTING
• While some teams do seem to use the “Agile” buzzword to justify simply
doing whatever they want, true agile teams are all about repeatable
quality as well as efficiency
• Agile is iterative and incremental. This means that the testers test each
increment of coding as soon as it is finished
• Programmers never get ahead of the testers, because a story is not
“done” until it has been tested