Tag: Auburn


microISV Research Alliance (Update)

June 18th, 2010 — 8:11am

Yesterday, Dr. Umphress and I met with Susan of Auburn University’s Office of Technology Transfer (OTT). The meeting produced excellent results. I’ve learned that the OTT does its best work when you meet with them early, like we did. Susan pointed out several important considerations that we’ll keep in mind as we go forward.

First, the Alliance does not need to be an independent legal entity; It can simply exist as a “persona” of one of the member universities. Since, at the moment, Auburn is the only member, then Auburn will in essence be the Alliance. Once I move on to another university, I’ll move Alliance operations there. In fact, having the Alliance as an operation under a university gives us several benefits, including having many administration functions at our disposal.

Second, we don’t have to worry about intellectual property rights being restricted. Since Dr. Umphress is acting on behalf of Auburn University, they are co-owners of any intellectual property we generate. On the other hand, since I am not being paid by the university or using significant university resources, I fall outside the intellectual property restrictions and am, therefore, a co-owner. In other words, from a legal standpoint, Dr. Umphress, Auburn University, and I all have right to do whatever we like with the generated intellectual property. Of course, from an ethical and professional standpoint, we will act as collaborators and agree on the uses of the intellectual property, so as to eliminate surprises.

Lastly, we talked a great deal about money. The discussion brought into focus several vague ideas I’d had about research funding. Let me break them down.

Option 1 – Corporate Grants – A private business may choose to “invest” money in our research in exchange for things like licensing rights, steering committee membership, early looks at data or report, etc. This is very common throughout the university system and is the easiest to formalize. The difficult part is negotiating with the business on what they’ll get for their money. The other challenge is deciding exactly how to divide up the money among member labs.

Option 2 - Membership Dues – Individuals in the microISV community might be encourage to “join the Alliance” for a small membership fee. This would be something akin to a micro-corporate grant. They would get access to certain benefits like data access, free publications, conferences, etc. I both like and dislike this idea, since I’d like the Alliance to be as inclusive as possible. Besides, microISVers have precious little money to start with.

Options 3 – Angel Investors – This would be the simplest, since we would be getting a grant with few or no strings attached.

Option 4 – Venture Capitalist Grants – When I spoke with Bob Walsh, he indicated there are more than a few VCs looking for the next Twitter or Facebook. I believe the biggest challenge VCs face is locating a high potential microISV before it had that explosive growth, because, once it explodes everyone wants in. If we build a strong community of microISVers, VCs may want access to that community and may be willing to provide grants for that access. Of course, this is all speculation at this point, since I haven’t actually spoken to any venture capitalists about it.

So that’s a quick summary of our meeting. As it stands, the only remaining hurdle to a full launch of the Alliance is getting IRB approval of the Pain Point survey. Once that’s done, we’re full steam ahead!

Comment » | mISV, micro-ISV, μISV

microISV Research

March 18th, 2010 — 7:18pm

I’m midway through my first year at Auburn University and I’m currently focused on finding a research area for my PhD dissertation.  For now, I’ve settled on microISVs (also known as mISVs or μISVs), from the technical aspects of writing code to the business operations.

The field of topics surrounding microISVs are not unique, but their implementation likely is.  I’ve put together a list of research areas to try and narrow down the possibilities.  As of this moment, the front-runners include process- and “tool stack”-related topics.  I will be meeting with my temporary advisor, Dr. David Umphress, on Friday to get a fresh perspective.

I would also like to survey the microISV-ers on the Business of Software forum to get their thoughts.  I will, however, hold off on moving on that until I get a better idea of what I would like to learn.

At a minimum, this will provide fertile ground for my dissertation and lead me further toward obtaining my PhD.  On the other hand, I can envision this growing far beyond a single publication, or set of papers.  I believe this could conceivably evolve into a sort of micro-ISV Research Center, which supports and grows new and existing microISVs.  I guess time will tell…

Comment » | mISV, micro-ISV, μISV

A Critical Examination of Evidence-Based Scheduling

December 6th, 2009 — 1:53pm

As part of the class I’m taking on software process, I was required to write a short paper on a course-related topic.  The topic I chose was Joel Spolsky’s Evidence-Based Scheduling (EBS) technique.

I approached the topic with a critical eye toward its aspects, strengths, and weaknesses.  Hopefully, this could serve as an unbiased reference for someone interested in the topic of task scheduling, EBS, and Monte Carlo style simulations.  Keep in mind that this paper was not written to be submitted to a journal publication and, therefore, is more of an expert opinion on the subject, rather than a definitive piece of research.

The paper is available online and as a PDF.

Note: The online version has a few formatting problems, for which I blame Microsoft Word, since I let it do the conversion.  The PDF version is the truest rendering of the work.

2 comments » | Software

First Week of School

August 25th, 2009 — 8:46am

So the first week of school at Auburn as a PhD student has left me with a few new accomplishments under my belt.

  1. Six minutes into my first (ever) PhD class, I derailed the professor’s train of thought with my cell phone ringing.  Oh yeah, he’s also the Department Head.
  2. I started learning a new programming language: Python.
  3. I got the swine flu.

All in all, I’d say things are starting off with a bang!

2 comments » | Off Topic

Back to top