Research And Evaluate A Suitable Company

07-12-17 cheapnisha 0 comment

Research And Evaluate A Suitable Company

1.1 research and evaluate a suitable company

Criteria Company 1 Company 2 Company 3 Company 4 Local shop/bar/restaurant
Travel
Salary
Flexible
Type of job
Technical skills expected
Soft skills expected Good time management

Good problem solving skills

Benefits

 

Rating of the company Reasons
Company 3
Company 1
Local shop

1.2 proposal web design / CV

Name
Job Title Web design
Duties
Soft skills
Technical skills
Brief introduction to your self
Reason for the work experience
Future plan
Supervisors: roles and responsibilities of academic and industrial mentors

Proposal for database /CV

Name
Job Title Database
Duties
Soft skills
Technical skills
Brief introduction to your self
Reason for the work experience
Future plan
Supervisors: roles and responsibilities of academic and industrial mentors

Select a proposal for email to employers / Communicate with employers

Your final agreed proposal

1.3 recognise the business constraints on the work experience offered

Business constraints Explanations ( Citations and reference required ) How I will manage ?
need to be fully trained,
adherence to quality systems
health and safety considerations
supervision time,
workload,
customer satisfaction
limited staffing
cost of materials

2.1

Identify a suitable job title

Prepare a job duties and responsibilities of the job

Apply MoSCoW to arrange the duties based on priorities of the task

 he categories are typically understood as:[3]

Must have

Requirements labeled as Must have are critical to the current delivery time box in order for it to be a success. If even one Must haverequirement is not included, the project delivery should be considered a failure (note: requirements can be downgraded from Must have, by agreement with all relevant stakeholders; for example, when new requirements are deemed more important). MUST can also be considered an acronym for the Minimum Usable SubseT.

Should have

Requirements labeled as Should have are important but not necessary for delivery in the current delivery timebox. While Should haverequirements can be as important as Must have, they are often not as time-critical or there may be another way to satisfy the requirement, so that it can be held back until a future delivery time box.

Could have

Requirements labeled as could have are desirable but not necessary, and could improve user experience or customer satisfaction for little development cost. These will typically be included if time and resources permit.

Won’t have (this time)

Requirements labeled as won’t have been agreed by stakeholders as the least-critical, lowest-payback items, or not appropriate at that time. As a result, won’t have requirements are not planned into the schedule for the next delivery time box. Won’t haverequirements are either dropped or reconsidered for inclusion in a later time box. (Note: occasionally the term would like to have is used; however, that usage is incorrect, as this last priority is clearly stating something is outside the scope of delivery).