Hi everybody,
I'm trying to plan test session without success 🙁 (Working with 4.4.2)
I've set my products, different release for each product, then one test sessions for each release.
- Test session are aleready planed (there's nearly one version per month)
- each test session last 3 weeks
- generaly 3 persons are working on a test session
My goal is to have test session scheduled with their start/end dates
So I defined each test session like this :
- validated start date & validated end date
- 3 ressources assignments of 6 days at 30%
- a low priority (100)
- fixed duration
When I click on the "Plan" button, test session does not respect the validated start/end date :blink:
For example :
- Session 1 between 13/02 and 06/03/2015
- Session 2 between 13/03 and 03/04/2015
- Session 3 between 10/04 and 30/04/2015
They appear on the planning like this :
- Session 1 : planned start_date 13/02 -> planned end_date 26/05
- Session 2 : planned start_date 13/03 -> planned end_date 16/06
- Session 3 : planned start_date 10/04 -> planned end_date 18/06
the "planned start date" is ok (equals "validated start date"), but the can you explain me why the "planned end_date" is so far in the future and how to manage my planning to enforce them ?
Thank you
Hi,
If you plan 6 days at 30%, it will take at least 20 open days to be done...
So cannot be planned from 13/2 to 6/3 (only open 17 days)
But this does not explain why end date is so far.
Could you please :
- check resources plan (see reports to check if they are not busy on another project)
- check affectation rate (to project) of the resource
- if all seems normal, please try and reproduce on the demo (you can connect as manager/manager and create your own project)
Thanks a lot Babynus, I really need to solve this.
First of all, I think there's a misunderstanding : I want my 3 ressources to work 1/3 of their day-time on test session.
Did I put the right stuff in the assignment zone ?
| resource | rate (%) | assigned | real | left |
| R1 | 33 | 5 | 0 | 5 |
| R2 | 33 | 5 | 0 | 5 |
| R3 | 33 | 5 | 0 | 5 |
Of course thoses ressources are busy on other tasks but thoses tasks have a higher priority value (so they came after in the planning process no ?)
I don't know how to affect a rate to a ressource on a project.
You assignments definition seems correct.
Please check report "Planning" / "Monthly planning resource/project/activity" and tell us what it says.
Nice Report ... I didn't knew it !
So the report says that my ressources are busy on other tasks !
The problem is that I want this specific tasks (test sessions) to be planned with high priority, so I put 100 as priority level and "regular between dates" (i also tried with "fixed duration") ... but nothing happens, those tasks are still planned in the future (after validated start/end dates now) !
Is there a trick ?
Possibly Resources are busy on other Project that you don't replan.
Try and plan all projects together.
I always replan all projects (by choosing "blank" project in the list before submiting planification).
My goal is to put all projects with their dead-lines, all ressources affected to those projects and to see where ressources have more than 100% of work.
What is your profile (access rights) ?
If you are Project Manager (or equivalent access rights), you can plan only projects you are affected to.
So planning "all project" will have no impact on projects you are not affected to (as expected), and resource planned work on these project will not be changed.
Could you try and reproduce your use case in the Demo so that I can have a look ?
I'm always doing this kind of work with admin rights 😉
I set an example on your demo site (Badgamme's project) but it's difficult to set the same activities for the 14 projects & 10 ressources I have to manage !
Anyway, you can see end-date are not respected (difference between validated and planned date).
Thank you for your help.
In your example, A, B and C are all assigned 5 days to TS1 at 30%.
So they can work no more than 0.3 each day on TS1, and this leads to minimum duration of 17 open days.
This cannot be done from 13/02 to 06/03 (only 16 open days), and minimum end date is 09/03.
B and C ends work on TS1 on ... 09/03 : completely correct.
A ends works on TS1 on ... 13/03, which is 4 days after expected target. If you look at his planned work, you can see he is busy on 17/02, 24/02, 04/03 and 06/03 on another project, for 0,8 (and his capacity is 0,8 so he has no more availability).
So planning calculation is completely correct.
If you want to respect fixed duration (as log as possible) try and set assignment rate at 100% on the task.
The work will be dispatched as best as possible, with possibly more than 0.3 some days.
Thanks Babynus,
As I said, the example is much more simplier than reality.
The problem is that the planification did not respect priority of tasks. If I tell my ressources to work 100% on each test session with a low priority of 100 ... they are still planned after tasks created with a priority of 300.
Hi,
I cannot find a case where planning priority is not respoected.
If you can set an example in the demo, please do !
(for instance with new project and new resources).
Really, take care of most important rule : if resource are shared on several projects and you don't plan all project together, exiting planning slots will not be moved, whatever the priority.
This is very important because your planning should not change planning on other project.