By storing all open issues in one prioritized list, Betaboard makes it easy to decide where to allocate your team's resources for maximum impact.

Subscriber login | Contact us

A service of Arlo Leach
Copyright © 2001-24, all rights reserved

Design principles

If you find something Betaboard can't do, it might not be a bug! We've found that consistent QA processes tend to break down without a few key limitations, so we built Betaboard to encourage these principles:

1. Project managers approve and prioritize new QA notes before developers address them. This ensures that at least one person on each project can keep a big picture view, attending to critical issues first while weighing the cost/benefit ratio of smaller issues.
2. Clients can interact directly with the system, posting notes and monitoring their progress through the development cycle. However, clients can't edit notes once they've been posted, and can't view the ongoing discussions among your team members. (You can override these limitations by increasing user permissions in the admin pages.)
3. Anyone can remind a team member of an outstanding note with an email notification, but this feature is intentionally limited to avoid overuse. With Betaboard's powerful sorting and filtering functions, nobody needs a mailbox full of reminder notes to stay on top of their work!
   
   (click to enlarge)
4. All communication about quality assurance issues takes place within Betaboard. This gives your team a complete record of development, keeps all status information in real time, and eliminates the need to check multiple locations for project news.