Agile Walk Through - Free Beta

Improve communication and project knowledge sharing


Agile Walkthrough encourages to communicate in structured way where all information is gathered as a project knowledge base.

It allows your team to be more efficient through eliminating of much waste and stress connected with the situation when oral communication prevails or when you don't have project information organized in a convenient way.

Save time on asking

When team members have access to up-to-date structured information about project they don't have to ask others with the same questions, and repeat the same things over and over again. Things are made clear once, and updated with changes made, when necessary.

Prevent interruptions

Needless to say, that interruptions are extremely counter-productive, and the situation, where the common way of getting necessary information or help is to go and ask colleagues, makes such environment really difficult for an effective work. Working with AWT means replacing this habit with searching for the necessary information in structured knowledge base first, and if it's not there - putting a question in relevant part of the base, what will save team-mates from interruptions, supply the inquirer the most relevant answers and deliver that information to all other interested parties. Moreover, asking the question in written, often can lead one to the answer to this question, some offers of the solutions or at least will make it clear which information is missing.

More clarity

Things explained in written are usually much more precise and thought out, whilst in oral communication things, in spite of sounding clear, often still remain quite vague when it comes to using that information communicated in spoken.

Save time eliminating many of your meetings

Very often meetings are only about exchanging the information, which is relevant only for some of the participants, but everybody's time is consumed anyway. And this can be much more effectively achieved through structured written communication - things will be clearer, much less time will be spent, information will be saved for further development process.

Keep everybody updated

Team-mates can choose which parts of the knowledge base are essential to track and can be sure that they always have recent knowledge about those areas.

Why is it better than Requirement specifications?

The main problem with traditional document-based specifications that they are not Agile.

  • It requires significant investment of time to create document which is complete enough,
  • It is very difficult to create such documentation by more than one person which often leads to one of two silly situations: either there's one or few analysts/architects and the rest are just executing monkeys doing exactly what they are told and not caring at all, or development team bringing more of their ideas and knowledge in the process and drifting away from the specification which sooner or later becomes completely irrelevant,
  • So those documents are usually either big and monolith and it's a pain to get acquainted only with needed subset of information or they are split, almost not connected with each other and making it even more difficult to orient in them,
  • It's difficult to discuss particular parts of the document and update interested parties with clarifications or changes,
  • It's almost impossible to go with a document gradually filling and changing it keeping everybody updated,
  • Finally, those documents are usually boring - people just avoid reading them if they can get away without doing it.

Why is it better than Wiki?

  • Wikis are just too flexible to maintain the order where it's clear to which part of the knowledge base particular information should belong,
  • Therefore it's very difficult to watch updates only of relevant subset of the information,
  • Information in wikis is completely disconnected from planning, estimating and work-reporting, whilst often it's convenient to have it coupled (description of the feature and it's evolution, plans and work progress information).
Copyright 2007-2010 Agile Walkthrough