Software Project Management Lecture 11. Outline Brain Storming session  Some simple discussion on questions and their answers  Case studies related.

Slides:



Advertisements
Similar presentations
Systems Investigation and Analysis
Advertisements

Software Project Management
Project Management Process. Project Complexity means that: a team of people are needed to supply expertise the work needs to be broken into manageable.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 28 Slide 1 Process Improvement.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 Project management.
1 Info 1409 Systems Analysis & Design Module Lecture 5 - Feasibility HND Year /9 De Montfort University.
Software Project Planning CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology December 12, 2002.
Class 28: Chapter 16: Project Management Class 28 Agenda –Collect Player Diary 2 and Conduct Player Audit No ed diaries – 5 PM Deadline –Discuss Grade.
Software project management (intro)
Fundamentals of Information Systems, Second Edition
Project Plan The Development Plan The project plan is one of the first formal documents produced by the project team. It describes  How the project will.
The Analyst as a Project Manager
Principles of Information Systems, Sixth Edition 1 Systems Investigation and Analysis Chapter 12.
Project Plan Development
Software Test Plan Why do you need a test plan? –Provides a road map –Provides a feasibility check of: Resources/Cost Schedule Goal What is a test plan?
Project Tracking and Scheduling Infsy 570 Dr. R. Ocker.
Bringing Softtek’s Software Testing Organization from Good to World- Class Software Testing Organization Proposal.
Project planning. Software project management Informal definition of management – The art of getting work done through other people Software project management.
Sharif University of Technology Session # 4.  Contents  Systems Analysis and Design Sharif University of Technology MIS (Management Information System),
© 2006 ITT Educational Services Inc. System Analysis for Software Engineers: Unit 5 Slide 1 Chapter 3 Managing the Information Systems Project.
Project Management An overview. What is a Project A temporary job to accomplish a specific task A temporary job to accomplish a specific task Attributes.
©Ian Sommerville 2000Software Engineering, 7th edition. Chapter 5 Slide 1 Chapter 5 Project Management Modified by Randy K. Smith.
S/W Project Management
COMPGZ07 Project Management Presentations Graham Collins, UCL
Test Organization and Management
Investment Portfolio Methodologies Pertemuan Matakuliah: A Strategi Investasi IT Tahun: 2009.
Software Project Management Introduction to Project Management.
Copyright © 2014 McGraw-Hill Higher Education. All rights reserved. CHAPTER 15 Project Management McGraw-Hill/Irwin.
1 IT Project – Project Lifecycle, methodologies, tools, resources and other issues.
Chapter 6 : Software Metrics
Lecture 4 1 Introduction to Systems Planning Lecture 4 2 Objectives n Describe the strategic planning process n Explain the purpose of a mission statement.
Switch off your Mobiles Phones or Change Profile to Silent Mode.
BIS 360 – Lecture Two Ch. 3: Managing the IS Project.
Lecture 7. Review of Lecture 6 Project Scheduling: The process of defining project activities, determining their sequence, estimating their duration Scheduling.
Project management Lecture 10. Topics covered Management activities Project planning Project scheduling Risk management.
© The McGraw-Hill Companies, Software Project Management 4th Edition Risk management Chapter 7.
Software Project Management By Deepika Chaudhary.
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
©Ian Sommerville 2000 Slide 1 Project management l Organising, planning and scheduling software projects l Objectives To introduce software project management.
Dr. Jana Jagodick Polytechnic of Namibia, 2012 Project Management Chapter 2 Project Management Cycle.
3 1 Project Success Factors u Project management important for success of system development project u 2000 Standish Group Study l Only 28% of system development.
Principles of Information Systems, Sixth Edition Systems Investigation and Analysis Chapter 12.
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
Project Management Cross lifecycle Activity
February 15, 2004 Software Risk Management Copyright © , Dennis J. Frailey, All Rights Reserved Simple Steps for Effective Software Risk Management.
Information System Project Management.  Some problems that org faced with IS dev efforts include schedule delays, cost overrun, less functionality than.
What is project management?
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
Quick Recap.
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
Fundamentals of Information Systems, Third Edition2 An Overview of Systems Development: Participants in Systems Development Development team –Responsible.
1 Project Management Software management is distinct and often more difficult from other engineering managements mainly because: – Software product is.
Establishing Project Scope 1. Factors Affecting Project Scope  The functionality that must be delivered to meet the user’s needs  The resources available.
Switch off your Mobiles Phones or Change Profile to Silent Mode.
Systems Analysis Lecture 5 Requirements Investigation and Analysis 1 BTEC HNC Systems Support Castle College 2007/8.
A Brief intro to Project Management What can it do for you
Chapter 11 Project Management.
Managing the Project Lifecycle
Fundamentals of Information Systems, Sixth Edition
Systems Analysis and Design in a Changing World, 4th Edition
Business System Development
CS 5150 Software Engineering
Activity Planning.
Lecture # 5 Software Development Project Management
Software Project Management (SPM)
Introduction to Projects
Project Management Chapter 11.
KEC Dhapakhel Lalitpur
Project Management II The Project Value Creation Process
Information system analysis and design
Presentation transcript:

