Course Title

- IT support for project management processes
- Course description
- Chapter 1 - Introduction to project management
  - Objective
  - 1.1 Project management
  - 1.2 Limitations
  - 1.3 Task
  - 1.4 Project planning
  - 1.5 V-model
  - 1.6 Summary
  - 1.7 Questionnaire
  - 1.8 Bibliography
- Chapter 2 - Introduction to PRINCE2
  - Objective
  - 2.1 Introduction
  - 2.2 Principles
  - 2.3 Themes
  - 2.4 Processes
  - 2.5 Tool demo example
  - 2.6 Summary
  - 2.7 Questionnaire
  - 2.8 Bibliography
- Chapter 3 - Introduction to PMBOK
  - Objective
  - 3.1 Description
  - 3.2 PMBOK's methodology
  - 3.3 PMBOK Core Areas
  - 3.4 PMBOK Facilitating Areas
  - 3.5 PMBOK Integration Management
  - 3.6 Summary
  - 3.7 Questionnaire
  - 3.8 Bibliography
- Chapter 4 - Introduction to Agile
  - Objective
  - 4.1 Description
  - 4.2 Sprints
  - 4.3 Roles
  - 4.4 Communication
  - 4.5 Requirements management
  - 4.6 Measurement
  - 4.7 Summary – pros and cons of Agile
  - 4.8 Questionnaire
  - 4.9 Bibliography
- Chapter 5 - Advanced Agile
  - Objective
  - 5.1 Description
  - 5.2 Kanban Development – Just-In-Time logistics
  - 5.3 Extreme Programming – Simplicity with a scent of quality assurance
  - 5.4 Crystal methodology – According to project size & criticality
  - 5.5 Dynamic Systems Development Method – Business value
  - 5.6 Feature-Driven Development – Business model
  - 5.7 Summary
  - 5.8 Questionnaire
  - 5.9 Bibliography
- Chapter 6 - Introduction to Lean
  - Objective
  - 6.1 Introduction
  - 6.2 History
  - 6.3 Lean basic concepts
  - 6.4 Further Principles
  - 6.5 Lean tools
  - 6.6 Basic overview of concepts and tools
  - 6.7 Lean improvement cycle
  - 6.8 Tool demo
  - 6.9 Summary
  - 6.10 Questionnaire
  - 6.11 Bibliography
- Chapter 7 - Advanced Lean
  - Objective
  - 7.1 Introduction
  - 7.2 Lean Principles
  - 7.3 Lean Software Development
  - 7.4 Summary
  - 7.5 Questionnaire
  - 7.6 Bibliography
- Chapter 8 - Discussion
  - Objective
  - 8.1 Introduction
  - 8.2 Modelling a project
  - 8.3 Other methodologies
  - 8.4 Related fields
  - 8.5 Groupwork, homework
  - 8.6 Summary
  - 8.7 Questionnaire
  - 8.8 Bibliography
- Chapter 9 - Comparison
  - Objective
  - 9.1 Introduction
  - 9.2 Principles – processes – tools
  - 9.3 Modelling the project
  - 9.4 Classifications of project management methodologies
  - 9.5 Proposed method
  - 9.6 Groupwork, homework
  - 9.7 Summary
  - 9.8 Questionnaire
  - 9.9 Bibliography
- Chapter 10 - Project management tools basics
  - Objective
  - 10.1 Description
  - 10.2 Desktop tools
  - 10.3 Cloud based tools
  - 10.4 Summary
  - 10.5 Questionnaire
  - 10.6 Bibliography
- Chapter 11 - Project management tools advanced
  - Objective
  - 11.1 Description
  - 11.2 Demonstration
  - 11.3 A walkthrough on Redmine
  - 11.4 Redmine deficiencies
  - 11.5 Summary
  - 11.6 Questionnaire
  - 11.7 Bibliography
- Chapter 12 - Summary, conclusion
  - Objective
  - 12.1 Project management methodologies and software solutions
    - 12.1.1 PRINCE2
    - 12.1.2 PMBOK
    - 12.1.3 AGILE
    - 12.1.4 Lean
    - 12.1.5 Discussion and comparison of the methods
    - 12.1.6 Various project management tools
    - 12.1.7 Redmine
  - 12.2 Groupwork, homework
  - 12.3 Questionnaire
  - 12.4 Bibliography

« Prev | Next »

# 3.3 PMBOK Core Areas

Figure 3.4: PMBOK Core areas

- Quality Management – processes and activities to determine quality objectives, responsibilities, policies for the project to satisfy the needs of stakeholders. Implementation of a quality management system with continuous process improvements.

> Main asset: Quality management Plan containing metrics, checklists and an improvement plan.

- Activities

  - Plan Quality to identify requirements and standards for the project, to get aware of how the project will meet those

  - Perform Quality Assurance to audit the quality requirements, examine the quality properties and act to ensure that all needed quality control processes are used

  - Perform Quality Control to execute quality activities and ensure that all defined processes are in place and met. Assess the performance of the quality process and recommend necessary changes.

- Time Management - to get the project done on time and within budget (more time spent results in cost increase)

Main asset: time management plan containing time management processes and tools. Schedule management plan, which is a subsection of the project plan.

- Activities

  - Define the Activities to identify specific actions to produce deliverables by using the requirement and organizational process assets

  - Sequence the Activities to document relationships amongst activities by using an activity and milestone list

  - Estimate Activity Resources to have an overview on the material, equipment and personnel needs of each activity. Achieve that by using expert's judgement and bottom-up estimation

  - Estimate Activity Durations to estimate work periods to complete milestones using an activity list and activity resourcing sheets

  - Develop a Schedule to get an overview on sequences, durations and meet schedule constraints using the relations amongst activities

  - Control the Schedule to adjust leads and lags by monitoring the status and making adjustment in changing the schedule baselines.

- Cost management – estimating, budgeting and controlling costs for the project to not exceed the planned and approved budget. Includes the change management processes of costs.

  Main asset: Cost Plan with activity cost estimates, work performance management plan

  - Activities

    - Estimate Costs – approximation of project costs on a per task basis, based on the needed resources and materials to fulfill all project needs

    - Determine Budget – summary of cost estimation of individual activities to logically related work packages to establish a cost baseline

    - Control Costs – monitoring cost status, updating costs by managing changes

- Scope Management – to ensure that the project includes all the needed tasks defined without any unnecessary ones

  Main asset: list of detailed requirements, Requirements Management Plan contained in the project plan.

  - Activities

    - Collect Requirements – create a requirements management plan and requirements documentation. Requirement elicitation can be done using interviews, workshops, prototypes, observations. Needed to be able to meet stakeholders' expectations and project objectives.

    - Define scope – create a detailed description of the project and on the resulting product. Can be achieved by using product analysis, expert's judgements and/or facilitated workshops

    - Work-break-down structure creation – creating granular, easily manageable tasks. Using task decomposition to create a task set.

    - Verify scope – create change requests and update project documentation by using inspection on the documents and interviewing stakeholders with different techniques.

    - Control the scope – to avoid increasing or decreasing the scope, create change requests if any new requirements or new tasks are arising from the documentation.

« Prev | Next »