Our forum platform uses a separate login to identify you; it's not the same as your LiquidPlanner application login.
If you wish to post and subscribe to change notifications, you will need to create a forum account.
After you login, you can access your profile by clicking your name floating at the top of the page. Clicking your name will also allow you to subscribe to e-mail change notification messages for the section you are currently looking at.
Note, the forums are a public area. Do not post any private workspace content.
This is something we are thinking about adding support for.
Charles Seybold
I'd add my vote for this.
Bryan deSilva
FYI - This is pretty high on our to-do list; still in the design bucket however. You might see something as earlier as summer 2010.
Charles Seybold
Upgraded to IN PROGRESS. We are working on variable effort rates for tasks and events in the next sprint (Sprint 24)
Charles Seybold
I have also been asked by team members in our organization about this. I am glad to see the position in the schedule. Thank You.
Michael Cunningham
|
PRODUCT Education & Non-Profit Program ©2012 LiquidPlanner, Inc. |
TOUR |
COMPANY |
COMMUNITY |
CONNECT Got a question? Please contact sales or call: Sales: 1-800-971-1601 x111 Corporate web site powered by: |
Hello
Unlike MS Project (unfortunately), liquidplanner doesn't have any concept of duration, only work. So, if someone has a task with work that'll take 8 hrs, liquidplanner assumes that person will complete it in one day.
BUT, that task will actually take a duration of 2 weeks. Sure, the work will be 8 hrs. But it's split across 2 weeks.
There are lots of cases where a person will NOT complete a task at one session. Rather he splits it across a period of time.
e.g., BC = Developing a business case may take a total of 10 hours. But the financial analyst needs to have daily reviews with all his various stakeholders until they're satisfied. So, spend 2 hrs/day over 5 days building his BC.
e.g., # 2: In requirements gathering or during the design phase where specs are being reviewed, the total time spent by the prod mgr or architect may be 20 hrs. But they'll only dedicate 2-3 hrs/day collecting feedback from everyone or working on it before signing-off on the requirements doc or the functional specs.
Why isn't there a way for a user to budget the amount of time that he'll spend on a task?
e.g., in the Work tab, specify that user will only dedicate x hrs/day on that task.
I love the other features in LP. Wish this feature was available.