Upgrade to Pro — share decks privately, control downloads, hide ads and more …

"Implementing Agile frameworks on mobile development projects QA role in agile" from Artem Bykovets

"Implementing Agile frameworks on mobile development projects QA role in agile" from Artem Bykovets

What is Agile — a methodology or philosophy? Why all that stuff like Scrum and Kanban is not working sometimes? What if the customer’s "wishlist" go constantly and he is not willing to wait even a week before the end of the sprint? Where is the space for Acceptance testing in the iterative development and do we need test documentation in Agile? - All answers on these and many other questions you can get from this slides.

uaMobiTech

August 02, 2016
Tweet

More Decks by uaMobiTech

Other Decks in Programming

Transcript

  1. AGILE FRAMEWORKS IMPLEMENTATION ON MOBILE PROJECTS. QA ROLE IN AGILE

    Artem Bykovets (CSM, CSPO, CSP, Agile coach, founder and CEO at StartIT)
  2. • 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
  3. 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
  4. 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.
  5. 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
  6. 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