Waterfall to Agile for a Tester – Part 3

This content is syndicated from Agile Testing | Tester Troubles by Ray Claridge. To view the original post in full, click here.

WaterfallIn my previous series posts, I blogged about unfamiliar terminologies and processes that a tester might come across, when switching from waterfall to agile. These covered definitions of the Product Backlog, User Stories, Sizing, Pre-Planning, Planning and the involvement a tester should expect.

In this third and final post of the series, I cover all things sprint related such as: Sprints, Scrum stand-ups, Burn-down, Review and Retrospective.

Sprints - Fixed periods to develop a deliverable product increment. It is strictly time boxed: it’s more important to fall short than to slip the date. The Sprint includes design, coding, testing, and documentation. Once a Sprint has started only the Scrum Team can add or remove items in Sprint backlog.

Test involvement - You will be expected to plan, and manage the execution of all test scripts that cover the sprint tasks. Remember, the goal is to have a deliverable piece of code at the end of the sprint, so regression testing near the end of the period is crucial.

Scrum stand-ups - A daily 15 minute status meeting held in the same place and time every day for consistency. The team stand in a circle facing each other and address the following three questions.

1. What have you done since the last Scrum?
2. What will you do between now and the next Scrum?
3. What got in your way of doing work?

Test involvement - The three questions above apply to all development team members including the tester.

Burn-down - A chart showing remaining work in the Sprint Backlog created during planning. Updated every day, it gives a simple view of the sprint progress. It also provides quick visualizations for reference for the whole team and stake holders.

Test involvement - You will be expected update all test related tasks on the burn-down, as and when you work on them. One important thing to remember when updating is, you enter the hours remaining and not the hours spent.

Review - At the end of each sprint a review meeting is held. During this meeting the Scrum team demonstrates what they completed during the sprint phase to stake holders. Typically this takes the form of a demo of the new features.

Test involvement - As a member of the scrum team, you might be asked to demonstrate a piece of completed work you're familiar with.

Retrospective - This meeting is used to discuss the just concluded Sprint and determines what could be changed that might make the next Sprint more productive. Typically the discussion is around: what went well, what didn't go well and what actions does the team need to take into the next sprint.

Test involvement - As a team member, you'll be expected to contribute to the general discussion.

Ray

See all series posts:
Waterfall to Agile for a Tester - Complete

Leave a Reply

What is 4 + 6 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)

There are 101 ways to approach anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”

DAN PULHAM, DIGITAL DIRECTOR
TELSTRA