Hello,
In the JEMS Maturity Matrix we would like to have measures describing software
productization. I'm not entirely sure what should be listed here, but I've got
some ideas and would appreciate your comments.
I like the following, short article about productization:
Effective productization in open source projects
anonymous wrote :
| Productization means turning the software into a "whole product" --
providing all the pieces that are necessary for mainstream users to get value from the
software. This includes documentation, support and training. It also involves some type of
branding (how people identify the product, like logos and company image).
|
Let's say we are measuring single project, mainly from user's point of view. We
can consider:
- available documentation (manuals, wiki, FAQ, javadoc),
- professional support,
- training,
- if it is packaged for download,
- easy installation (web installer or installation manual),
- JEMS integration,
- user forums (?, as a kind of support),
- project version.
These are mainly booleans, but considered together they can give you some sense of how
mature project is.
Metrics listed above could take necessary data from the project.xml files. Some info is
already present (like JEMS integration), rest would be easy to include (like links to
docs) and could be useful in the other contexts as well.
Also, project branding was mentioned above. It seems hard to measure how people recognize
or appreciate the product. Idea that came to my mind was kind of google metric (for
instance, how many web pages link to the product page), but it might be difficult to do it
fairly.
Project popularity could be also measured with number of website visits. Or, maybe, we
should introduce metrics based on polls?
I wonder what's your opinion.
Cheers,
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968162#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...