Open Stack

Hi Lauren,

The survey that was distributed at the Cloud Foundry Summit was intended to “recruit" app developers for future studies rather than a deep dive to understand needs, pain points, etc.  It was intentionally short because it’s a bit tough to stand in a vendor area and complete a survey.

The actually app developer survey is just started to be created here:

https://etherpad.openstack.org/p/newton-osux-appsurvey

It’s really intended to do a deeper dive with app developer and identify their specific needs, i.e. pain points, needs, etc.  Flanders is right that we should do interviews before and after the survey. The interviews before the survey could potentially help identify which questions should be part of the survey and the interviews afterwards could be used to help add some clarity to how respondents answered the survey.

It might be helpful to schedule a meeting because it feels like the various teams aren't quite aligned on goals for each survey.

In any event, I’m driving out to Bueno Vista, CO to scope a few fourteeners.

Cheers,

Piet







From: Lauren Sell <lauren at openstack.org<mailto:lauren at openstack.org>>
Date: Monday, May 30, 2016 at 7:39 AM
To: Pieter Kruithof <pieter.kruithof.jr at intel.com<mailto:pieter.kruithof.jr at intel.com>>
Cc: David F Flanders <flanders at openstack.org<mailto:flanders at openstack.org>>, Anne Gentle <annegentle at justwriteclick.com<mailto:annegentle at justwriteclick.com>>, Edgar Magana <edgar.magana at workday.com<mailto:edgar.magana at workday.com>>, user-committee <user-committee at lists.openstack.org<mailto:user-committee at lists.openstack.org>>, Ju Lim <julim at redhat.com<mailto:julim at redhat.com>>, "Sterrett, Craig" <craig.sterrett at intel.com<mailto:craig.sterrett at intel.com>>
Subject: Re: [SPAM] Re: [SPAM] [User-committee] Application Developer recruitment survey


On May 30, 2016, at 8:27 AM, Kruithof Jr, Pieter <pieter.kruithof.jr at intel.com<mailto:pieter.kruithof.jr at intel.com>> wrote:

Hi Lauren,

Don’t we have the day off?  ;^)

Yes, I’ve been traveling so just trying to get caught up :)

My comment was really that it would difficult for the foundation to add a significant number of questions to the semi-annual survey because it would be too long.  However, it would be a great idea to add a link to the semi-annual survey to a second app developer-focused survey.

I’m not sure it would significantly affect the length of the existing user survey since several of the questions you’ve developed might replace existing questions and the demographic questions are already covered. We would of course need to take a closer look, but I glanced through the survey monkey you developed last week for the Cloud Foundry Summit and thought it was a good start.

Totally agree that it could be left open indefinitely and allow the different teams to request data from the foundation.  My only concern is that there night be a bias towards developers that are specifically focused on contributing to the openstack community which introduces it’s own bias to the sample.

Getting the right folks to answer the app developer portion of the survey has been a challenge, but I think that’s going to be true with any survey we put together. We will definitely need to have a discussion about ideal respondents and promotion alongside survey development.

Did you want the OpenStack UX project to continue engaging with the application ecosystem WG?  Or does it make more sense for the foundation to develop the survey?

I’m not exactly sure what's happening between the app eco wg and UX team right now--and I certainly don’t want to put up road blocks--but yes we’d like to be involved along with the user survey team. I think it’s fine to use the survey monkey you’ve developed to start testing questions and gathering information in the near-term with the goal of incorporating that learning and pushing all feedback into the user survey over the next cycle of two.

Best,
Lauren


Cheers,

Piet



From: Lauren Sell <lauren at openstack.org<mailto:lauren at openstack.org>>
Date: Monday, May 30, 2016 at 7:16 AM
To: Pieter Kruithof <pieter.kruithof.jr at intel.com<mailto:pieter.kruithof.jr at intel.com>>
Cc: David F Flanders <flanders at openstack.org<mailto:flanders at openstack.org>>, Anne Gentle <annegentle at justwriteclick.com<mailto:annegentle at justwriteclick.com>>, Edgar Magana <edgar.magana at workday.com<mailto:edgar.magana at workday.com>>, user-committee <user-committee at lists.openstack.org<mailto:user-committee at lists.openstack.org>>
Subject: Re: [SPAM] [User-committee] Application Developer recruitment survey

