What Worked Well
With the project complete, the Wiki delivered and working, and having had the time to review what I did(is this what they call an agile retrospective?), I would like to report the following positive aspects of the development process:
What Would I Change in the Future?
Although the project completed successfully(admittedly, with a deliberate fifth iteration overrun), with the benefit of 20–20 hindsight, the one area I might change, if I was still working in the team and there was a requirement to run a similar project, would be in the area of continuous integration and refactoring.
What I would have liked to have been able to do was to undo changes I had made in a formal, safe(i.e., allowing me to restore a change), and repeatable manner. For example, if a particular request for a change had resulted in a catastrophic problem in the system, it would have been nice to have easily restored the system to its prechange working state. Also, it would have been nice to have been able to retain those successful changes that might have been made in parallel with the problem change while undoing that change.
Given the relatively low size and complexity of this project, this was in practice a relatively small problem(although I did spend several frustrated sessions in the evening, and on one occasion across a weekend, fixing such issues). However, I can see where this would be an extremely serious issue with larger and more complex applications and larger teams.
This seems to me to be largely a configuration management problem, and my solution to this issue on future projects would be to employ tool support, using either a shareware tool off the Internet for the sort of small project described in this case study or a more capable and robust proprietary product for larger, industrial-strength projects.
Perhaps the most innovative thing I might try in the future, if I was involvedin a similar project, would be to use some of the new hi-tech means of online collaboration, such as team meetings in Second Life. For example, I have heard of Second Life design review meetings where the team could actually walk through a 3D representation of the design diagrams and provide instant online feedback on the information displayed. While Second Life might not be a perfect solution to the problem of not being able to get together for face-to-face meetings, I really believe it is an option well worth exploring(assuming my older colleagues actually have accounts on Second Life)!
Finally, my only other wish–and again while this was not really an issue on this small project(I can see benefits for larger and more complex projects)–would be to consider automated software testing. In the case of this project, a web testing tool(to check navigation, usability, and security)might have been very useful and, for larger projects, some form of record and playback tool to regression-test later builds and releases could save huge amounts of valuable tester time and effort(avoiding the unwelcome prospect of spending too much time manually testing the software in the evenings and at weekends, when I could have been out partying instead)!
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.