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 »

# 11.2 Demonstration

An example project used to demonstrate Redmine

- Introducing a project management system for an R&D site – can be a faculty of a University – with 20 associates and 3-4 parallel projects

  - High-level plan in Redmine

1. Plan - Define

   1. Usage requirements

      1. System available 24/7

      2. Access from local and remote computers available

         1. Web based UI

      3. Logging all activity

      4. Gantt chart for printing

      5. Logging time on a project, later on a ticket basis

         1. Mandatory time log at the end of the week by all employees

         2. Granularity: log a minimum of 4 hours / issue of a project

      6. Role & permission handling

         1. Project auditor / head of department

            1. Read-only mode for all projects

            2. Monitors all projects on a weekly basis

         2. Project manager

            1. Read and write for own projects

            2. Manages projects, creates and assigns tasks, evaluate process

            3. Creates time log on a ticket basis

         3. Project executors

            1. Limited read and write access for own projects, full access to own tickets

            2. Execute assigned tasks, create more granular task list in a hierarchical format, if needed

            3. Creates time log on a ticket basis

   2. Success criteria

      1. Web based, multi-user system set up

      2. All users use the system on a daily basis

      3. All projects of the department are available in the system

      4. Granular task list with start and finish dates available

      5. System is up-to-date, shows real-time process

      6. All employees logs a minimum of 7 hours per day for the current week till the following Tuesday evening

   3. Technical tasks on installing and modifying the system

      1. Create a secure server environment

      2. Use encryption

      3. Set up support and maintenance roles and responsibilities

2. Provide a task list for integration to to-be-used processes

   1. Define type of tickets and workflow

      1. Type of tickets : workflow

         1. Prototyping: New > Accepted > In Progress > Testing > Done

         2. Development: New > Analysis Done > Implementing > A Testing > Integrating > B Testing > Done

         3. Testing: Test ready > Define Test cases > Implement auto test cases > Implement regression test > Execute manual & Auto test cases > Evaluate > Back to development (Convert to Development ticket) | Done

   2. Add users & permissions, according to the above

      1. User Audit, pw. 123

      2. User PM, pw. 456

      3. User User1, pw 789

   3. Add a sample project for the department

3. Execute task list

4. (Constantly) measure if success criteria are met,

   1. Evaluate

   2. Report

« Prev | Next »