What is the methodology of software development based on the wiki?

Perhaps you mean something like Trac.
There is widely used a Wiki, there are analogues of many.

As a very dull sound instead of a definition. Probably meant not instead of product backlog, and the fact that pb items can be documented not in the backtrace or tfs, and in Vick. In the same scrum-e instead of some of the boards propose to use a wick that the whole Department was aware of what the team.

We did and easier and harder at the same time: the requirements are stored as Issues in Redmine, respectively, there are can be fixed and processed. And in a single document I collect them straight from the database a separate php scriptical. Its results if necessary, print, then the declared requirements document and sent to the customer.