- Posts: 85
- Thank you received: 0
Support us on Capterra
Quality Based Open Source Project Organizer
|
|
I confirmWe've been advised, that we shouldn't create a project for everything, if a job is too small to perhaps warrant such a configuration.
Yes, good choiceSo if an Activity is maybe 1-2 days, it could be an activity of a project called "Mini projects".
If your first activity has higher priority (lower value of "priority" or just samller WBS), it will be planned before the second one. So the second one should not interact with first one.The issue I'm seeing here, is if I plan 1 of the "Activities" in this project... there is no way to finalise this? The next time I add a small activity to be planned, it may well affect the other activity i've planned/agreed with the client?
Please Log in or Create an account to join the conversation.
Just record it as a MeetingActivity1 is a fixed date (can't move) because for example we've arranged it with 30 people, a big meeting and simply something that CANNOT slip in terms of delivery. It's a specified time/place possibly with people around the world.
If Activity 1 comes first (in priority and / or WBS) there is no chance that same resource will be booked first on activity 2.Activity2 comes in and needs to be planned "ASAP" but uses the same resources
There is no risk Activity2 might accidentally reschedule Activity1?
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
babynus wrote:
Just record it as a MeetingActivity1 is a fixed date (can't move) because for example we've arranged it with 30 people, a big meeting and simply something that CANNOT slip in terms of delivery. It's a specified time/place possibly with people around the world.
Please Log in or Create an account to join the conversation.
