Download
1 / 18
180 likes | 319 Views
Project Management. ITS Version. What is Project Management?. It is a method by which projects are more easily managed. Projects are developed using the following processes: Define Plan Design Implement Close/Evaluate. 1a. Define Phase – Problem Identification.
E N D
Project Management ITS Version
What is Project Management? • It is a method by which projects are more easily managed. Projects are developed using the following processes: • Define • Plan • Design • Implement • Close/Evaluate
1a. Define Phase – Problem Identification You cannot begin a solution if you do not have a clear idea of the actual problem. Proceeding with the development of a product without careful planning and identification of a problem can waste precious time and money. Identifying Problem - Example The Coca-Cola company specialises in selling carbonated soft drinks. Their most famous beverage is of course Coke, but they also sell Sprite, Fanta and Lift. The company has a physical presence in most countries around the globe… Coca-Cola wants to overhaul their current website and develop a new design for the company. The site needs to provide info such as company profile, products, etc. for consumers as well as potential business clients. The current website has been in existence for 2 years and has become stale. The new site will be more dynamic, vibrant, colourful and will be updated on a more regular basis. The website will utilise the following features: - Easy to navigate menu interface - Accessibility will be integrated to assist users who have disabilities - Etc. - Etc. It is believed that the increase in traffic to the website will increase the profile of the company, and hence increase the sale of their products.
1a. Define Phase – Problem Identification • i) Background information – This provides a context from which the problem needs to be resolved. • If you are creating a website for Coca-Cola, you might want to provide some information on it’s history, when it was established, what products they provide, etc. • ii) Problem specification – You must explain what the actual problem is, thereby providing a reason for the development of your product. • It could be that the current website is not exciting or lacks sufficient interactivity for its users. • It might also lack accessibility features that does not compensate those users who have disabilities. • iii) Solution – Describe the product that you are developing and its features. • The website might have the following features: • Sound effects and music, colour, animation. • The interface will be easy to use. • Accessibility will be integrated into site.
1b. Define Phase – Goal There should be only ONE overall goal that the project is trying to achieve. What is the overall goal of the project? Goal – Example To plan, design, implement and test a vibrant and accessible website for Coca-Cola using Fireworks, Dreamweaver and Flash by June 30, 2004.
1c. Define Phase – Objectives • What must be done so that the overall goal can be achieved? • Use the SMART model when determining your objectives. Each objective must be: • Specific • Measurable • Assignable • Realistic • Time-related Objectives - Example 1. Research the Coca-Cola company (profile, products, etc.) by March 1, 2004. 2. Interview the Public Relations of Coca-Cola Australia to determine website contents by March 3, 2004.
1d. Define Phase – Assumptions & Risks • Each objective will have a relevant assumption and risk associated with it which will impact on its success or failure. For each objective you must ask: • What risks are associated with any of the objectives listed? • What assumptions have to be made for the objective to be fulfilled? Assumptions & Risks – Example 1) Research the Coca-Cola company (profile, products, etc.) by March 1, 2004 A&R: It is assumed that the information about the company will be freely available from their website and company brochures. The risks are that the information might be difficult to access and not freely available as first thought. The information might also be dated.
2. Plan Phase • Identify project activities • Objectives are broken up into smaller, more manageable activities • Estimate time and cost • How long will the activity take and what will it cost? • Sequence activities • Some activities will need to happen before certain activities. • Determine resources • What will you need (paper, electricity, etc.) for the activity • Formal proposal • A formal letter to the client summarising the activities to be undertaken and the overall costing
3. Design Phase Develop a number of preliminary designs for the client and get them to choose the most suitable one. Produce rough sketches to illustrate the different designs of your website. Produce detailed and annotated storyboards for your chosen design. The design should show where pictures will appear, what headings you will use, fonts, columns and white space. The design should be as detailed as possible. Show the design to the end-user and ask them to comment on it.
3. Design Phase In this phase include the storyboards and a flowchart that shows how a user navigates through your presentation. The storyboards should include detailed list of all the proposed video clips, images, animations, sounds and music.
3. Design Determine what changes you will make as a result of these comments. Devise a test plan. In other words, describe how you will test the different components of your site or system.
4. Implementation Phase The actual development of the product. Provide screen shots to illustrate the development of the system. Include annotations (comments) to explain the various components.
4. Implementation Phase Complete the test plan. You should document any problems that you came across during the implementation of the product. Complete alpha testing (testing that is done by the developer to find any ‘bugs’ in product) Complete beta testing (further testing done by other groups of people, e.g. 3rd party users to find other potential ‘bugs’)
5. Close/Evaluation Phase • Evaluate every objective • Were they achieved? If yes, how. If no, why not. • What problems (technical, etc.) were encountered? • Explain changes to original design. • Supply evidence that the end-user has seen your work and supplied comments. • Say what you think of the end-user's comments. • How could your work be improved/extended? • User-manual with screen shots explaining the use of the product.
