LinkedIn emplea cookies para mejorar la funcionalidad y el rendimiento de nuestro sitio web, así como para ofrecer publicidad relevante. Si continúas navegando por ese sitio web, aceptas el uso de cookies. Consulta nuestras Condiciones de uso y nuestra Política de privacidad para más información.
LinkedIn emplea cookies para mejorar la funcionalidad y el rendimiento de nuestro sitio web, así como para ofrecer publicidad relevante. Si continúas navegando por ese sitio web, aceptas el uso de cookies. Consulta nuestra Política de privacidad y nuestras Condiciones de uso para más información.
Waterfall vs Agile
High Risk Low RiskVS
• Early testing of requirements and the design of
features during the early stages of the project.
• First execution of the feature being developed.
Don’t wait until a feature is fully developed to test it
if you don’t have to. Try to find issues as quickly as
• Regression testing following changes and fixes.
• Integration testing is carried out as soon as
something is ready to integrate. Rather than waiting
to integrate a mass of features, especially
deliverables from earlier increments are integrated
with current deliverables.
• Effective and productive involves the input and collaboration of
all people involved; all stakeholders. This will increase the
productivity of the test, fix and reset cycle. This is inline with the
Agile concept of collaboration – any one who can test something
should! This usually means the business owners testing the
features they requested.
• This concept only really works when teams are collocated. If this
is not the case then a clear plan or process needs to be in place
to ensure that there are working arrangements for testing.
Since we are developing in iterations, then we should also
test in iterations. Tests should be ran several times before
the product passes the customers tests. Tests need to be
designed to be repeatable.
Being collaborative, working together and ensuring that regular demonstrations take place
allow you to test the full end-to-end experience of the feature. The full feature needs to be
tested like this so you can ensure changes can be made to enhance the experience.
As well as the developer and QA testing the feature, an
independent user should also test. Involvement from the
business teams ensures that an independent view is
All tests needs to be prioritized. It may not be possible to test
everything exhaustively. Each test needs to be attached to a
product or feature. The major or high risk tests should be
carried out first – the ones with the biggest impact.
With this method, tests are created even before development is
created. This ensures that the acceptance criteria are confirmed
before any effort is wasted on creating the wrong product.
Risk Based Testing
Some tests, if done first can reduce the risk with putting a new
development in a production environment. It would be best value
to carry out these tests first. All requirements should be assessed
for risk, and will allow you to prioritize the tests for each one, so
resource can be applied appropriately.