Please note: I reserve the right to delete comments that are offensive or off-topic.

Leave a Reply

Your email address will not be published. Required fields are marked *

4 thoughts on “How to Break Down Your Projects

  1. Hi Harry,

    I really like your approach to explain the WBS set of mind. (Break Down).

    I would like to know if you be kind enough to finish all the arms from the Mindmap, you open up the Initiation, and Planning, would you be able to share the same break down for Executing, Monitoring and Controlling and Closing .

    Thanks a lot,

    Fred

  2. Hello Harry!

    Thank you for this video. In my career it was interesting to see how difficult it can be to explain the difference between the “Deliverables” and the “Activities” (or Objectives and Tasks). The Noun vs. Verb is one of the good explanations.

    With regard to creating a convenient WBS I have happened to see different approaches, some involving breaking down the project into Phases, others suggesting to break down projects into blocks that are assigned to one or another group of resources (e.g., Coding Team, Testing Team, Training Team). It would be helpful to know your experience in this matter and to learn the best practices, if any, when one or another WBS creating approach is most suitable.

    Thanks for your great business!

    • Hi Sergey,

      For large projects, it can be helpful to break a project into phases. For example, you may have a project that will take 12 months to deliver. You could prioritize the requirements and deliver the project in stages (ex. Stage 1, Stage 2, Stage 3). In this manner, we could deliver the highest priority deliverables quicker. This is what I call staged projects. Another approach would be to use an agile approach where you are completing monthly sprints; at some point, you could implement a set of sprints. Again, this allows you to deliver high priority items sooner.

      I am not a fan of breaking projects into groups (e.g., requirements, coding, testing, development, training, etc.). Why? I have found that projects are best delivered by a cross-functional team that includes representatives from the key stakeholder groups such as users, developers, testers, and trainers. This approach greatly enhances communication and accountability.

      I hope this helps! Best wishes.