Tilo Linz

Testing in Scrum

Notify me when the book’s added
To read this book, upload an EPUB or FB2 file to Bookmate. How do I upload a book?
These days, more and more software development projects are being carried out using agile methods like Scrum. Agile software development promises higher software quality, a shorter time to market, and improved focus on customer needs.However, the transition to working within an agile methodology is not easy. Familiar processes and procedures change drastically. Software testing and software quality assurance have a crucial role in ensuring that a software development team, department, or company successfully implements long-term agile development methods and benefits from this framework. This book discusses agile methodology from the perspective of software testing and software quality assurance management. Software development managers, project managers, and quality assurance managers will obtain tips and tricks on how to organize testing and assure quality so that agile projects maintain their impact. Professional certified testers and software quality assurance experts will learn how to work successfully within agile software teams and how best to integrate their expertise.Topics include:Agile methodology and classic process modelsHow to plan an agile projectUnit tests and test first approachIntegration testing and continuous integrationSystem testing and test nonstopQuality management and quality assuranceAlso included are five case studies from the manufacturing, online-trade, and software industry as well as test exercises for self-assessment.This book covers the new ISTQB Syllabus for Agile Software Testing and is a relevant resource for all students and trainees worldwide who plan to undertake this ISTQB certification.
This book is currently unavailable
313 printed pages
Have you already read it? How did you like it?
👍👎

Quotes

  • Mikhail Chesnokovhas quoted9 years ago
    Practices
    Planning Poker:
    – Estimation in Story Points (SP), minimum of 1, maximum of 13 SPs per task
    – Break complex tasks down into smaller units
    – Acceptance criteria are to be agreed on and recorded in writing
  • Mikhail Chesnokovhas quoted9 years ago
    eHome Controller project Team Charter
    Team Charter
    – How we will implement Scrum in the eHome Controller project –
    Sprint
    Duration: 4 weeks
    Each Sprint is preceded by a Sprint Planning phase and ends with a review
    Meetings
    Daily Scrum: At 11am, maximum duration 15 minutes, Product Owner takes part
    Sprint Planning: Wednesday at 9am (at the start of the Sprint), maximum duration 1 day
    Review: Tuesday at 11am (at the end of the Sprint)
  • Mikhail Chesnokovhas quoted9 years ago
    A successful Sprint delivers a potentially shippable product. Early Sprints should deliver at least a prototype to show the customer, while later Sprints should generate constantly improving releases that can be used in a productive environment
fb2epub
Drag & drop your files (not more than 5 at once)