©2008 John Wiley & Sons Ltd. www.wileyeurope.com/college/van vliet Software Engineering Management Main issues:  Plan - as much as possible, but not too.

Slides:



Advertisements
Similar presentations
Module N° 4 – ICAO SSP framework
Advertisements

1 Dr. Ashraf El-Farghly SECC. 2 Level 3 focus on the organization - Best practices are gathered across the organization. - Processes are tailored depending.
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
More CMM Part Two : Details.
Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department of Defense © 1998 by Carnegie Mellon.
lamsweerde Part 1: Introduction © 2009 John Wiley and Sons 1 Requirements Engineering From System Goals to UML Models to.
CSCU 411 Software Engineering Chapter 2 Introduction to Software Engineering Management.
Informatics 43 – April 16, Homework 1 What is the purpose and goal of each section in the document? Two audiences: non-technical users and technical.
Project Planning and Control Main issues:  How to plan a project?  How to control it? ©2008 John Wiley & Sons Ltd. vliet.
Software Engineering Management Main issues:  Plan - as much as possible, but not too much, up front  Control - continuously.
ICS Management Poor management is the downfall of many software projects Software project management is different from other engineering management.
Course Technology Chapter 3: Project Integration Management.
a judgment of what constitutes good or bad Audit a systematic and critical examination to examine or verify.
Monitoring, Review and Reporting Project Cycle Management A short training course in project cycle management for subdivisions of MFAR in Sri Lanka.
International Campus – Kish Sharif University of Technology Session # 2.
Information Technology Project Management
Marc Conrad University of Bedfordshire 1 Project Management – PMBOK® Project Initiation Dr Marc Conrad Office: D104 – Park Square
Learning with a Purpose: Learning Management Systems Patti Holub, Director District Initiatives and Special Projects Miguel Guhlin, Director Instructional.
The Key Process Areas for Level 2: Repeatable Ralph Covington David Wang.
Copyright Course Technology 1999
Matching PMBOK Section
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights.
Information Systems Security Computer System Life Cycle Security.
The Planning Process Copyright, 2006 © L. Ouyang Liubo Ouyang Personal Software Process Lecture 11.
Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?
Soft Tech Development Inc. 1 Software Project Tracking A CMM Level 2 Key Process Area Soft Tech Development Inc.
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.
Centro de Estudos e Sistemas Avançados do Recife PMBOK - Chapter 4 Project Integration Management.
FACTORS INFLUENCING IMPLEMENTATION OF MAJOR INFRASTRUCTURE PROJECTS IN KENYA: A CASE OF THE SOUTHERN BYPASS ROAD, KENYA By 1. Dr. Charles Wafula Misiko.
Good Hygiene Practices along the coffee chain Assemble the HACCP Team – Task 1 Module 4.3.
Chapter 3: Project Management Omar Meqdadi SE 2730 Lecture 3 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
1.  Describe an overall framework for project integration management ◦ RelatIion to the other project management knowledge areas and the project life.
lamsweerde Requirements Engineering © 2009 John Wiley and Sons 1 Requirements Engineering From System Goals to UML Models.
Quality Management (WP5) Roman CHIRCA Agency for Innovation and Technological Transfer TecTNet ………... This project has been funded with support from the.
WVU Libraries Intranet  internet | intranet | extranet  library intranet | extranet ideals  plans  issues.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
User Interface Design Main issues: What is the user interface How to design a user interface ©2008 John Wiley & Sons Ltd.
BSBPMG505A Manage Project Quality Manage Project Quality Project Quality Processes Diploma of Project Management Qualification Code BSB51507 Unit.
Software Engineering Modern Approaches Eric Braude and Michael Bernstein 1.
Managing Software Quality Main issues:  Quality cannot be added as an afterthought  To measure is to know  Product quality vs process quality ©2008.
©Ian Sommerville 2000 Slide 1 Project management l Organising, planning and scheduling software projects l Objectives To introduce software project management.
 Management ◦ The activities and tasks undertaken by one or more persons for the purpose of planning and controlling the activities of other in order.
