CSC111H Project Planning Dennis Burford

Slides:



Advertisements
Similar presentations
Project Management Concepts
Advertisements

Facilitated by Joanne Fraser RiverSystems
Project Management Process. Managing the Information Systems Project Focus of project management To ensure that information system projects meet customer.
Quick Recap. Quick Recap The Project Plan Plan Your Work, then Work Your Plan.
Chapter 2 The Analyst As Project Manager In Managing Information Systems 2.3.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Project Management.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
Degree and Graduation Seminar Scope Management
Project Plans CSCI102 - Systems ITCS905 - Systems MCS Systems.
Projmgmt-1/17 DePaul University Project Management I - Work Breakdown Structure Instructor: David A. Lash.
What is a project? Project Management Institute definition
Introduction to Project Management ECE 480 Erik Goodman.
Lecture 3 Managing your project How? Milestones Deliverables Meeting tutors.
Project Management Session 7
1 SOFTWARE PRODUCTION. 2 DEVELOPMENT Product Creation Means: Methods & Heuristics Measure of Success: Quality f(Fitness of Use) MANAGEMENT Efficient &
Project Tracking and Scheduling Infsy 570 Dr. R. Ocker.
Planning. SDLC Planning Analysis Design Implementation.
Project Management and Scheduling
Community Capacity Building Program Project Management.
Copyright 2002 Prentice-Hall, Inc. Managing the Information Systems Project 3.1 Chapter 3.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
07 – Project Management Software
SA Capstone Requirements and Design Week 10 SYST Winter 2013 Instructors: Jerry Kotuba & Joe Varrasso.
S/W Project Management
PROJECT PLANNING. PLANNING Planning is essential and software development is no exception. Achieving success in software development requires planning.
Pre-Project Activities Text Chapters 5 and 6. Pre-Project Activities 1.Contract Review 2.Development Plan 3.Quality Plan.
1 - Understanding the Basics. PROJECT What is a project?  A task (with some degree of complexity) with a known end point Building a new house Creating.
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.
BSBPMG503A Manage Project Time Manage Project Time Unit Guide Diploma of Project Management Qualification Code BSB51507 Unit Code BSBPMG503A.
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
1 IT Project – Project Lifecycle, methodologies, tools, resources and other issues.
Using the Logical Framework to Develop Activity and Resource Schedules.
What’s a Project? AD642. Why the Emphasis on Project Management? Copyright 2011 John Wiley & Sons, Inc. 1-2  Many tasks do not fit neatly into business-as-usual.
IHRIM n International Association for Human Resource Information Management n Professional group - HR, HRIS, IS managers; compensation, computer, and other.
Project Management Project Planning Estimating Scheduling.
Software Project Management Lecture # 7. Outline Project Scheduling.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Software Project Management Lecture # 7. What are we studying today? Chapter 24 - Project Scheduling  Effort distribution  Defining task set for the.
BIS 360 – Lecture Two Ch. 3: Managing the IS Project.
Ahmad Al-Ghoul. Learning Objectives Explain what a project is,, list various attributes of projects. Describe project management, discuss Who uses Project.
Software Project Management By Deepika Chaudhary.
Project monitoring and Control
Chapter 11. Intro  What is Project Management?  Project Manager  Project Failures & Successes Managing Projects  PMBOK  SDLC Core Process 1 – Project.
Information Technology Project Management
Slide 1 Project Management Chapter 4. Slide 2 Objectives ■ Become familiar with estimation. ■ Be able to create a project workplan. ■ Become familiar.
©Ian Sommerville 2000 Slide 1 Project management l Organising, planning and scheduling software projects l Objectives To introduce software project management.
© Mahindra Satyam 2009 Configuration Management QMS Training.
An Introduction to Software Engineering
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design.
Information Systems System Analysis 421 Chapter 3 Managing the Information Systems Project.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Chapter 2 Managing the Information Systems Project 2.1.
Test Postmortem Dennis Burford
1 Project Management Software management is distinct and often more difficult from other engineering managements mainly because: – Software product is.
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.
P3 Business Analysis. 2 Section F: Project Management F1.The nature of projects F2. Building the Business Case F4. Planning,monitoring and controlling.
Creating a Work Breakdown Structure with Microsoft Project.
Prof. Shrikant M. Harle.  The Project Life Cycle refers to a logical sequence of activities to accomplish the project’s goals or objectives.  Regardless.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Chapter 11 Project Management.
Stacy Kowalczyk WIC Technical Hour 3/30/2005
Project Management Processes
“In the midst of chaos, there is also opportunity” - Sun Tzu
Introduction to Project Management ECE 480 Erik Goodman.
Project Management Processes
Project Management Chapter 11.
Chapter 3 Managing the Information Systems Project
“In the midst of chaos, there is also opportunity” - Sun Tzu
Presentation transcript:

