At the risk of starting a circular argument, Wikipedia defines a Wiki as
a collection of web pages designed to enable anyone who accesses it to contribute or modify content, using a simplified mark-up language. Wikis are often used to create collaborative websites and to power community websites. The collaborative encyclopaedia, Wikipedia, is itself one of the best-known wikis. Wikis are used in business to provide intranets and Knowledge Management systems.
The manager of the team I had been assigned to, as a work experience student, gave me the goal of implementing a Wiki to provide the team with a resource for posting team news and success stories. In effect my teammates were also the customers/users of the Wiki
The inevitable requirements creep1 would eventually lead to the purpose of the Wiki being extended to include information on best practices for the team, definition of team roles and responsibilities, team structure, and reporting/liaison lines(in effect, a process/framework definition for the team–yet another recursive aspect of the project and this case study write-up)!
Given the nature of the system I was tasked with developing, the chaotic nature of the requirements(often driven by two different managers simultaneously, plus the ad hoc requests/comments from the team;i.e., the users), the lack of available resources(i.e., low/no budget, plus limited access to other human resources), and the need to employ a formal method to develop the Wiki, I determined that adopting an agile approach would be the best solution to developing and testing the software.
Also, using an agile approach to developing and testing the Wiki seemed a particularly appropriate solution, as the origin of the word Wiki comes from the Hawaiian wiki wiki, which is translated as “fast.”
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.