Project Workshops Project Planning 1. Project planning proper management is essential the responsibility of the student with the advice of supervisor.

Slides:



Advertisements
Similar presentations
University of Leeds Project Management Stuart Roberts School of Computing.
Advertisements

Final Year Project Workshops Workshop 1 – Planning Cornelia Boldyreff Department of Computer Science University of Durham.
Targets for the individual and the organisation By Rachel, Claire, Kirsten and Natalie.
for Computing Research Projects
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
CHAPTER 1 SOFTWARE DEVELOPMENT. 2 Goals of software development Aspects of software quality Development life cycle models Basic concepts of algorithm.
 Chapter 6: Activity Planning – Part 1 NET481: Project Management Afnan Albahli.
Systems Analysis and Design 9th Edition
W5HH Principle As applied to Software Projects
COMP2001 HNC Project. Project Characteristics A project must have: clear objectives planning & control resources assurance of quality.
Your Project Proposal.
Project Workshops Initial Preparation. 2 Final Year Projects A significant piece of individual and academic work A double module -- 20% of final mark;
Final Year Project Workshops Workshop 1 Planning.
MSc Dissertation Introduction
Lecture 3 Managing your project How? Milestones Deliverables Meeting tutors.
1 SOFTWARE PRODUCTION. 2 DEVELOPMENT Product Creation Means: Methods & Heuristics Measure of Success: Quality f(Fitness of Use) MANAGEMENT Efficient &
Chapter 5: Project Scope Management
Business Studies Grade 11.
Projmgmt-1/22 DePaul University Project Management I - Realistic Scheduling Instructor: David A. Lash.
Planning. SDLC Planning Analysis Design Implementation.
Capstone Design Project (CDP) Civil Engineering Department First Semester 1431/1432 H 10/14/20091 King Saud University, Civil Engineering Department.
Time Management.
The Project AH Computing. Functional Requirements  What the product must do!  Examples attractive welcome screen all options available as clickable.
INTRODUCTION Time management
© 2005 Prentice Hall14-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
© 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 5 Slide 1 Chapter 3 Managing the Information Systems Project.
Chapter 3 : Managing the Information Systems Project.
BRIEFING 1: FYP INTRODUCTION
 Probably the most time-consuming project management activity.  Continuous activity - Plans must be regularly revised.  Various different types of.
Project Planning with IT Y/601/7321
4th Phase : 4th Phase : CONTROL Why is control necessary? Because:  People make mistakes  External factors can have impact on the project  Requirements,
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights.
Project Management Chapter 3. Objectives Become familiar with estimation. Be able to create a project workplan. Understand why project teams use timeboxing.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
NAVCA Quality Award Andrea Allez Performance Improvement Manager Excellent service for local groups.
Lecture 4 Title: The Scope Management Plan
IT Project Management, Third Edition Chapter 6 1 Chapter 3: Project Time Management.
BIS 360 – Lecture Two Ch. 3: Managing the IS Project.
Software Project Management
Slide 1 Project Management Chapter 4. Slide 2 Objectives ■ Become familiar with estimation. ■ Be able to create a project workplan. ■ Become familiar.
T Project Review WellIT PP Iteration
INFO 424 Team Project Practicum Week 2 - Launch report, Project tracking, Review report Glenn Booker Notes largely from Prof. Hislop.
©Dr I M Bradley Doing the project and other things.
The System and Software Development Process Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Apply Quality Management Techniques Project Quality Processes Certificate IV in Project Management Qualification Code BSB41507 Unit Code BSBPMG404A.
CS3100 Software Project Management: Monitoring & Control 1 Software Project Management Week 10: Project Monitoring & control Ian Blackman.
Project Management Cross lifecycle Activity
Chapter Sixteen Managing Network Design and Implementation.
BSBPMG404A Apply Quality Management Techniques Apply Quality Management Techniques Project Quality Processes C ertificate IV in Project Management
Chapter 3 Managing the Information Systems Project
Project Management Inspections and Reviews 1 February.
Project 1 (CGNB 413) Briefing
Project Time Management
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Creating the Work Breakdown Structure. INFO 638Lecture #22 WBS The goal of the project should be accomplished when all tasks in the WBS are completed.
Slide 1 CS 310 Ch5: Project management What do you think is involved? Proposal writing Project costing Project planning and scheduling Project monitoring.
BSBPMG501A Manage Project Integrative Processes Manage Project Integrative Processes Project Integration Processes – Part 2 Diploma of Project Management.
Project Planning A2 ICT Edexcel. Learning Objective To look at ways of breaking down a project into manageable stages To produce a project plan with suitable.
1 Chapter 2 SW Process Models. 2 Objectives  Understand various process models  Understand the pros and cons of each model  Evaluate the applicability.
BSBPMG503A Manage Project Time Manage Project Time Project Time Processes Part 2 Diploma of Project Management Qualification Code BSB51507 Unit Code.
Chapter 3 Managing the Information Systems Project
Project Management MGT 30725
Chapter 6: Database Project Management
Chapter 2 SW Process Models
Project Management Process Groups
Building a relationship with your supervisor
Importance of Project Schedules
Project Management.
Project Workshops Introduction.
Presentation transcript:

