My name is Greg Hodgkinson and I work for Prolifics, where one of my roles has been to provide leadership in software development process. It has to be said that I started with a love–hate relationship with agile methods born out of many years’ experience of seeing them both being successfully used, but also(sometimes)abused;let me explain:
So, taking a step back, it’s not the methods themselves I have a problem with–far from it– ut rather the blind faith from those who have jumped on the agile bandwagon without proper consideration for what they are trying to achieve.
And who hasn’t jumped on a bandwagon at some stage or other? In fact I’d suggest that one of the best things about the emergence of agile methods is that it has stirred up passions for the use of software development processes as a way of improving the lot of the IT professional–fantastic!
But blindly applying agile methods without really trying to understand what problems you’re trying to solve with them, and also which problems you’re not relying on them for solution, can cause unnecessary problems. I’d like to start by observing three reasons why adopting methodologies sometimes goes wrong:
So building on this, for anyone who has spent any amount of time thinking long and hard about software development methodologies, the inevitable and oft-written conclusion is that the best thing to do is to customize your own–consider the types of projects you need to run in your organization and then take the best bits of the various methods out there(as applicable) and combine them to “grow your own!”
Apply care and attention, prune where required, and over time you will end up with a mature method that perfectly fits the needs of your organization. It also helps to start with the right seeds(base methods)and cuttings(customizations). Don’t get me wrong–there is no reason for the average organization to have to build a custom method from scratch. The exercise should be one of assembly rather than of build. If you’re building your own from the ground up then you’re doing it the hard(and expensive!) way.
This case study focuses on methods to support a specific class of project–those that produce SOA solutions. To support these projects requires “special tactics” over and above what is covered by “out-of-the-box” agile methods. This is the raison d’ˆetre for me growing my own method–AgileSOA, which, as the name suggests, combines the best of two classes of methods: agile methods and methods used to produce SOAsolutions.
This case study is based on my experiences in applying this method to a number of significant customer projects over the years at Prolifics and at my previous company, 7irene, where this method was first formed. Any method should be judged by its performance, and we have yet to have a project use this method that has not been a success(although we have learned along the way!). I hope you find some parts of this case study useful to your own efforts to “grow your own” method!
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.