Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

High Level Design in Project Initiation ?

Status
Not open for further replies.

yusufkaragol

Programmer
Jan 24, 2011
1
TR
Hi everybody,
I'm a software developer but nowadays I've been helping to my project manager to create the work breakdown structure for our new coming project.
But I cannot imagine that how could it be possible without designing the general structure of the deliverables and interfaces between them.
I suppose at least a design activity (such as defining the product components and assigning requirements to them as in CMMI's requirement development) is needed to create wbs.
What is the point(s) I missed?
 
According to PMBOK, the Define Activites process creates the WBS by identifying deliverables at the Lowest Level called a work package. Inputs are the Scope Baseline, Organizational Process Assets (policies, procedures, guidelines, historical info from previous projects, etc as available from the organization PMO or similar), and Enterprise Environmental Factors such as tools (like MS Project).

-------------------------
The trouble with doing something right the first time is that nobody appreciates how difficult it was - Steven Wright
 
You are quite right. It is self delusional.

In fact there is nothing to stop you doing a WBS but the level of abstraction would mean it would be virtually meaningless given the lack of detail.

I can see the logic in a WBS but in 30 years and 30 projects/programmes I've never done one or seen one, and I've worked for some of the biggest companies in the World.

Tell you PM to chill out and get a life.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top