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.


See all series posts:

Waterfall to Agile for a Tester - Complete

Leave a Reply

Your email address will not be published. Required fields are marked *

eleven − three =

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

What People Say

“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”


“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“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.”


“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”


“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”


“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”


“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”



To explore how we can help you, please get in touch