I want to train a few new team members in the use of Microsoft Project. All are familiar with the basics but I want to explain WBS hierarchy and predecessors. I am trying to think of an 'every day life' example of a project that most people would agree on the contents and logic so we can use this to build a plan together. I have used 'cook a meal' previously, but would prefer something over longer timescale.
I think the best example would be building a house (image source):
Although people might not have built houses before, they have seen it happen at some point or another, and there is a good familiarity with the concept since we all live in houses :).
And it's also a good model to use because it allows you to go in as wide or as deep as necessary to explain various concepts. There are also dependencies between each part (since you can't build the walls without a foundation, or the roof without the walls, etc), you might need to add buffers to your schedule (because of the weather, for example). There is also procurement of materials, if you want to throw that in the mix too, and so on.
I suggest you choose an example that is relevant to the business domain that your team are expected to deal with. WBS and schedule makes sense for some kinds of work but not so for others. For example it's not usually a good idea to use WBS for software products; Product Breakdown Structure makes much more sense.
Are you as a contractor offering Works Breakdown Structure to a client, or are you somebody who is in the process of purchasing/building a home and wanting to organize his vendors with Microsoft Project. The reason I'm asking is that it will impact you're training strategy. Having Project as a resource when building a home is a great idea... having everybody using it to a potential is a luxury that some successful project engineers should utilize. There will be variants in place of Project already I'm sure. It's just uncommon these days or so I think.
Pick an example in your business domain with all different task dependency types
I want to explain WBS hierarchy and predecessors
Pick an example in your business domain, but make sure you bring in all different task dependency types.
- FS (Finish-To-Start) Dependency: This is the most common dependency found in any project. Task A must finish in order for Task B to start. So, you don't have to think hard to find this one.
- FS (Finish-To-Start) Dependency with a lag: This is not that common. For example, you can't paint a wall immediately after plastering. You have to wait until the plaster is dry.
- SS (Start-To-Start) Dependency: For example, the writing of a business proposal must have begun in order for review/editing of the proposal to start.
- FF (Finish-To-Finish) Dependency: For example, electrical work cannot finish until drywalling is complete.
- SF (Start-to-Finish) dependency: This is a very rare one. For example, start of the next shift of the security guards has to happen for the previous shift to end. If the next shift security guards don't turn up, the previous shift security guards have to continue their duty.