R012

R012

1. SMART Goals

   • Specific
     • For this you have to be specific with your goal, it must be able to be done and to far out to be difficult to get. It must be clear to other people in the project as well who has the basic knowledge of the project.                 
     • Why
     • Who
     • Where
     • What
     • Which
   • Acheviable
     • You must identify the goals that are most important. Then you must develop your skills, abilities, financial.
   • Measureable
     • You should know if the goal is able to be done and how far you are to complete. Make sure you measure your progress till you have finished.   
   • Timely
     • It should spread, there should be enough time to achieve the goal, not too much time, which can affect project performance.
   • Realistic
     • It has to be not difficult to do, it has to be "realistic". It would be within the availability of resources, knowledge and time.

2. The Project Life Cycle

   • Predictive Life Cycle
     • 1.Plan
     • 2. Design
     • 3. Implement
     • 4. Test
     • 5. Release
   • Adaptive Life Cycle
     • 2. Plan
     • 5. Access/ Test
     • 1. Assemble
     • 4. Check
     • 3. Design
   • Stages of The Project Life Cycle
     • 1. Initiation
       • Inputs
         • User Requirements
           • Some requirements may be specific.
           • The reports that are generated by the product must fit onto the company headed paper.
           • The length of the video to be embedded in the product must last for 3 minutes and include the company contact details at the end.
           • All queries in the product must require user input.
         • User constraits
           • Timescale: the start and end date for the project. The end date is when the deliverable product is released to the client.
           • Budget: the amount of money that can be spent during the project. If the project is planned in enough detail then the budget should not be exceeded. There are, however, always exceptions to this.
           • Hardware: the hardware that the client wants the deliverable product to be installed or run on. The hardware to be used during the creation of the product may also be defined by the client.
           • Software: the software that the client wants the deliverable product to use to run on. The software to be used during the creation of the product may also be defined by the client.
       • Outputs
         • Feasibility report
           • The feasibility report includes the answers to all the questions that are asked during the initiation phase. The report can also include different solutions for the client.
           • The client can then select the solution they would like to be created.
           • The feasibility study will also consider the constraints and requirements which have been provided by the client. These need to be realistic if the project is to go ahead.
           • If any of the requirements or constraints are not realistic, then the project manager can liaise with the client to create new requirements and constraints.
         • Legislation implications
           • The legislation implications will need to be considered at the start of the project. Which Acts, legislation and regulations need to be considered will depend on the type of product that is to be created::
             • If a website is to be created, then the project manager may need to consider the Copyright, Designs and Patents Act, if any images or photographs created by other people are to be used.
             • If a database is to be created which holds people’s personal contact details, then the Data Protection Act (DPA) will need to be considered by the project manager.
     • 2.Planning
       • This phase is key to successful project management and focuses on developing a roadmap that everyone will follow. This phase typically begins with setting goals. Two of the more popular methods for setting goals are S.M.A.R.T. and CLEAR
       • During this phase, the scope of the project is defined and a project management plan is developed. It involves identifying the cost, quality, available resources, and a realistic timetable.
       • The project plans also includes establishing baselines or performance measures.
       • These are generated using the scope, schedule and cost of a project. A baseline is essential to determine if a project is on track.
     • 3. Execution
       • This This is the phase where deliverables are developed and completed. This often feels like the meat of the project since a lot is happening during this time, like status reports and meetings, development updates, and performance reports.
       • Develop team
       • Assign resources
       • Execute project management plans
       • Task assignments are executed
       • Status meeting
       • Update project schedule
       • Procurement management if needed
       • Modify project plans as needed
     • 4. Iterative review / Final evaluation
       • This is all about measuring project progression and performance and ensuring that everything happening aligns with the project management plan.
       • Project managers will use key performance indicators to determine if the project is on track.
       • Project Performance: This monitors changes in the project. It takes into consideration the amount and types of issues that arise and how quickly they are addressed. These can occur from unforeseen hurdles and scope changes.

3. Data Protection Act

   • Second Principle
     • Purpose for which data are obtained and processed: This principle requires organisations to be open about their reasons for obtaining personal data and that what they subsequently do with the information is in line with the individual's expectations. if you are not required to notify and the processing is for an obvious purpose the specified purpose should be taken to be the obvious purpose.    
   • Third Principle
     • Adequacy and Relevance of data: Only the minimum amount of information required to properly fulfil the purpose is held by the data controller. Information cannot be held on the basis that it might possibly be useful in the future.    
   • Fourth Principle
     • Accuracy of Data: Inaccuracies in certain types of information, can have wide-ranging meanings for the data subject. Data are defined as being inaccurate if they are not true or misleading as to any matter of fact.
   • Fifth Principle
     • Time for keeping data: There should be a system in place for removal of different categories of data from systems when, for example, only a limited record needs to be taken. Information does not therefore have to be deleted once a relationship ends if it necessary to keep that information for further purposes.
   • Seventh Principle
     • Measures Against Misuse and Loss of Data: Security of personal data is a matter of public concern.  
   • First Principle
     • Fair and lawful processing:  Fair Processing Ensuring fairness in everything you do with people's personal details is central to complying with a data controller's duties under the Act.   You must have legitimate reasons for using, collecting, sharing someones personal data. Be open and honest about how you intend to use the information. nsure that people are not misled or deceived about the use of their information  
   • Eight Principle
     • Transfer of Data Abroad:   
   • Sixth Principle
     • The data subject has the following rights: Right of access to personal information known as a Subject Access Request (SAR)  

Images and files in the map