In a Scrum team, there are three roles: Product Owner, Development Team and Scrum Master. There is no explicit mention of software testers and some could question if testing specialists are really necessary in Scrum teams. After working on several projects, Eric Delahaye has found that they are and shares with us four reasons why they should be included as soon as the first Sprint Planning.
Before including a user story in a Scrum sprint, it is important to clarify and confirm its acceptance criteria.In recent years, lots of Agile software development teams have been using a simple collaborative technique called Example Mapping to break down user stories. It was conceived co-founder of Cucumber, Matt Wynne, who wrote the seminal post introducing the practice “Introducing Example Mapping“.
How do you manage software quality in Scrum? In traditional waterfall projects, teams will try to detect bugs in the final software testing activities like integration and acceptance tests. With the short timeframe of Scrum sprints, this approach does not work for Agile projects. In his book Scrum Product Ownership, Robert Galen provides some guidance on how to build quality software with one fundamental tip: you don’t test quality!
Agile Open Florida is a conference organized by leaders and volunteers from the Agile Florida community who are passionate about building community and advancing all things Agile. Adam Sandman, whose company was also sponsoring Agile Open Florida 2016, has written his personal report about some of the sessions.
Jeff Sutherland makes a convincing argument of using Scrum outside of software development in his recent book Scrum: The Art of Doing Twice the Work in Half the Time. A full 111 years before Sutherland published this book, the Wright Brothers practiced scrum to outmaneuver better funded and more entrenched competitors. REPL driven development is a technique that comes to business software creation from the scientific computing community.
If we often associate Agile mainly with project management, the principles of the Agile Manifesto can also be applied to other software development activities. In this article, Nadya Knysh explains how to use these principles in mobile software development and more specifically in the testing of mobile apps.
How often did you meet a situation when everybody knows about an issue, at retrospective everybody agrees that it should be resolved, but next retrospective brings the same issue and the same action items? Why team of mature developers cannot change a situation on a project, cannot apply new practices or fail to apply innovations? Let me explain it on real project example and get you to the root cause, go from best practices to basic principles and back.
Copyright © 2009-2020 Martinig & Associates