Apply Quality Management Techniques Project Quality Processes Certificate IV in Project Management Qualification Code BSB41507 Unit Code BSBPMG404A.
Lessons from Programme Evaluation in Romania First Annual Conference on Evaluation Bucharest 18 February 2008.
Project Management and Risk. Definitions Project Management: a system of procedures, practices, technologies, skills, and experience needed to manage.
Quality Criteria : Are you and your team capable of communicating the shared vision to whom it may concern so that it make sense to all relevant stakeholders.
People Management, People Organization Main issues:  People are key in software development  Different ways to organize SD projects ©2008 John Wiley.
Configuration Management Main issues:  manage items during software life cycle  usually supported by powerful tools ©2008 John Wiley & Sons Ltd.
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System A Use Case Primer Organizing.
Pertemuan 14 Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
BSBPMG501A Manage Project Integrative Processes Manage Project Integrative Processes Project Integration Processes – Part 2 Diploma of Project Management.
V. 2. © Copyright and all rights reserved 4. Project Integration Management PMP Prep Course Based on the PMBOK ® Guide 3 rd Edition.
Introduction to Project Management Project Monitoring and Control Lecture a This material (Comp19_Unit9a) was developed by Johns Hopkins University, funded.
PFM reform – change management Module 3.2 Preparing and managing a PFM reform programme 1.
University of Southern California Center for Systems and Software Engineering Barry Boehm, USC CS 510 Fall 2010 Software Planning Guidelines.
1 Processes and Process Models Lecture # 5. 2 Process - 1 A process is an organized set of activities, which transforms inputs to outputs We can use synonyms.
University of Palestine Faculty of Applied Engineering & Urban Planning Civil Engineering Department Engineering Project Management Chapter 1 Introduction.
Introduction to Project Management Project management.
Project Execution Methodology
ESTIMATING PROJECT TIME, COST & BUDGETING
Project Management PTM721S
Game Design, Development, and Technology
RAF9038 Final Coordination Meeting
Cost Estimation Models
Imran Hussain University of Management and Technology (UMT)
Software Subcontractor
Project Integration Management
Component-Based Software Engineering
CS 577b: Software Engineering II
Software Cost Estimation
Presentation transcript:

©2008 John Wiley & Sons Ltd. vliet Software Engineering Management Main issues:  Plan - as much as possible, but not too much, up front  Control - continuously

©2008 John Wiley & Sons Ltd. vliet 2 A broader view on software development information planning boundary conditions people documentation program software inputoutput procedures

©2008 John Wiley & Sons Ltd. vliet 3 Example: information plan of a university registration of student data  Relations to other systems: personal data, courses, course results, alumni, …  Use both by central administration, at faculty level, and possibly by students themselves  Requires training courses to administrative personnel  Authorization/security procedures  Auditing procedures  External links, e.g. to scholarship funding agencies, ministry of education

©2008 John Wiley & Sons Ltd. vliet 4 Contents of project plan  Introduction  Process model  Organization of project  Standards, guidelines, procedures  Management activities  Risks  Staffing  Methods and techniques  Quality assurance  Work packages  Resources  Budget and schedule  Changes  Delivery

©2008 John Wiley & Sons Ltd. vliet 5 Project control  Time, both the number of man-months and the schedule  Information, mostly the documentation  Organization, people and team aspects  Quality, not an add-on feature; it has to be built in  Money, largely personnel

©2008 John Wiley & Sons Ltd. vliet 6 Managing time  Measuring progress is hard (“we spent half the money, so we must be halfway”)  Development models serve to manage time  More people  less time?  Brooks’ law: adding people to a lae project makes it later

©2008 John Wiley & Sons Ltd. vliet 7 Managing information  Documentation  Technical documentation  Current state of projects  Changes agree upon  …  Agile projects: less attention to explicit documentation, more on tacit knowledge held by people

©2008 John Wiley & Sons Ltd. vliet 8 Managing people  Managing expectations  Building a team  Coordination of work

©2008 John Wiley & Sons Ltd. vliet 9 Managing quality  Quality has to be designed in  Quality is not an afterthought  Quality requirements often conflict with each other  Requires frequent interaction with stakeholders

©2008 John Wiley & Sons Ltd. vliet 10 Managing cost  Which factors influence cost?  What influences productivity?  Relation between cost and schedule

©2008 John Wiley & Sons Ltd. vliet 11 Summary  Project control concerns  Time  Information  Organization  Quality  Money  Agile projects do less planning than document- driven projects