The Project Reel’s five step approach for successful projects

Slides:



Advertisements
Similar presentations
Project Management M Taimoor Khan
Advertisements

1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
W5HH Principle As applied to Software Projects
Stepan Potiyenko ISS Sr.SW Developer.
1 These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Types of Risks 1.Project risks –Impact schedule and cost –Includes budgetary, schedule, personnel, resource, customer, requirement problems 2.Technical.
Incremental Model Requirements phase Verify Specification phase Verify
Project Management Concepts
1 Chapter 3 Project Management. 2 The 4 P’s  People — the most important element of a successful project  Product — the software to be built  Process.
1 Project Management CIS 375 Bruce R. Maxim UM-Dearborn.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Workshop: Teamwork practicalities Kauppinen, M. Ylikangas, M.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Soft Tech Development Inc. 1 Software Project Tracking A CMM Level 2 Key Process Area Soft Tech Development Inc.
CSEB233: Fundamentals of Software Engineering
1 Chapter 5 Software Engineering Practice. 2 What is “Practice”? Practice is a broad array of concepts, principles, methods, and tools that you must consider.
Chapter 3 Project Management Concepts
1 Chapter 3 Project Management. 2 Project Management Concerns staffing? cost estimation? project scheduling? project monitoring? other resources? customer.
Project Management Concepts 1. What is Project Management? Project management is the process of the application of knowledge, skills, tools, and techniques.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Lecture 16: Chapter 24 Project Management Concepts
Company LOGO CSEB233 Fundamentals of Software Engineering Module 9: Software Project Management Badariah Solemon 2010.
Software Project Management Lecture # 2. Outline The 4 Ps in Project Management Detailed Insight of each P.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Software Project Management Lecture # 2 Originally shared for: mashhoood.webs.com.
Empirical Estimation Models Based upon historic data Basic Structure E = A + B * (ev) C where A, B, c are empirical constants ‘ev’ is the effort in terms.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Programming Techniques Lecture 15 Project Management Based on: Software Engineering, A Practitioner’s Approach, 6/e, R.S. Pressman Lecture 4 An Introduction.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Monitoring Risk Factors General attitude of team members based on project pressures The degree to which the team is jelled Interpersonal relationships.
Software Project Management
1 These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman.
CSC 480 Software Engineering Team Issues. Essence of a Successful Team To be successful, teams must  Plan their projects  Track their progress  Coordinate.
1 Supplementary Slides for Software Engineering: A Practitioner's Approach, 6/e Part 4 Supplementary Slides for Software Engineering: A Practitioner's.
P ERSONAL & TEAM PROCESS MODELS Lecture 05 Part -2.
Software Project Management
Software Engineering (CSI 321)
CSC 480 Software Engineering
Software Engineering Lecture #41
Chapter 3 Project Management
McCall’s Quality Factors
Software Engineering Lecture #2
For University Use Only
Chapter 3 Project Management
Software Engineering Lecture #39
SE Tasks for a Concept Development Project
Assessing Risk Impact Factors affecting the consequences Nature Scope
Software Engineering Lecture #25
Software Engineering Lecture # 17
Software Engineering Lecture #26
Program Restructuring
Error Tracking Defect removal efficiency DRE = E / (E+D)
Defects yet to be fixed Defects Time Total reported defects
Software Engineering: A Practitioner’s Approach, 6/e Chapter 2 Process: A Generic View copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Quality Measurable characteristic Cyclomatic complexity Cohesion
For University Use Only
Decision Tree.
Chapter 31 Project Management Concepts
Software Engineering Lecture # 01
Software Engineering Lecture #3
Software Engineering Lecture #40
Software Engineering Lecture #16
Software Project Management
Software Engineering Lecture #29
S M A R T Smart Objectives Goals need to be Achievable
Software Engineering Lecture #28
Presentation transcript:

The Project Reel’s five step approach for successful projects Start on the right foot Understand the problem, set realistic objectives, build the right team, provide the needed infrastructure Maintain momentum Track progress Make smart decisions Conduct a postmortem analysis

To Get to the Essence of a Project - W5HH Principle WHY is the system being developed? WHAT will be done? By WHEN? WHO is responsible for a function? WHERE are they organizationally located?

W5HH Principle (cont.) HOW will the job be done technically and managerially? HOW MUCH of each resource (e.g., people, software, tools, database) will be needed?

Critical Practices in Project Management Formal risk analysis Empirical cost and schedule estimation Metrics-based project management Earned value tracking Defect tracking against quality targets People aware project management

Recap

Software Engineering II Lecture 8 Fakhar Lodhi

Summary of Today’s Lecture