Hi Piet,

On May 27, 2016, at 2:34 PM, Kruithof Jr, Pieter <pieter.kruithof.jr at intel.com<mailto:pieter.kruithof.jr at intel.com>> wrote:

-1 There is a significant amount of misaligment on the goals for the two efforts

Application Developer Recruitment Survey:  The intent of this survey is to create a panel of users that are willing to participate in user research on behalf of the community.  In this case, the survey questions are specifically intended to enable the different working groups/projects recruit folks for their studies.

Application Developer Study:  The goal of the study is to generate deeper understanding of app developers for the community.  I may have caused some concussion by referring to this as a “survey” rather than indicating that the team haven’t landed on a specific methodology.  It may turn out that the team really needs a series of interviews to generate more qualitative data…we don’t really know at this point.

The feedback that I’ve received is that the semiannual user survey doesn’t provide enough information about app developers which kind of drove the need for additional research.  We could consider rolling additional questions into the semiannual survey, but the impression I get from Heidi is that it’s already too long and the likelihood of adding significantly more questions is unlikely.

That’s not the case. We’re very interested in improving the app developer section of the survey and are actually anxious to get input from the appropriate app ecosystem or UX working groups. We’re open to changing or killing the current questions and adding new questions. We of course need to keep an eye on survey length, but that’s true no matter where it lives.

Over the long term, I hope the semiannual survey will meet both of your goals if we are able to update the questions and include a tick box to opt-in for additional studies (in the same way we’ve set it up for you in the operator / deployment portion). We’re also looking at making the deployment survey open year round and could consider the same for the app developer portion of the survey (with a direct link) for use at events outside of the main user survey push.

Thanks for all of your work!

Piet


From: David F Flanders <flanders at openstack.org<mailto:flanders at openstack.org>>
Date: Friday, May 27, 2016 at 1:17 PM
To: Anne Gentle <annegentle at justwriteclick.com<mailto:annegentle at justwriteclick.com>>
Cc: user-committee <user-committee at lists.openstack.org<mailto:user-committee at lists.openstack.org>>, Edgar Magana <edgar.magana at workday.com<mailto:edgar.magana at workday.com>>, Pieter Kruithof <pieter.kruithof.jr at intel.com<mailto:pieter.kruithof.jr at intel.com>>
Subject: Re: [User-committee] Application Developer recruitment survey

+1 thank you Anne for translating.  Main User survey is what this effort should build to long term imho.
On 27 May 2016 11:57 AM, "Anne Gentle" <annegentle at justwriteclick.com<mailto:annegentle at justwriteclick.com>> wrote:
I think what Flanders is saying is that there should not be a second "user survey" and there should remain questions for app devs incorporated into the main user survey.

There could definitely be a set of interviews as part of this recruiting effort. Recorded interviews would be helpful in figuring out which communities appdevs/devops are already participating in, so that we know where to listen and participate.

I'm currently thinking you can leave the TC name out of the call-to-participate, as we're merely supporters not do-ers in this effort.

Anne

On Thu, May 26, 2016 at 8:15 PM, Kruithof Jr, Pieter <pieter.kruithof.jr at intel.com<mailto:pieter.kruithof.jr at intel.com>> wrote:
Moving from TC to UC

Hi Flanders,

You lost me a bit, but this is what it feels like you’re saying:

  1.  Recruit app developers to create a pool of folks that are interested in participating in user research on behalf of the community.
  2.  Conduct a series of interviews (n=~8) to help us understand what kinds of questions we should include as part of the app developer survey
  3.  Based the interviews, design and distribute a survey to app developers.

One quick point. Part of me is wondering whether we should do a series of ~16 individual interviews rather than a survey because it feels as though we’re really trying to get qualitative data.  The why’s rather than the what’s.  Or maybe…conduct eight interviews, distribute a survey and then conduct another eight post-hoc interviews to add context to the data collected from the survey.

