agilewalkthrough.com
Be transparent - the key idea of Agile Walkthrough
http://agilewalkthrough.com/key-ideas/be-transparent
Replacing some of the oral communication and on-site meetings with written artifacts. Being distributed or offshore. AWT helps you to easily navigate constant information flow, watching the bits of it which are the most appropriate for your occupation within the project. The whole information is roughly divided into project design, planning, workload and general notes. It is possible to subscribe to necessary subset of the information, to watch only relevant updates. Part covers work necessary to address...
agilewalkthrough.com
Easy start and way through the project - the key idea of Agile Walkthrough
http://agilewalkthrough.com/key-ideas/easy-start-and-way-through-the-project
Easy start and way through the project. There are three main challenges in every undertaking: first is. To keep on going. And the third one is. Often it's difficult to start describing things in a structured, top-to-bottom, complete way from the beginning, unless it’s a small project or you are a genius. Picasso once said. I begin with an idea and then it becomes something else. AWT makes it easy to start with anything and continuously shape your concept. Bringing it to the finish. Is similar to programm...
agilewalkthrough.com
Expected pricing of Agile Walkthrough
http://agilewalkthrough.com/expected-pricing
At the current moment we are a tiny company and the price of the service we're planning to offer you on a commercial basis will be in large extent imposed by our costs: (a) server facilities necessary to provide fast and reliable service, and (b) support costs. During Beta phase we expect to get better understanding of usage frequency, load, and get other related information in order to create fair pricing. Plan – $25. No additional workers available,. Plan – $50. Active workers included with the plan,.
agilewalkthrough.com
Quality assurance - the feature of Agile Walkthrough
http://agilewalkthrough.com/features/quality-assurance
AWT has following means to assure quality of the product:. Verification of requirements,. Verification of fixed bugs,. Verification of tasks implementation,. We understand a snapshot of the developed software that can be run on a computer. It helps to track the state of the code-base in which certain issues arose or being resolved. In AWT builds can be used to track:. In which build bug was found,. In which build bug was fixed,. In which build task was implemented. Tracking time and progress.
agilewalkthrough.com
Requirements - the feature of Agile Walkthrough
http://agilewalkthrough.com/features/requirements
Requirements describe expectations about the result which should be produced (i.e. how it should behave, look and feel). They define necessary attributes, capabibilities or characteristics of the system in order to be valuable for the user. In AWT requirements are superior design elements, and they are used as subjects of planning and as containers for tasks and bugs. Requirements are organized in a hierarchy. Drag-And-Drop sorting of elements. As a child of more generic. You can create a requirement as.
agilewalkthrough.com
Access to project - the feature of Agile Walkthrough
http://agilewalkthrough.com/features/access
In AWT you can work on multiple projects, giving people specified access to them. Add companies and people to project:. Can add people or just companies,. Can add people from their companies who will participate in the project. In every area there are three levels of access:. Hides all applicable data from the user,. Allows user to browse entities and comment on them, where comments are available,. Gives user possibility to create, change, browse and delete data. Access to project notes.
agilewalkthrough.com
Be distributed or offshore - the key idea of Agile Walkthrough
http://agilewalkthrough.com/key-ideas/be-distributed-or-offshore
Be distributed or offshore. Collaboration is the core of Agile approach and canonical Agile requires having whole team including customer in one location. Customer's role is to answer domain-related questions of the development team which arise, review progress and re-evaluate priorities. Our approach to be Agile in distributed environment is:. Constant communication in structured and written form, sharing project knowledge within all team in form of AWT project artifacts,. Reasons for being distributed.
agilewalkthrough.com
Reserving team members - the feature of Agile Walkthrough
http://agilewalkthrough.com/features/reserving-team-members
Are used to ensure availability of team-members. Reservation is created for a defined period of time and results in multiple reservations added for particular working days. There can be different approaches to form a project team imposed by project- or company-specifics:. Project team can be fixed for whole duration of the project or its iterations. For example:. 1 business analyst - 4h / day,. 1 ui designer - 4h / day,. 3 programmers - 8h / day * 3 = 24h / day,. 2 qa engineers - 8h / day 6h / day,.
agilewalkthrough.com
Bugs - the feature of Agile Walkthrough
http://agilewalkthrough.com/features/bugs
Bug is a term used to describe encountered situation when delivered result doesn't behave, look or feel as it should. Bugs life-cycle is similar to the one of tasks. Verification/rejection of bugs is configured per project. Since bug is defined as something which doesn't work as it should, AWT encourages to create the bug for the requirement which describes correct target result. Associating a bug with a parent requirement brings following benefits:. Depending on organization of your team, responsible pe...