CSC111H Project Planning Dennis Burford

Planning Important because: –Software development is complex process –Team work is essential –Time and money constraints –Need direction... i.e. goals May build wrong thing! –Need a measure of progress / success or failure

Planning Problem Definition Determine Constraints Task Breakdown Scheduling Delegation of tasks - Team Work Documentation

Problem Definition Define problem clearly and unambiguously “Build” system on paper –Tests problem understanding –Uncovers potential problems Draw up formal problem definition –Need knowledge of problem (above) –Part of software lifecycle Will refer to prob. def. throughout project

Software Lifecycle Specification –what are the needs? (WHAT) Design –how will we do it? (HOW) Implementation –do the actual programming Testing –make sure it does what it was supposed to do Maintenance –ongoing adjustments & corrections

Determine Constraints Time –Milestones and deliverables –Final delivery date People –Number of participants –Skills available Resources –Money –Equipment –Information?

Task Breakdown Establish “areas” of work Give names to tasks Task hierarchy –Each task broken into smaller sub-tasks –Task complete when all subtasks complete

Task Breakdown Project GUIC/S RequirementsLayoutImplementation Integration ComponentsListeners

Scheduling Dependencies –What tasks to be done before others? Estimate time –Conservative estimates –Rather overestimate and have more time at end Allocation of people to task –Fair breakdown –Maximise skills

Dependencies : Making Tea... TaskDurationDependent on... A. Boil water in kettle4 B. Heat milk7 C. Tea bags into pot1 D. Sugar into cups1 E. Pour water into pot3 F. Pour tea into cups1 G. Add milk to tea1 H. Stir and drink6

TaskDurationDependent on... A. Boil water in kettle4- B. Heat milk7- C. Tea bags into pot1- D. Sugar into cups1- E. Pour water into pot3A, C F. Pour tea into cups1D, E G. Add milk to tea1B, F H. Stir and drink6G Dependencies : Making Tea...

Scheduling Scheduling techniques / documents –Table of tasks, delegation, time estimates and completion dates –Gantt chart: visual representation of tasks, dependencies and completion times

Scheduling: Table

Scheduling: Gantt Chart Boil Water A Heat Milk B T bags C Sugar D Water in pot E T in cups F Add milk G Drink H

Scheduling: Making Tea... TaskDurationDependent on... A. Boil water in kettle4- B. Heat milk7- C. Tea bags into pot1- D. Sugar into cups1- E. Pour water into pot3A, C F. Pour tea into cups1D, E G. Add milk to tea1B, F H. Stir and drink6G

Scheduling Milestones –Check of progress made –End of distinct stage –Must be verifiable Deliverables –Milestone –Tangible progress - usually delivered to customer 9

Team Work Division of labour between members Ensure fair breakdown Use strengths / skills of each member Team work, “interfacing”, is part of any project Related sub-tasks should be done by same person Plan for integration of separate work

Team Work Hold meetings: –Regular –Focussed –Efficient use of time Responsibility, Accountability, Discipline

Documentation Workbooks –All ideas, plans, designs –Dates and page numbers –Record of meetings, problems, progress Project Report –“Active” document –Start writing from day 1 –Constantly revise and rewrite

Project Pitfalls Coding before planning No milestones Unrealistic goals Great plan, no action Rigid “at-all-costs” task completion (overrun time allocation) One man show No documentation / last-day write-up

Assignment: Work-plan The aim of this deliverable is for you to start thinking about the project in more detail. It is suggested you read through all the future tuts associated with this project (3-8). You are required to break down the project in a number of detailed tasks. For each task estimate how long the task will take you (and then multiply this by 2 for a more realistic estimate). From this develop an outline plan of how you intend structuring your work over the remainder of the project (remember to include the time to do your documentation). For each task, state how long you estimate it will take you (in hours), as well as the date you expect to complete it. Your tasks must be more detailed than the handins we have specified.

Assignment: Work-plan Programming tasks 30% –Well thought out, and detailed = 30% –Some tasks, but very broad, or major tasks missing=15% –No programming tasks given=0% Documentation tasks 30% –Well thought out, and detailed=30% –Some tasks, but very broad, or major tasks missing=15% –No documentation tasks given (0%) Estimated Time 20% –Seems realistic=20% –Times given, but not very realistic=10% –Estimated times not given=0% Neatness (in electronic form, tables etc) 20%