Big feature - small sprint

  • 40 min

During last two years I've been working in Agile teams and quite often have come across the situation when the feature is pretty big, but they still want to release it at the end of the sprint. That is in spite of the fact, that there is a great risk of violation of the timing and poor product quality.

So what should we, quality guards, do when eventually everything depends on us?

My report presents the analysis of the development stages from the testing point of view in such a difficult situation and provides tips for success.

Большая фича - маленький спринт. Советы для успеха from Vlad Orlikov on Vimeo.

Comments ({{Comments.length}} )
  • {{comment.AuthorFullName}}
    {{ comment.DateCreated | date: 'dd.MM.yyyy' }}

To leave a feedback you need to