Lemme know if this makes sense.  I’m OK with the scale of the research effort increasing because app developers are so important to us.

Cheers,


Piet

From: David F Flanders <dff.openstack at gmail.com<mailto:dff.openstack at gmail.com>>
Date: Thursday, May 26, 2016 at 11:53 AM
To: Pieter Kruithof <pieter.kruithof.jr at intel.com<mailto:pieter.kruithof.jr at intel.com>>
Cc: Thierry Carrez <thierry at openstack.org<mailto:thierry at openstack.org>>, "openstack-tc at lists.openstack.org<mailto:openstack-tc at lists.openstack.org>" <openstack-tc at lists.openstack.org<mailto:openstack-tc at lists.openstack.org>>, Heidi Joy Tretheway <heidijoy at openstack.org<mailto:heidijoy at openstack.org>>, Edgar Magana <edgar.magana at workday.com<mailto:edgar.magana at workday.com>>
Subject: Re: Application Developer recruitment survey

My only one request would need that this effort build towards having questions generated for the main user survey as being coordinated by the AppEco-WG and overseen by Edgar on the UC.
As to, the iterations would look something which supports Piet's UX methods:
1.) Short survey to recruit appDev
2.) Interviews with half a dozen appDev to a.) Generate info re appDev UX, and b.) generate (thematic analysis of interviews) questions for future user survey questions to be shared/circulated with AppEco-wg for refinement.
3.) Agreement with UC on which questions will go into the annual main survey.
@Piet please do amend as you are fit re UX methodology.
Kind Regards,
Flanders
On 26 May 2016 7:16 AM, "Kruithof Jr, Pieter" <pieter.kruithof.jr at intel.com<mailto:pieter.kruithof.jr at intel.com>> wrote:
Committee,

OpenStack UX, User Committee and the foundation’s marketing team have been working on a short survey to recruit application developers.

The question for the techncial committee is whether we are able to use your name in the introduction for the survey:


"The OpenStack Foundation and Technical Committee are distributing a survey to help the open source community understand application developers and build more relevant products. The survey should take no more than ten minutes to complete.

As thanks for your time, three people will be randomly selected to win a $100 gift card.

https://www.surveymonkey.com/r/appdev-survey”


The goal of the recruitment survey is to generate a pool of application developers who are interested in participating in user research activities on behalf of the community.  The survey contains eight questions that can be used to screen potential participants for upcoming studies i.e. “We need to recruit eight participants with at least three years experience developing applications on a public cloud for a usability study.” App developers are difficult to recruit because they are less likely to attend community events or leverage the OpenStack IRC channels which is why we’re making a specific effort to recruit them.

The survey includes questions for the following areas:

* Company Type (Academic, ISV, etc)
* Company size
* Location of respondent
* Years developing apps
* App development languages
* Public clouds used by respondent (if at all)
* Private clouds used by respondent (if at all)
* Whether they participate in the community

We are trying to keep the survey as short as possible because we’re trying to recruit as many application developers as possible.  As Flanders noted, it’s challenging to have folks complete a survey at a conference or summit if they need to stand there for more than a couple of minutes.

The data collected from the survey will be managed by the foundation and email addresses for the respondents will not be shared with the community.

Let me know your thoughts.  In the meantime, we can always swap-out "OpenStack Foundation and Technical Committee” with “OpenStack UX project”.

Thanks,



Piet


--
Piet Kruithof
Sr User Experience Architect, Intel OTC
PTL, OpenStack UX Project

Mobile: 512 576-2844<tel:512%20576-2844>
IRC: piet

_______________________________________________
User-committee mailing list
User-committee at lists.openstack.org<mailto:User-committee at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee




--
Anne Gentle
www.justwriteclick.com<http://www.justwriteclick.com/>
_______________________________________________
User-committee mailing list
User-committee at lists.openstack.org<mailto:User-committee at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/user-committee/attachments/20160530/4f5db14d/attachment-0001.html>