Project Workshops Project Planning 1

Project planning proper management is essential the responsibility of the student with the advice of supervisor management involves: –preparing a plan –monitoring progress against the plan –time planning: roughly 16 hours per week –basic, intermediate and advanced deliverables 2Project Planning

Planning Decomposition of the basic deliverable into a partially ordered network of components, to help prioritise tasks and define ways of making initial rapid progress. Consider time management to allow you to schedule your activities in Term 1 and to raise any foreseeable problems with supervisors. 3Project Planning

Planning Your Project Identify the key tasks involved in your basic deliverables Order on those tasks and any new skills you think you will need to do the project successfully. Use GANTT or PERT charts Important, in each case to state the project goals and what your basic deliverable entails – start with the project description from your supervisor 4Project Planning

Planning Your Project Plan regular meetings with your supervisor at least once a week Concentrate on planning for the basic deliverable to get a clear plan for tackling that over the next 3 months. Plan to re-plan later on as your project progresses and you have a better understanding enabling you to predict how design choices made now will affect the later goals. 5Project Planning

Time Planning with Supervisor How often? Once a week for at least 30 minutes Keep track of the meetings on the Project Work forms that should be kept in your Project Log Get in contact in case of “problems” 6Project Planning

Self Organisation How many hours in which week? - 16 on average Depending on lectures, assessments, etc. Depending on music events, beer festivals, etc. Unforeseen events can happen!! - allow for some extra time planned towards the end; 7Project Planning

Time Planning Soft deadlines / hard deadlines (throughout the project for each phase, deliverable, assessment) Use charts or diagrams to visualize tasks/time, since they are easier to read than a diary 8Project Planning

Plan Time for Revisions (suggested by supervisor; after testing/evaluation) Testing or evaluating the design, implementation, algorithms Draft versions of report writing - start in time (yesterday) Basic, intermediate and advanced deliverables 9Project Planning

Plan Time for Reflections and adapting the plan Unforeseen, e.g. additional reading, adapting software tools 10Project Planning

Deliverables Use the project description as a starting point Relate the deliverables to the objectives Discuss the feasibility with your supervisor 11Project Planning

Levels of Deliverables Basic deliverables –Related to minimum objectives –Turned into a part of the design or a piece of code –With a basic level of functionality –If this is delivered at the end and everything else is okay, it means just passed (depending on the weighing of parts) 12Project Planning

Levels of Deliverables Intermediate / Advanced deliverables –Related to intermediate / advanced objectives –Further refinement / Fair deal of evaluation, testing etc. –More / almost all of the functionality (but realistic!) –If this is delivered and the rest is very good / excellent, it distinguishes between class 2.1 and 1 13Project Planning

Further Details Chapters on Project Planning in books ASE Lecture on Planning 14Project Planning

Summary Take note of these workshops and the documentation as failure to do so in the past has resulted in students attaining very poor marks and even failing completely Start early. Put in enough work. If you do not do enough, you will fail. 15Project Planning