BTEC First Diploma for ICT Practitioners

BTEC National Diploma/Certificate/Award for ICT Practitioners

Scheme of Work for IT Project – unit 4

Overview

Learning outcomes

On completion of this unit a learner should:

1 Understand how projects are specified and managed

2 Be able to plan an IT project

3 Be able to implement an IT project

4 Be able to test, document and review an IT project.

Num of hours (total hours) / Teaching topic / Delivery methods / Guidance
2 hours / Understand how projects are specified and managed / Whole-class teaching
Group work / Project specification: identification of stakeholders; business case requirements;specific objectives or deliverables; benefits and success factors; projectboundaries or scope; constraints; consideration of options; other eg ethicalissues, sustainable issues, understanding consequences of failure to hit deadlinesor produce product; risks and risk mitigation
2 hrs ( 4 in total) / Understand how projects are specified and managed / Group Teaching
Individual research / Project life cycles: eg defining and producing specification, planning and
designing, collecting information, implementing, completing and reviewing
2 hours (6 in total) / Understand how projects are specified and managed / Whole-class teaching
Individual Research / Project management tools: general planning and scheduling tools eg Gantt charts,PERT charts; critical path methods; specialised software packages eg MicrosoftProject
2 hours (8 in total) / Understand how projects are specified and managed / Whole-class teaching
Individual Research / Resources: information; people (expertise and responsibilities) eg project
managers, product developers, programmers, systems analysts; equipment orfacilities eg software, hardware; money
6 hours (14 in total) / Understand how projects are specified and managed / Individual work / Other issues: effects of changing external factors; monitoring progress; takingcorrective actions where necessary; communications; working within relevantguidelines (internal and external) and legislation; dealing with conflict; impact ofproject outputs on other systems eg staff, organisational structuresProject methodologies: benefits and drawbacks of formal methodologies;examples eg Prince2, Sigma, company specific
6 hours (20 in total) / Whole-class teaching
Individual or small
group research
6 hours (28 in total) / Be able to plan an IT project / Whole-class teaching
Practical work / Project plan: purpose; content eg identification of phases and activities,
timescales; review points; use of appropriate and available software eg projectmanagement packages, spreadsheets, drawing packages, graphics, databases
6 hours (34 in total) / Be able to plan an IT project / Whole-class teaching
Practical work / Detail of activities: potential for parallel or sequential processes, resources
needed for each activity; review points eg milestones, checkpoints, deadlines;collecting information
12 hr ( 46 in total) / Individual work
3 hours ( 49 in total) / Be able to implement an IT project / Practical Whole-class teaching
Group work / Design: use of appropriate methods to design a solution to the problem; designdocumentation
1 hrs (50 hrs) / Be able to implement an IT project / Individual / Implementation tools: appropriate choices made; use of appropriate software orhardware
1 hour (51 hrs) / Be able to implement an IT project / 1-1 tutorials / Deliverables: product eg software application, service, system; other deliverableseg user training; technical and user documentation
6 hours (57 hrs) / Be able to implement an IT project / Whole-class teaching
Individual or small
group research
Practical work / Monitoring: routine communications with stakeholders; interim reviews; use oflogbooks; routine updating of plan where necessary; others eg accessing
additional resources where necessary, reacting to unforeseen circumstances
3 hours (60 hrs) / Individual
Be able to test, document and review an IT project / Completing process: testing; documentation; review; handover and sign off; othereg arranging support
Be able to test, document and review an IT project / Functional testing of product: test data eg normal, extreme; structured ‘walk
throughs’; test plan or scheduleReview: against specification; identification of potential additional development
Be able to test, document and review an IT project / Review of project management: actual dates achieved for milestones comparedto planned dates with reasons for difference; actual use of resources comparedwith planned resources needed; others eg unanticipated external factors thataffected the project; validity of the tools used
Be able to test, document and review an IT project / Technical documentation: documentation as appropriate to the particular projectchosen
Be able to test, document and review an IT project / User guide: instructions on how to use the product or service; getting help; knownbugs; gaining and using feedback; other eg hardware or system requirements

DStainton/BTEC/ITProject/SOW/Nat