Docsity
Docsity
Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity

Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan

Guidelines and tips
Guidelines and tips
Sell on Docsity
Sell on Docsity
Docsity AI
Docsity AI
Log inSign up

Prepare for your exams

Study with the several resources on Docsity

Find documents

Prepare for your exams with the study notes shared by other students like you on Docsity

Search for your university

Find the specific documents for your university's exams

Docsity AINEW

Summarize your documents, ask them questions, convert them into quizzes and concept maps

Explore questions

Clear up your doubts by reading the answers to questions asked by your fellow students

Earn points to download

Earn points by helping other students or get them with a premium plan

Share documents
download point icon20 Points

For each uploaded document

Answer questions
download point icon5 Points

For each given answer (max 1 per day)

All the ways to get free points
Get points immediately

Choose a premium plan with all the points you need

Study Opportunities

Choose your next study program

Get in touch with the best universities in the world. Search through thousands of universities and official partners

Community

Ask the community

Ask the community for help and clear up your study doubts

Free resources

Our save-the-student-ebooks!

Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors

Introduction to Software Engineering Project Management (Part 1), Schemes and Mind Maps of Data Warehousing

Catholic University of Eastern AfricaData Warehousing

An introduction to software engineering project management, covering key concepts such as project definition, stakeholders, project management process groups, and tools. It explores the challenges of is project failures and success, highlighting common causes and strategies for mitigation. The document also introduces the project management institute (pmi) and its pmbok framework, emphasizing the importance of project management techniques for successful project completion.

Typology: Schemes and Mind Maps

2024/2025

Uploaded on 03/02/2025

brian-omondi-4
brian-omondi-4 🇰🇪

1 document

1 / 42

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
1/42
CS-413
Introduction To Software
Engineering Project Management
(Part 1)
Bilgisayar Mühendisliği Bölümü – Bilkent Üniversitesi – Fall 2009
Dr.Çağatay ÜNDEĞER
Instructor
Bilkent University, Computer Engineering
Middle East Technical University, Game Technologies
&
General Manager
SimBT Inc.
e-mail : [email protected]
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19
pf1a
pf1b
pf1c
pf1d
pf1e
pf1f
pf20
pf21
pf22
pf23
pf24
pf25
pf26
pf27
pf28
pf29
pf2a

Partial preview of the text

Download Introduction to Software Engineering Project Management (Part 1) and more Schemes and Mind Maps Data Warehousing in PDF only on Docsity!

CS-413^1 /

Introduction To Software

Engineering Project Management

(Part 1)

Bilgisayar Mühendisliği Bölümü – Bilkent Üniversitesi – Fall 2009 Dr.Çağatay ÜNDEĞER Instructor Bilkent University, Computer Engineering Middle East Technical University, Game Technologies & General Manager SimBT Inc. e-mail : [email protected]

Introduction To Software

Engineering Project Management

  • (^) What is Software Engineering?
    • (^) By Fritz Bauer
    • (^) By IEEE
  • (^) What is a Project?
    • (^) Introduction
    • (^) IS Project Failures & Success
    • (^) Characteristics of an IS project
  • (^) What is Project Management?
    • (^) Introduction
    • (^) Project Management Institute (PMI)
    • (^) Tools for Project Management

Software Engineering (2)

  • (^) (1) Application of a systematic, disciplined, quantifiable approach to; - (^) Development, - (^) Operation, and - (^) Maintenance of software (that is the application of engineering to software);
  • (^) (2) The study of approaches as in (1) (IEEE)
  • (^) Institute of Electrical and Electronics Engineers (IEEE)

Introduction To Software

Engineering Project Management

  • (^) What is Software Engineering?
    • (^) By Fritz Bauer
    • (^) By IEEE
  • (^) What is a Project?
    • (^) Introduction
    • (^) IS Project Failures & Success
    • (^) Characteristics of an IS project
  • (^) What is Project Management?
    • (^) Introduction
    • (^) Project Management Institute (PMI)
    • (^) Tools for Project Management

Introduction (IS Projects)

  • (^) Information System (IS) projects aim at making ongoing activities of institutions and enterprises; - (^) Faster, - (^) More efficient and - (^) More productive by integrating the information technologies into the process.

Introduction (Stakeholders)

  • (^) People that have an interest in a new or existing project, including; - (^) Project team members, - (^) Project sponsors, - (^) Stockholders, - (^) Employees and - (^) The community.

Introduction (Project Manager)

  • (^) A person who;
    • (^) Has a diverse set of skills (e.g. good general skills, technical manegement, conflict man., customer relationship man. and leadership skills), and
    • (^) Responsible for;
      • (^) initiation,
      • (^) planning,
      • (^) executing,
      • (^) controlling,
      • (^) monitoring, and
      • (^) closing down a project.

Introduction (Why?)

  • (^) IS projects are usually undertaken for two reasons; - (^) Solving business problems and - (^) Taking advantage of business opportunities.

IS Project Failures

  • (^) Don’t think that;
    • (^) A project failure only occurs when it is cancelled because of not successfully completing it.
  • (^) A project can be considered as failed when;
    • (^) The project finished over budget,
    • (^) The project did not finish on time,
    • (^) The project did not deliver a system that satisfies the stakeholders expectations,
    • (^) The project did not deliver a system that satisfies its objectives.

IS Project Failures

  • (^) First step:
    • (^) Identify causes of project failures, in order to avoid them.

Causes of project failures

(More Detailed)

  • (^) Lack of executive support:
    • (^) Lack of top management support and organizational commitment
  • (^) Lack of user input:
    • (^) Lack of user participation, user resistant to change, lack of user cooperation, and lack of user commitment

Causes of project failures

(More Detailed)

  • (^) Inexperienced project manager:
    • (^) Lack of leadership skills, project progress not monitored closely, ineffective communication
  • (^) Inexperienced team members:
    • (^) Inadequately trained team members, lack of team member commitment to project, frequent turnover within the team

Causes of project failures

(More Detailed)

  • (^) Ineffective project management:
    • (^) Lack of an effective project management methodology applied throughout the project
  • (^) New software infrastructure:
    • (^) Use of new technology that has not been practiced before, and use of immature and highly complex technologies

Causes of project failures

(More Detailed)

  • (^) Unstable organizational environment:
    • (^) Changes in organizational management during the project, and restructuring organization during the project
  • (^) Unreliable outside suppliers:
    • (^) Dependence on unreliable suppliers and involvement of many external suppliers