My feedback

1 result found

1. In chart view display hour & or resource name

   6 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  General  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   AdminPhilip Lee (Supporter, Mobilinked) responded

   NORMALLY!, the process of a project is: … → Breakdown Work (estimation) → SOW (contract) → High level plan → Schedule → executing and report → …
   - WBS is for work breaking down, the project team will use it to evaluate the estimate, time and resources needs for contract.
   - WBS is NOT to assign resource and plan the efforts
   - WBS work is NOT same as project task ( there are many methods to break down work, for example by delivery, a delivery will NOT be same as a task)
   - WBS can be a good reference for later planning, but the work in the WBS is not the list of the tasks when planning
   That means WBS is not the step to maintain the schedule (the relationship of task, time and resource)

   but NATURALLY,
   - people like the way WBS do to report project status (process step : executing and tracking) – like to report the project status LIKE the way WBS shows in a tree structure
   - PM needs to report the custom the status of contract executing
   Our project planning app “QuickPlan” provides function to export project as a WBS file, so the PM can use WBS to create the report

   I’d like to emphasise that WBS is for working break-down (and estimation), which is not the step of project schedule and project tracking.

   NORMALLY!, the process of a project is: … → Breakdown Work (estimation) → SOW (contract) → High level plan → Schedule → executing and report → …
   - WBS is for work breaking down, the project team will use it to evaluate the estimate, time and resources needs for contract.
   - WBS is NOT to assign resource and plan the efforts
   - WBS work is NOT same as project task ( there are many methods to break down work, for example by delivery, a delivery will NOT be same as a task)
   - WBS can be a good reference for later planning, but the work in the WBS is not the list of the tasks when planning
   That means WBS is not the step to maintain the schedule (the relationship of task, time and resource)

   but NATURALLY,
   - people like the way WBS do to report project status… more

   Christian supported this idea  ·  May 7, 2016
   An error occurred while saving the comment
   Christian commented  ·  May 7, 2016  ·  Edit…  ·  Delete…

   Thanks for the PM lesson, HOWEVER, I (and many other people) use the WBS as a powerful planning tool on an executive level (brainstorming with the board of directors/steering committee/CEO) and therefore I NEED to add resource's name in order to assign accountability to each branch.
   You see, one thing is the academic idea of an instrument. How you use it in real life and how it makes sense in your organization is a whole different story.

   Therefore, please add the possibility to assign resource's name to each branch/task.

   Thanks in advance,
   Christian

   Save Submitting...