The change program progressed more slowly than expected.This was in part due to a very flat organizational structure,which meant that it took longer than anticipated to get everybody onside with suitable tools for unit test and code analysis automation and configuration management.
The release testing team pressed ahead with automation of testing and reduction of the release testing window to four weeks but found it difficult to deliver in the four weeks because the development and configuration management changes had not been implemented.This led to lengthy integration delays caused in the most part by a lack of continuous integration by the developers.
What worked well included
It could be argued that these disciplines could have been adopted anyway,regardless of whether an agile method,such as XP,was adopted.
There is always a danger with testing or quality-driven improvement programs that the rest of the organization does not take them seriously.There was a feeling that with this “testing-driven” change program,the changes were tolerated as long as they didn’t cause any harm to the basic operating model of the company.
Additionally as the company grew and became established in the marketplace,it was observed during the sales process that potential customers were performing a more rigorous review of the development approach.There was a view that City Street Traders’ management was keen to wear the agile badge as a way of giving credibility to some of their established development practices.
What I would have done differently,with the benefit of hindsight,would have been to work harder to make the change self-propagating.Although the development team was already relatively small,I would have started with a smaller development team, let them establish the benefits,and then sell them onto their colleagues.Thus,a momentum for change would build up,mitigating against resistance and halfhearted adoption.The learning point from that experience is that just because the company is small,you do not have to change it all in one go.
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.