Strengths
Low cost
Specific: No equipment and physical products required
Measurable: The finished design demonstrates the intended idea
Agreed upon: continually provide sketches of the development
Realistic: computer and paper based designs
Time based: week 13
Abundance of resources on creating web services and feature examples
Specific: Gain feature ideas from existing popular web services
Measurable: the features chosen adds to the products experience
Agreed upon: inspired by popular websites like digg.com, facebook, twitter etc.
Realistic: taking positive features and improving on lacking features of the current job sites
Time based: early development
Users interact directly with site
Specific: create social networking features
Measurable: Ability to vote, comment and submit data
Agreed upon:
Realistic: use existing comment template, search for voting code in php
Time based: week 7 – end of development
content is generated for us
Specific: Existing content in “careerhub” will feed our database
Measurable:
Agreed upon:
Realistic: limit entries to manageable amount (e.g. 50 jobs)
Time based:
Team member’s skills complement each other
Specific: two members works on html and css tasks while the third provide graphic design services
Measurable: Having tasks specific to skill levels done
Agreed upon: tasks match each member’s skills
Realistic: implementing our skills
Time based: end of each week
Weaknesses
Little experience in database coding
Specific: set aside time to familiarize with a database language (maybe php)
Measurable: create a sample database
Agreed upon: 2 members will go through a crash course
Realistic: The internet (tutorial sites), tutors and experienced help
Time based: 2 weeks
Time allocations may not be sufficient to cover all aspects planned
Specific: Lay out a team organizer. Specific tasks per member each week
Measurable: Each members reports back at end of week
Agreed upon: Team blog and calendar
Realistic: Google blogger and calander
Time based: Each weekend
Requiring technology we are not familiar with (search engine)
Specific: Use existing search engine, for e.g google
Measurable: Having a working search engine in the website
Agreed upon: Testing out google search with product
Realistic: google search engine, tutorial sites
Time based: by the end of 5th week
Non-native English speakers make it difficult especially in writing reports
Specific: each member does a round of proof reading
Measurable: external party read through and validate
Agreed upon: each member does at least one round of proof reading
Realistic: Members, external party and spell check
Time based: at least 1 day before due
Lack of knowledge on managing website
Specific: gain an understanding on web usability and marketing
Measurable: beta testing
Agreed upon: blog posts on survey and web beta testing result
Realistic: Books and resourses on web usability,
Time based: constant development stageOpportunities
Collaboration with university system
Specific: using data from careerhub, and featured inUQ website
Measurable: featured on UQ frontpage
Agreed upon: work with university staff
Realistic: IT staff of UQ
Time based: When basic features are working
Tutor’s experience
Specific: Attaining as much assistance in tutorial times.
Measurable: problem solved
Agreed upon: tutors and team
Realistic: Tutors
Time based: teaching hours
Low competition (dysfunctional links in current system)
Specific: create a working and engaging alternative to current system
Measurable: feedback from beta testing
Agreed upon:
Realistic: Research and testing on current system
Time based: end of development
Low possibility of gaming (abusing) the system
Specific: early stages, does not create a major impact on the system.
Measurable: focus on other aspects of project
Agreed upon: possibilities of abuse discussed
Realistic: research on current popular trends in social networking
Time based: early stages
People are familiar with increasing trends in social networking
Specific:
Measurable:
Agreed upon
Realistic
Time based
Threats
Little interest/ lack of publicity
Poor organization of data, may cause confusion for users/developers
Lack of feedback about jobs in UQ
Gaming/system abuse may happen in later stages
Identical website appears during development
RISKS
Scaling problems (crashing when a lot of users)
Viruses and hacks
Cross platform compatibility issues
Content is fully controlled externally (we don’t have a say)
Health/personal problems within team to halt production
No comments:
Post a Comment