The Pharos Beta is a critical step in the development of the Pharos Project. The future of healthy building material selection rests on your active involvement to help refine and shape the tool. We need your help.
It is important for you to understand that you are participating in the development process of Pharos at an early stage. Till now, Pharos has been an idea and those of us who have spent months thinking about and implementing the vision don't pretend to have thought of everything. We are committed to our values of establishing a user-driven, democratic, Open Source process for improving upon and completing our work. Therefore, in the spirit of the Open Source movement, we are inviting you to be part of that early cycle of initial review. This means that you have an unprecedented opportunity to play a part in substantially shaping the look, feel and functionality of these tools - not to just tinker around the edges. We fully expect very substantive commentary and critiques from you - the users. We also expect that as a result of your input these tools may look very different in a few weeks or 6 months or in the coming years.
What is a Beta test period?
Beta testing is where a select group of people is given access to the available set of Pharos Tools for a limited time. Throughout the testing period, participants use the tools and report any problems and opinions they might have. If this sounds like something you would like to do, click here to join the community of Pharos Beta Testers.
Why is the Pharos Project conducting Beta tests?
Tests of web applications and software are routinely conducted by potential users to test new or enhanced services and tools. The Pharos Project is introducing a new approach to evaluating and selecting building materials designed to be user-driven, open-source and democratic, making the purpose of a Beta testing period even more significant as we want the Pharos community to get the tool that best meets the needs that led to the creation of the Pharos Project to begin with.
Regardless of what is being tested, a Beta program has three main objectives:
To verify the design and usability of new or enhanced features with real world users, before the product is released
To find any bugs not previously identified by internal Quality Assurance
To ensure technical support operations will be prepared to support the product upon its release
Who can become a Pharos Beta tester?
Our primary interest is in the architects, engineers, designers and building material specifiers that are making decisions about building materials every day. But, at this point, no one is excluded as long they complete the Pharos registration process and agree to the Pharos Beta Testers Users Agreement. The Pharos Project reserves the right to close participation in the Beta testing period at any point it deems necessary and/or appropriate. Consistent with our values, we will be transparent about our decision and report our rationale for such a decision to the Pharos community.
After you fill out the form, you will be entered in our database of testers and can begin using the various Pharos Tools available during the Beta testing period. You may be contacted about a specific test or question for which you qualify.
Why should I volunteer to become a Pharos Beta tester?
The Pharos Project is a democratic, user-driven, open-source process. As the old saying goes, democracy is not a spectator sport! This means we rely on you, the building material users, to ensure the project is on the right track.
The Pharos Beta testing period is a critical step in the development of the Pharos Project. It's the time for users to improve the tool and provide feedback as we refine and improve the Pharos framework and tools.
As a Pharos Beta tester, what will I be able to do?
Beta testers can use the Pharos Product Library and create Pharos labels on specific building products by evaluating available data and rating importance across the three major categories of Environment & Resources, Health & Pollution, and Social & Community, and associated subcategories. Testers can also upload data and add new products, create Pharos labels, and store them in the product library for others to view and provide comments.
Beta testers will determine what's working and what's not, and provide critically important suggestions and improvements to the tool. Collaboration among testers, users and the Pharos Team will help move the Pharos Project toward a wider public release of the tool later.
How will I report problems and provide feedback?
A ticketing system has been established allowing you to report problems to our technical support team. The same system will allow you to provide feedback on any aspect of Pharos. The Pharos Wiki will offer a discussion board to talk about issues with both the Pharos team and the greater Pharos community. The Pharos Wiki Community Manager will glean ideas and suggestions from the ongoing discussions and communicate them back to the Pharos Team for incorporation into their efforts to improve Pharos.
Where and how do I begin?
First, you must register and accept the Pharos Beta Tester User Agreement. Those who do not register and accept the terms of the user agreement can browse the site, but will not be able to enter data, evaluate products and create their own Pharos labels.
Once you have registered, you can browse and search for products using CSI, LEED or Pharos criteria. You can enter and rate new products. Just follow the on screen instructions.
Why do I have to accept the user agreement to be a Pharos Beta tester?
In order for the Beta period to be useful to the Pharos team, and ultimately, the public, we want to ensure that all testers understand and agree to the parameters and goals of the Beta process. If you are not comfortable with the User Agreement, you can choose to wait until the Pharos tools are more fully vetted with other testers and we unveil Version 1.0.
What will be expected of me as a Pharos Beta tester?
Beta testing does entail a significant commitment of time and effort on your part. We hope that you will:
Remain available to test for the duration of the testing period
Maintain Internet access and provide us with your current email address and other information required in the registration process
Read all testing instructions or tasks presented to you on testing web sites or via email
Use the tools being tested as soon as you receive access to it
Regularly report your honest, thoughtful feedback throughout the testing period
Additional special tasks or behaviors may be necessary for specific tests
What feedback do I have to give?
Your feedback will be needed in some keys areas:
Report of any problems or "bugs" found during testing
Identify areas for improvement in all aspects of the Pharos Project
General testimonial of your experience using Pharos tools
You will be asked to answer several questions related to product usage. We would like you to push the product to its limits whenever possible. We solicit feedback on areas for improvement and bugs in the programs as well as request a testimonial of your experience using the software. Beta testers must participate actively in order to be considered for future tests.
You will be asked to execute a test suite and answer several questions related to the performance of the product during the tests. We would also appreciate your comments on what you liked or didn't like about the product's functionality, feel, and interface, as well as any other feedback you wish to give.
What are "bugs"?
"Bugs" are a coding error in a computer program (i.e., glitches and software malfunctions). Bugs can also represent problems with how the software interacts with the computer hardware. This is one thing Beta testers help discover.
Are there limitations to the Pharos Tools during the Beta test period?
The Beta version of Pharos Project Tools is not complete. For example, the Pharos Team is still investigating rating mechanisms for certain categories such as Climate Change and Community Relations, amongst others. The Beta version is expected to contain defects and a primary purpose of this Beta testing is to obtain feedback on their performance and the identification of defects. With the feedback of Beta testers we aim to complete the tools and release Version 1.0. at some time in the near future.
What are the benefits of joining the program?
This is your chance to contribute to product design! By testing and providing feedback, you help determine the product's functionality, feel, and interface. You can help shape the tool so that is something you can rely heavily on in your daily practice. We welcome comments from Beta testers about the features and overall usability of the Pharos Tools. You have an opportunity to evaluate the system early in its development cycle for potential benefit to your work. We do recognize that Beta testing is a purely voluntary effort and we appreciate the time and effort each Beta tester expends.
Unlike any other interaction you might have with us, testing allows you to communicate directly with the people who design and build the systems you like and need - through the feedback you submit.
In addition to identifying bugs, Beta tester's suggestions can provide the inspiration for new features and ways for moving forward.
What if I want to test, but don't want to be REQUIRED to actively participate and give feedback?
We want Beta testers that can actively participate to help us perfect the Pharos Tools. If you can't actively participate, we recommend that you not participate in the Beta testing period. You will still be able to browse our site and view products rated by Beta testers. You can also participate in ongoing discussions via the Pharos Wiki.
What are the Pharos Project's Technical Support commitments?
The Pharos Project will provide a ticketing system for providing feedback, suggestions and input for improving the tools. We will, to the best of our abilities, provide technical support, although it will not always be able to be timely, one-on-one support. You can always contact us at info@pharosproject.net.
How often will feedback be incorporated into the Pharos tools?
We may periodically update Pharos tools during the Beta testing period and report such updates on our Web site and via email to all Beta testers. These updates will include any newly implemented fixes. The interval between these updated versions will depend on the number and nature of the feedback and changes. We estimate that the postings will be several weeks apart.
Will product data I enter during the Beta period be preserved for use long term in the Pharos Project?
It is our goal to make use of all product data submitted through the Pharos Tools during the Beta test period. All data submitted will be transferred to the next version subject to review for consistency with and changes made to the Tools and their data requirements during the period.
When will Pharos Version 1 be released to the market?
This is hard to predict. Much depends on the extent and nature of the feedback we receive and the length of time it takes to complete the tools. We'll keep you informed through emails and updates on our progress will be posted on our websites.
Can I be prevented from being a Beta tester?
You may be excluded from being a Pharos Beta tester if you fail to register, don't agree to the terms of the User Agreement or if the Pharos Project has determined Beta testing capacity has been met.
