2. NEM201 Week 4

3. Project Plan Create and complete outstanding items. 01. Front Cover 02. Document details 03. Scope Document 04. Technical Design 05. Creative Design 06. Project Timelines: Do this first 07. Risk Management Plan 08. Quality Assurance Plan 09. Communication Management 10. Process Management

4. Project Plan 01. Front Cover –Document Name –Project Name –Purpose of Document –Authoring Team’s Name –Intended Recipient’s Name –Date –Version

5. Project Plan 02. Document details –Name –Version –Background to the Project Discuss Brief Discuss Stakeholders (i.e. who can sign-off and when) –Purpose of the Document –Structure and Content Overview –Glossaries

6. Project Plan 03. Scope Document 04. Technical Design –Emphasise Functionality 05. Creative Design –Emphasise Functionality 06. Project Timelines: –WBS –Gantt Charts –Task Network Diagram

7. Project Plan 07. Risk Management Plan –What risks currently exist? –In addition to what Risk Management Strategies you already have in place, consider the following: Avoidance Contingency Planning Transference Acceptance

8. Project Plan 08. Quality Assurance Plan –Documentation Quality Strategies –Personnel Control Strategies –Functionality Testing Strategies –Usability Testing Strategies –Bug Tracking and Resolution Strategies

9. Project Plan 09. Communication Management –Project Team Organisational Diagram –Detail how you communicate when everything is on track (i.e. Super-Group Meetings, Sub-Group Meetings, Entire project Team Meetings, Client Meetings, Email etc. ) –Detail how you communicate when things go off track or when there is an emergency

10. Project Plan 10. Process Management List all project processes: –Meeting types and times –Internal and external sign-off processes –New Work, Change Request and Impact Analysis Processes and Forms –Filing Systems and Naming Conventions –Task Allocation Structure –Peer Review Process –Dispute Resolution Process –Post-Implementation Review

11. Work Breakdown Structure (WBS) Create WBS

12. Work Breakdown Structure (WBS) What comprises it: –A list of all Project Objectives –A list of all Phases that must be completed in order to meet each Project Objective –A list of all Tasks that must be completed in order to meet each Objective’s Phase –Details on which resources are needed to complete each Task –Details on how long each Task, Phase, and Objective is expected to take

13. WBS Design: Rules The diagram does not have to be symmetrical Each box is a summary of the boxes in the levels below it A numbering convention should be adopted The sum total of boxes must represent the complete project: You can leave nothing out Ask yourself: When all the deliverables we have listed are completed will the project be finished? The entire project team should be involved in developing the work breakdown structure

14. Work Breakdown Structure (WBS) Warning: –You must focus on the Objectives more than the Tasks when using your WBS to guide your work effort. –It is possible to perform all of your Tasks without meeting your Objectives if Tasks are not considered with Objectives in mind.

15. When completed, you should review the work breakdown with the client. This is to ensure that it is complete and that it addresses their specific concerns. This will happen at the end of next week’s lecture.

16. WBS Add-on for MS Project http://www.criticaltools.com/download.htm

17. Create Network Diagrams

18. Quality Plan QA is dealt with in detail in another module. The purpose of QA in this module is purely to generate an awareness of the need for QA within an organization or project team. You have implemented standards and procedures to maintain quality, but these standards and procedures are not as strict as what would be expected in industry (or your QA module).

19. Quality Plan: Documentation For example: –Directors approve document contents before they are passed on to the PM –PM approves document content before it is submitted to the client –QA approves global document styles and document formatting before it is submitted to the client –QA manages version control

20. Quality Plan: Personnel Control For example: –Personnel productivity is monitored via timesheets –When productivity decreases, timesheets should be measured against Gantt Charts to discover points-of-failure –Personnel attendance can be monitored via a roll-call at meetings

21. Quality Plan: Functionality Testing Determine a list of the requirements for functionality testing e.g. –Website links work –Game controls work Determine the resources for functionality testing e.g. –Sub-groups Determine the structure for functionality testing e.g. –Sub-groups test for functionality, then sub-group directors approve the test results and pass on to QA

22. Quality Plan: Usability Testing Determine a list of the requirements for Usability testing e.g. –User can find the information they need in the Game Manual quickly –User can navigate around the website quickly Determine the resources for Usability testing e.g. –Users independent of the authoring sub-group Determine the structure for Usability testing e.g. –Users independent of the authoring sub-group pass the test results on to QA for approval

23. Quality Plan: Bug Tracking and Resolution When a bug is found during Functionality or Usability testing, consider how bug resolution will take place e.g. –QA passes list of bugs onto PM who reassigns tasks as required.

24. Creating Schedules in MS Project What is expected: –Phases (indent Task Groups to add to a phase) –Task Groups (indent Tasks to add to a Task Group) –Tasks: Name Start and Finish Dates Priorities Any relevant Constraints Any relevant Dependencies –Resources –Milestones