Review of Jacob Hobbs' Proposal

According to mentioned before reviewing scheme, here is a review of Jacob Hobbs' proposal

Summary of the proposal:

The proposed system is an automated management system that automates online game routine tasks. Farmville is an example of the such gave was given, where simple routine and boring tasks as collecting and planting plants, would be automated for end users.


Ratings:

Syntax = 5
Plausibility = 5
Support = 4
Novelty = 4
Stakeholders = 5
Scope = 4
Profitability = 4
Legal = 4
Security = 3
-------------------------------------------
Total score of the document = 4.22


Clarification on ratings:

• Syntax

Clearly formed ideas, professional language, and great grammar. I didn't see any typos nor grammatical errors. The minor detail, I didn't really like reference to automation tool as a bot, it is a slang afterwards, and it may scary some of the reviewers that have really bad associations with bots. Or may be it is just me, who really dislike the actual bots ;)

• Plausibility

I really liked an example presented as a potential UI look. Project seem to have great perspective, as well as the proposer seem to have the right set of qualifications for leading the project to the end.

• Support

Mainly most of the document had really great supported information. However, promised future salary to the involved stock holders and developers are somewhat arbitrary and would need some better support.

• Novelty

Unfortunately, Automation Labs had tried something similar, but that made me somewhat concerned why they didn't succeed in their product. I search for their name on google and any potential lawsuits. No lawsuits were found, however, they were wrongly blamed for violating privacy security of the users, which what might have put their success to end. This is something to be concerned with any product, especially if there were some similar attempts.

• Stakeholders

Developers would be the main stakeholders of the product, with some other potentially involved stakeholders.

• Scope of the project

Scope was somewhat unclear about features of the final product. To be more specific, on page 5 of the proposal, the author had referred to configuration settings as "[o]nce everything is configured", which was really broad and needs to be more specific, so the reviewer is aware of what to expect from the final product. The configuration settings in this particular automation tool are the main key in determination of the final product's capability.

• Profitability of the project

High profits promised in return to involved developers and stakeholders. However, the numbers of the promised/expected returns would need some better concrete support.

• Legal

No legal issues were discussed. Personally, I would be concerned about legal rights of Zynga as a main developer of majority of the online multiuser games for the social networks such as Facebook and Myspace. Some support seems to be needed to assure reviewer of legal intentions of the proposal's product.

• Security Concerns

Did see any major security concerns, other than may adding some greater detail about the how would the product provide the end user with the basic security measures. As well as put some thought about securing the licenses of the final product.

In overall, the product does have great potential beyond this class's time limit. The author of the proposal has great set of skills for leading proposed project to its successful end.