Showing posts with label waterfall. Show all posts
Showing posts with label waterfall. Show all posts

Wednesday

Part # 7 Points to watch out for when converting from waterfall to agile testing

Agile can be a challenge for the Test Analyst who has been trained and is accustomed to working in the traditional waterfall, Prince 2 environments or using the V model. A tester who finds themselves as part of “the team” using the agile scrum frame work can find that they are out of their comfort zone and may feel a little exposed. We recently held a meeting with a group of Test Analysts and asked them to identify what areas of our scrum implementation the needed to be improved and what areas they thought were going well. The key points identified are listed below.
Possible areas to Improve
50% said there were:
  • No proper test management processes.
  • Not enough sharing of information across the different groups (group = testers, product managers and developers).
  • No re-use of test scripts across the different on-line products using the same backend systems.
  • 25% said that:
  • Being left out of emails containing relevant information to the sprint.
  • Changing requirements half way through a sprint and not being clear on the actual change.
  • Test work not being prioritised enabling the tester to know what order to test tasks in.
  • Tester work is 1 to 2 sprints behind the development. (....Need to read the what done really means)
  • 100% stated that:
  • There was a lack of written requirements to test against, not enough detail in the requirements resulting in no real understanding on how a feature should work. Also a lack of forethought on features causes problems later on in th sprint.
  • No formal tracking of defects: only the tester is using the defect log and changing the status.

Areas that are going well:

  • 100% agreed that:
  • Definition of sprint cycle.
  • Sprint planning and pre-planning meetings.
  • Communicating daily with developers.
  • Good visibility as to what is coming up .
  • Agile process being well implemented- everyone understanding the business benefits of agile.
  • 75% agreed that:
    Close working with developers and business owners
  • Good use of the impediment log
  • Agile process being well implemented: everyone understanding the pros and cons of agile.
Tips for those new to the test agile role
If your thinking about joining a company, as a tester from a waterfall/Prince 2 background, that works in an agile way or your current company is planning to implement agile then I would recommend that you think about the following:
  1. Make sure that you attend the sprint planning meetings and wear your 'Business Analyst' hat – make sure you gather requirements that will enable you to write short test scripts and therefore test each backlog item and task. If need be arrange (with the Scrum Master and Product Owner) a follow-up meeting to clarify the requirements.

  2. Don’t be shy in raising impediments – it’s the Scrum Masters job to ensure that all impediments are removed so that “the team” can successful carry out their work. Impediments can include "I need more details on how this function should work."

  3. Review, on a regular basis, the product backlog and create and maintain a query log that maps each backlog item – this will help you when your in the sprint planning meeting to ask the right questions at the right time.

  4. Keep a defect log during each sprint - add those defects that are not cleared at the end of each sprint to the product backlog.

See also:
Agile Testing is not for Dummies
Agile requirements are barely sufficient!
Agile Testing
Why Testers should be in at the start







Pain without gain (ROI) or pleasure with gain (ROI).

Pain with a threatened ROI or pleasure with an improved chance of a greater ROI - which one appeals to you?

At the end of a waterfall project (or any project for that matter) the product manager or project manager will usually hold a ‘lessons learnt’ session where the participants of a project that has not gone so well discuss what went wrong with the view of improving performance on the next project. Developers and other technical team members feel put on the spot – attempting to explain, from their perspective, why the project was deemed a failure or put another way not as successfully as it could have been. The key points that ususally need to be explained, by product managers and developers, are why:
  • deadline were missed
  • budget(s) overrun or why
  • the customer wasn’t happy.

Post mortems of this kind are always uncomfortable and are a typical symptom of waterfall projects: lots of pain with out delayed gain (ROI).

The symptoms of agile are pretty much the exact opposite: short daily focussed, stand-up, meetings involving all stakeholders. Budgets (man hours) agreed up front and controlled by the product owners, sprint retrospectives designed to give business owner, product manager, and technical teams the opportunity to identify what could be done in the next sprint to improve on the previous one and the opportunity to put it into practice and evaluate with in a few weeks as opposed to many months or a few years (as is often the case under the waterfall project methodology).

From a Product & Project Mangers point of view waterfall is a long and drawn out process that may end up in a painful lessons learnt session. While agile gives short bursts of mild discomfort with the opportunity to turn the discomfort into a pleasurable experience as software gets delivered:

  • on time (time is fixed)
  • with in budget (which is under the control of the product owners) and
  • to the customer’s satisfaction (involvement in the sprint planning meetings the daily catch up meetings limits the chances of unpleasant surprises at the end of the project).

This sounds and feels like “pleasure with gain” or pleasure with increased/quicker return on investment (ROI).

For more: How do lessons learnt influence an organastion