Please login or join to subscribe to this thread
A quick visual representation of your scope in terms of WBS always helps .
The PMBOK says WBS should contain all of your project scope and having a WBS makes sure that "work does not slip through the cracks" .
Once you have , with the teams help, determined all the work to be achieved through WBS, you can break it into activities and then develop the schedule based on activities.
And yes , nothing stops you from having an overall MS Project schedule split by project phases because every phase will have scope items and work packages from the WBS that can be further decomposed into activities.
If you are running Agile then you can break down the project scope into user stories and run them through the sprints. You can represent the sprints in an MS Project schedule, should you have a requirement to do Management reporting . But this kind of sprint schedule will just be blocks of time . You really maintain your sprints and your user stories and your backlog within a software like JIRA
By Phases or By deliverables?
You can answer the Poll directly as well.
A WBS is not structured to represent time or dependencies between work packages. A schedule on the other hand is usually more readable if tasks are organized chronologically as most FS dependencies are near term. As such, while I prefer to have deliverable organized WBSs, I do phase based schedules. So long as WBS IDs can be defined to ensure traceability between these documents and to others such as a WBS dictionary all should be good.
The ask is when teaching what your choice by phases or by deliverables, that's the basic question. :)
Ideally, phases should be aligned with deliverables. (Note: a "deliverable" may not be a complete product or service; it may be a significant milestone, a prototype, a set of data, or a proof of concept used to make decisions about the next phase.)
Back when I was learning project management, one professor after another would merely say that a phase was simply a way to break up your project into smaller chunks. They have very little guidance about what project phases were, or how they should (and shouldn't) be used.
The question is: If you had to choose between the two, which one it would be for teaching a PM newbi?
By phases? or By deliverables?
A deliverable-based WBS truly shows the intent and purpose of the exercise: identification of the scope, the whole scope and nothing but the scope. To teach using a phase-based approach robs the students from the goals of doing a WBS.
We will see final results :)
Most studentes think that having a logical start to finish approach in their project schedules is the best approach...
I start, I continue working and I finally close down...
Students minds are different that some experienced people...
Again, thanks.... Let's see what others respond.
I teach what I practice so WBS by deliverables ideally, and schedule chronologically which usually means by phase.
Please login or join to reply