Overview of Very-small-scale Agile Development And Testing Of A Wiki Agile Testing

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.”

All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

Agile Testing Topics