AGILE

Scrum Roles and Responsibilities

The Scrum Team The Scrum Team consists of 3 roles a Product Owner, the Development Team, and a Scrum Master. Scrum Teams are self organising and cross-functional, the Development Team does not recognise more specific roles within it but Cross-functional teams have all the competencies needed to accomplish the work without depending on others that…

Agile vs Waterfall

Agile vs Waterfall As a Tester there is a big difference in your approach when it comes to using different SDLC methodologies. From my experience, the two that are often used are Agile and Waterfall. “One of the differences between agile software development methods and waterfall is the approach to quality and testing. In the…

QA Testing role within the Scrum Team

QA Role in the Scrum Team The QA Role within Scrum is not actually a recognised role, this is because everyone in the Development team is described as a Developer, this means that all members of the Scrum team are responsible for Quality. Which means it is down to all the members of the Scrum…

Certified Scrum Master and Scrum

Certified Scrum Master and Scrum Overview The Certified Scrum Master credential is designed for those who have experience as a Scrum Master or are looking to start a career as a Scrum Master. Candidates will gain a broad knowledge of the Scrum Agile Framework, the Scrum Masters role and the roles and responsibilities of the other…

Kanban Agile Methodology

Kanban Agile Methodology An Agile approach does not fit all oganisations and when adopting one several factors must be reviewed. One approach is that of the Kanban Agile Methodology. The Kanban Agile Methodology is one of the simplest Agile Methodologies. In essence it is a to-do list with priorities and each item/task is tracked by…

Agile Exploratory Testing

Agile Exploratory Testing Exploratory testing is a type of functional testing and is equally as important in an Agile testing environment as in the Waterfall testing environment. Exploratory testing allows testers to take ownership over the newly developed code and test it in a structured yet some say unorganised fashion. The QA tester does not follow…