Greetings, all,

I would like to initiate a once-a-year solicitation of feedback from the 
Hackystat community regarding their desires for future development.  To do 
this, I've designed the following questionnaire, which I intend to send out to 
hackystat-dev-l, hackystat-users-l, hackystat-announce-l, all accounts on the 
hackystat public server, and another (ISERN) mailing list that contains people 
who have been actively following Hackystat.  I'd like to send it out to you 
folks first for feedback before sending it out "for real". 

So, please take a look at the following, and let me know if you see 
opportunities for improvement.  Don't answer the questions yet---I will 
distribute the improved version again to this list. I'd like to get it out by 
the end of this week, so if you can reply with any comments you might have in 
the next few days, I'd appreciate it. 

Cheers,
Philip

-----------------------------------------------
Greetings,

I am sending this email as a representative of the Hackystat Project
<http://www.hackystat.org/> to request your involvement in prioritizing
future development activities by responding to the following survey. It
consists of four questions and will take most people only five to 10
minutes to complete. You can reply to this email and indicate your
responses in any way you wish, and you can answer only a subset of the
questions if you prefer. Feel free to forward this email to any other
people you think might be interested in influencing future development.
Your reply will be confidential. Only aggregate, anonymous summaries of the
data will be provided to the development team to help prioritize future
development activities.

1. Your usage class (indicate all that apply):
* User (I collect and analyze project data)
* Administrator (I download, install, and maintain a hackystat server)
* Developer (I design and implement sensors, sensor data types, analyses, etc.)
* Other (please explain)

2. Your current barriers to use (indicate all that apply; clarifying comments 
appreciated)
* Sensors are difficult to install.
* Sensors do not collect the appropriate data.
* Server is difficult to install.
* Server does not provide appropriate analyses.
* Problems due to the GPL license
* Problems using the public server
* System performance
* Documentation
* Interface complexity/usability problems
* Privacy problems 
* Organizational/political issues 
* Other

3. Your desired future measurement/analysis capabilities (indicate all that 
apply)
* XP/Agile
* Project cost/size/schedule estimation
* Model-driven development
* Requirements management
* Risk assessment
* Security
* Defect analysis
* UML
* CMM
* Other

4. What tools do you use for which you would like a Hackystat sensor?

Thanks very much for your help. If you would like to receive a followup
email with a high-level summary of results, please indicate so here. 

Cheers,
Philip

Reply via email to