Software Project Management Lecture 11

Outline Brain Storming session  Some simple discussion on questions and their answers  Case studies related to project management

Before the Brain Storming begins… Recap of what we have learnt so far in SPM course  What is Project, Project management, Software project management, stakeholders, team structures, 4Ps  Software Metrics  Estimation  Project Scheduling  Risk Management

Reason out … You are required to use your knowledge gained in SPM course and give reasoning based answers to the following questions…

Question Are there any differences between software project and software development?

Answer Software project includes the following three typical activities:  Feasibility study - the preliminary investigation to decide whether a potential project is worth pursuing.  Planning - the initial planning of a project to pursue. Detailed planning is necessary at later stages of the development.  Project execution - the execution of the development of the software product. Software project includes software development as part of its activities.

Question Which Software Process Model will be more suitable when requirements for a project are not completely defined OR not well defined?  Spiral  Waterfall  Prototyping

Answer Prototyping  It models the development process as prototype building to the satisfaction of the users.  promotes early understanding of the proposed system; involves user as part of the team; reduces uncertainty and risk  the system developed is usually not well-structured; lack of control of the project for developers  Well suited for those projects that do not have a clear or well-defined requirements, e.g., web-based projects

Question Spiral model:  It views software development effort in the light of the risks involved. It combines development activities with risk management to minimize and control risk of software development.  Benefits monitor and control risk; can incorporate other process models such as prototyping  Drawback overhead in risk assessment  For uncertain and changing requirements, it can initiate a small prototyping process for clarification and understanding.  Well suited for high risk projects and projects with uncertainties Continued on Next slide

Question For which of the following projects is the spiral model best suited? A system to control an X-ray machine for taking medical images from human body The payroll system of a company A Web-based transaction system

Answer X-ray machine system as it is a safety critical system

Question What are the various resources for a software project?

Answer Human resources Equipment (H/W) resources Software resources  Reusable / COTS / others.

Question Who manages resource allocation in a project?

Answer Project Manager

Question Context (Risk management)  You are in charge of a software project. However, your company does not have a hazard checklist or questionnaire. You decide to produce your own checklist. List at least one question that you might include under each of the following categories. Application factors (how it fits in the big picture) Supplier factors HR / Staff factors

Answer Application factor  Will the product need to interface with existing applications?  Is the product an application or an operating system? Supplier factor  What is the creditability of the suppliers?  How well established are the suppliers?  How often did the supplier deliver their products on time? Staff factor  Do the staffs have expertise in evaluating such a product?  Do the staffs have expertise in developing such a product?  Do the staffs have expertise in the development tools or environment?

Question Consider the following situation. The following table is extracted from a project plan that shows the number of activities, their durations and dependencies. Create a task network for it.

Answer

Question The arrows highlighted (bold) in last answer show the ‘Critical Path’. What is the significance of critical path?

Answer The critical path is simply all the tasks that drive the end date of your project schedule. If one of those tasks is late by one day, then your project end date will be extended by one day. If your project schedule has multiple critical paths, then your project schedule is considered sensitive. The critical path methodology is simply a technique to identify all the tasks that will directly impact the project end date.

Now some Case Studies…