My feedback

  1. 6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →

    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…

    Christian supported this idea  · 
    An error occurred while saving the comment
    Christian commented  · 

    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,

Feedback and Knowledge Base