]po[ Gantt Editor Test Scenario

This document describes test scenarios for the Gantt Editor package.


Simple Tests

This section contains a number of individual tests that can be executed using certain features or not.

Complexities of Test Scenarios in terms of features

The complexity of the test scenarios below can be modified by using one or more of the following features (from lowest complexity towards highest complexity):

  • Using only simple Gantt bars ("tasks")
  • Using the "Task Properties" window to change task properties, instead of grid columns
  • Using resource assignments to tasks
  • Using the "percentage bar" of each task
  • Using dependencies between tasks
  • Using hierarchical tasks
  • Using milestones
  • Using sub-projects of type "ticket container"
  • Using tickets inside the ticket containers
  • Using keyboard shortcuts
  • Using automatic scheduling

Test Scenario: "Create a new Gantt diagram from scratch"

Starting with a newly created project, create a project schedule manually from scratch. Then press the "Save" button and reload with "F5".


Test Scenario: "Extend an existing Gantt diagram"

Starting with any Gantt diagram, extend the diagram and press "Save".


Test Scenario: "Delete unsaved tasks in a Gantt diagram"

Starting with any Gantt diagram, extend the diagram and then delete part of the new elements. Then press "Save" and reload.


Test Scenario: "Delete saved tasks in a Gantt diagram"

Starting with any Gantt diagram, extend the diagram, press "Save", reload and then delete part of the new elements. Then press "Save" again and reload.


Complex Test Scenario: "Car Configurator"

This test scenario takes a hypothetical "Car Configurator" project in the IT department of a "Fidos" car manufacturer as a base. The life cycle of this "car configurator" serves to list the various interactions of users with ]project-open[.

What is a car configurator?

"Fidos" Utility Vehicles Austria

Fidos IT is the semi-autonomous IT department of Fidos that invoices projects and services to Fidos business departments.

Fidos IT is a long-term ]project-open[ installation in order to track their list of ongoing projects, resources, budgets and profitability.

Uses ]po[ in order to manage their projects.


Project charter: Goal to present on Paris fair. You've got a few man months. Get things done.


  1. Executive input - Start planning for an Internet car configurator. A first version should be available in the Paris car exhibition, a full-blown version should be ready in a year.
  2. Spend a few weeks on estimating the project.
  3. Determine possible resources required for the project
  4. Analysis capacity - Analyze different databases with product configuration data
  5. Hold stake-holder meetings with different departments involved
  6. Understand data-envionment - How to get configuration data from databases
  7. Analysis phase - only main consultant & PM working
  8. Get configuration sheets from reseller in Paris
  9. Decision taken - Use the reseller Excel sheets as base for the Internet car configurator
  10. Create architecture document - all important questions were resolved
  11. Write detailed project plan
  12. Determine resource requirements
  13. Check risks for Paris auto show
  14. Determine creation of photos
  15. Phase 1
  16. Phase 2
  17. Phase 3
  18. Phase 4
  19. Geneva install & show presentation (travel costs, expenses for stand)
  20. Phase 5
  21. Phase 6
  22. Demo Internet prototype
  23. Project killed by head quarter



  • Create project in ]po[ and set initial team.
  • Rough project plan based on skill profiles & resource reservation 200 man days & budget for the later phases once the scope is known and approved
  • Project Portfolio priorization - Project been approved by supervisory board
  • Baseline - create a copy of initial planning
  • Execution first phase - analysis: Timesheet & travel costs
  • Creation detailed initial project plan
  • Execute sprints 1, 2 and 3, leading to a first pilot system to be demoed on board meeting
    • How to enter SCRUM sprints in the project
    • Define user stories to implement
  • Milestone / Quality gate: Go for Paris trade fair: Go
  • Replanning after "go": With more realistic tasks & times
  • Execute sprints 4 and 5.
  • Prepare milestone car fair
  • Project being taken over by HQ production team.



  1. Create new project
  2. Empty Gantt Editor
  3. Create High-Level project schedule
  4. Assign skill profiles to tasks - "JD[150%]; SD[50%]
  5. Info: Red corners means fields not being saved


  Contact Us
  Project Open Business Solutions S.L.

Calle Aprestadora 19, 12o-2a

08902 Hospitalet de Llobregat (Barcelona)


 Tel Europe: +34 609 953 751
 Tel US: +1 415 200 2465
 Mail: info@project-open.com