We decided that there were two aspects to the successful delivery of the system:
Rather than try to adopt a whole new process we decided to adopt a smaller number of agile practices taken from the Essential Unified Process.The concepts within this process are delivered using cards–this means that minimal information is referenced when it is needed.The practices used were Iterative Essentials and Use Case Essentials.
The beauty of the Essential Unified Process is that it adopts a practice-based approach,where the practices underlying the process are defined separately in a way that allows you to select just the ones that will benefit your project.In this case we didn’t have to adopt the other practices from the process(such as the component based development or architecture practices)to be able to benefit from the use of use cases and iterations.
the deliverables the project needed.The diagram on each was ticked to show the level of detail required for that deliverable.
The practice approach provides a very agile way of using small parts of the process to add value where and when needed. Lightweight is the key adjective for this, and we took advantage of this to introduce the changes quickly and effectively.
We also followed the advice provided by the iterative practice for improving communications and introduced daily Scrums.The improved communication allowed us to minimize the amount of documentation we produced(although the minimum on this project actually turned out to be quite a lot!).Combining smart communication with fit-for-purpose levels of documentation turned out to be very important in supporting the testing effort needed to ensure high-quality and reliable delivery.Communication through simply talking has proven invaluable in ensuring that all stakeholders are headed in the same direction.
Due to the need for high quality,we placed the testing at the heart of the process.Our process encouraged the involvement of the test resources throughout the project in
as many activities as possible (and in many more activities within this project than any other I have previously worked on). For example, the testers were involved in working with the customers alongside the analysts, producing the test cases at the same time as the use cases (an integral part of the use case essentials practice). This test-driven approach provided us with significant improvements in productivity and accuracy compared with traditional methods, and the software continues to be developed using this technique. Similarly, we ensure that the requirements, both functional and nonfunctional, have a test built alongside them during their development. We have found that spending time on establishing traceability between the requirements, tests, and components provides the minimal level of documentation that is needed and adds value. This was especially true when the personnel changes within the team were so regular, new staff could understand the system by means of the documentation provided and quickly become productive with relatively little negative impact on the project. The idea of having good people plus good process within the team was also extended to the customer; we took the approach that the customer representative was an essential part of the team and mandated that customer representatives be involved in the software development from day one. We followed the assumption that “the customer will only know what they want when they see it,” and through having them on hand at all times we could make sure that we were building and testing the right thing. The agile principle of promoting good and regular communication works very well with the customer and cuts down the amount of time spent on clarifying or confirming issues.
Agile Testing Related Interview Questions
|ETL Testing Interview Questions||Manual Testing Interview Questions|
|Selenium Interview Questions||Database Testing Interview Questions|
|Automation Testing Interview Questions||Software testing Interview Questions|
|Performance Testing Interview Questions||Embedded Testing Interview Questions|
|A/B Testing Interview Questions||Hadoop Testing Interview Questions|
Agile Testing Tutorial
Old-school Development And Testing
Agile Development And Testing
From Waterfall To Evolutionary Development And Test
How To Test A System That Is Never Finished
Implementing An Agile Testing Approach
Agile Testing In A Remote Or Virtual Desktop Environment
Testing A Derivatives Trading System In An Uncooperative Environment
A Mixed Approach To System Development And Testing: Parallel Agile And Waterfall Approach Streams Within A Single Project
Agile Migration And Testing Of A Large-scale Financial System
Agile Testing With Mock Objects: A Cast-based Approach
Agile Testing – Learning From Your Own Mistakes
Agile: The Emperor’s New Test Plan?
The Power Of Continuous Integration Builds And Agile Deve- Lopment
The Payoffs And Perils Of Offshored Agile Projects
The Basic Rules Of Quality And Management Still Apply To Agile
Test-infecting A Development Team
Agile Success Through Test Automation: An Extreme Approach
Talking, Saying, And Listening: Communication In Agile Teams
Very-small-scale Agile Development And Testing Of A Wiki
Agile Special Tactics: Soa Projects
The Agile Test-driven Methodology Experiment
When Is A Scrum Not A Scrum?
Analysis Of The Case Studies
My Agile Process
The Roll-out And Adoption Of My Agile Process
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.