- Each request (change or fix) come from our customers and is about ONE requirement. Example: change the color of the button.
You really defined a project for a request to change the color of a button ?
When the requirement is in prestudy, we study the feasibility
And what is the requirement linked to ? (if not to a project)
How do you manage work spent on requirement feasibility study ? (if not inside a projet)
Really I thing you should manage your sub-projects as activitiies.
1) you can copy a requirement into an activity
2) an activity can be split into sub activities
3) Requirements and acitivites can belong to same main project
4) if you please, you can define some activity type called "project"
It really makes sense to me to define an activity (and not a project) to change the color of a button, and not a project.
I checked with projects manager
Do the project managers manage 1 and 1 only requirement ?