How can organizations ‘crowdsource‘ while still ensuring reliability/quality? I’ve discussed why software development is the first place to look when thinking about an issue that is relevant to every business.
The Business Readiness Rating (BRR) represents one effort to standardize appraisal of crowd-based software development. I’m posting the twelve criteria the BRR employs, and highlighting a few that speak to the unique dynamics of crowdsourcing:
Functionality – does the software meet user requirements? Usability – is the software intuitive / easy to install / easy to configure / easy to maintain? Quality – is the software well designed, implemented, and tested? Security – how secure is the software? Performance – how does the software perform against standard benchmarks? Scalability – can the software cope with high-volume use? Architecture – is the software modular, portable, flexible, extensible, and open. Can it be integrated with other components? Support – how extensive is the professional and community support available? Documentation – is there good quality documentation? Adoption – has the software been adopted by the community, the market, and the industry? Community – is the community for the software active and lively?
Professionalism – what level of professionalism does the development process and project organisation exhibit?
In the future, we’ll consider whether/how reliability and crowdsourcing can be balanced in other product development processes.