<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Debating the Organization Structure</title>
	<link>http://www.talash.net/blog/debating-the-organization-structure/108/</link>
	<description>Blog space for Indus Net Community</description>
	<pubDate>Tue, 06 Jan 2009 20:14:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.3</generator>

	<item>
		<title>by: yudhvir singh</title>
		<link>http://www.talash.net/blog/debating-the-organization-structure/108/#comment-181876</link>
		<pubDate>Fri, 07 Mar 2008 11:46:26 +0000</pubDate>
		<guid>http://www.talash.net/blog/debating-the-organization-structure/108/#comment-181876</guid>
					<description>I need to design a project management structure for a BPO firm in india writing content for company websites. Please give me leads. Where do I start?</description>
		<content:encoded><![CDATA[<p>I need to design a project management structure for a BPO firm in india writing content for company websites. Please give me leads. Where do I start?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Mukul Gupta</title>
		<link>http://www.talash.net/blog/debating-the-organization-structure/108/#comment-14928</link>
		<pubDate>Wed, 25 Apr 2007 09:58:28 +0000</pubDate>
		<guid>http://www.talash.net/blog/debating-the-organization-structure/108/#comment-14928</guid>
					<description>Hello Marieke, 

I think as small organization, division by projects make lot of sense. We evolved that way too but later on some 5 years back, we selected the functional organization structure in order to promote technical growth. 

We thought of implementing organization by projects, but for a size of a company with 200 employees where more than 50 simultaneous projects are running, it sounded like a difficult proposition. Moreover, it still does not helps us address the technical growth of the organization seperately from project management. For instance, how do we ensure that we are better at PHP technologies today then last day or we will be better tomorrow than today? Unless, someone is made accountable for it, chances of this happening is very less. 

The easiest and most logical think to do, is too form a seperate project management office as it calls for least amount of modification in the existing structure. 

Mukul Gupta</description>
		<content:encoded><![CDATA[<p>Hello Marieke, </p>
<p>I think as small organization, division by projects make lot of sense. We evolved that way too but later on some 5 years back, we selected the functional organization structure in order to promote technical growth. </p>
<p>We thought of implementing organization by projects, but for a size of a company with 200 employees where more than 50 simultaneous projects are running, it sounded like a difficult proposition. Moreover, it still does not helps us address the technical growth of the organization seperately from project management. For instance, how do we ensure that we are better at PHP technologies today then last day or we will be better tomorrow than today? Unless, someone is made accountable for it, chances of this happening is very less. </p>
<p>The easiest and most logical think to do, is too form a seperate project management office as it calls for least amount of modification in the existing structure. </p>
<p>Mukul Gupta
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Mukul Gupta</title>
		<link>http://www.talash.net/blog/debating-the-organization-structure/108/#comment-14921</link>
		<pubDate>Wed, 25 Apr 2007 09:52:41 +0000</pubDate>
		<guid>http://www.talash.net/blog/debating-the-organization-structure/108/#comment-14921</guid>
					<description>Hello Frank, 

Thanks a lot for writing!

In order to compete effectively, we want to ensure that as an organization we mature both in the technical as well as managerial discpline. 

Moreover, with the implementation of CMMI it is apparent that seperating the project management and engineering discpline makes more sense. We have seen that some of our best developers are simply not interested in trying to learn formal project management disclipline and some of our best managers dont want to learn about engineering process areas within the CMMI model. 

There is definetely room for both these types of people and we want offer them seperate career path. Thus, I think this seperation is a win/win model. 

This model will also help our current functional heads to look beyond project pressure to new areas of improvement which I think will add a lot of dynamism to the company. 

Mukul Gupta</description>
		<content:encoded><![CDATA[<p>Hello Frank, </p>
<p>Thanks a lot for writing!</p>
<p>In order to compete effectively, we want to ensure that as an organization we mature both in the technical as well as managerial discpline. </p>
<p>Moreover, with the implementation of CMMI it is apparent that seperating the project management and engineering discpline makes more sense. We have seen that some of our best developers are simply not interested in trying to learn formal project management disclipline and some of our best managers dont want to learn about engineering process areas within the CMMI model. </p>
<p>There is definetely room for both these types of people and we want offer them seperate career path. Thus, I think this seperation is a win/win model. </p>
<p>This model will also help our current functional heads to look beyond project pressure to new areas of improvement which I think will add a lot of dynamism to the company. </p>
<p>Mukul Gupta
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Marieke Hensel</title>
		<link>http://www.talash.net/blog/debating-the-organization-structure/108/#comment-14457</link>
		<pubDate>Tue, 24 Apr 2007 18:25:09 +0000</pubDate>
		<guid>http://www.talash.net/blog/debating-the-organization-structure/108/#comment-14457</guid>
					<description>Thanks for this overview! I have to get the structure down for our new company and this really helps me. As you already give a good overview of advantages and disadvantages. 

BTW, our company will go in the direction of organizing by project teams. Because it is flexible and brings the energy in a project because they choose for one project or another.

Marieke Hensel
www.henselhosting.com
The Netherlands</description>
		<content:encoded><![CDATA[<p>Thanks for this overview! I have to get the structure down for our new company and this really helps me. As you already give a good overview of advantages and disadvantages. </p>
<p>BTW, our company will go in the direction of organizing by project teams. Because it is flexible and brings the energy in a project because they choose for one project or another.</p>
<p>Marieke Hensel<br />
<a href='http://www.henselhosting.com' rel='nofollow'>www.henselhosting.com</a><br />
The Netherlands
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Frank Kanu</title>
		<link>http://www.talash.net/blog/debating-the-organization-structure/108/#comment-14410</link>
		<pubDate>Tue, 24 Apr 2007 16:26:55 +0000</pubDate>
		<guid>http://www.talash.net/blog/debating-the-organization-structure/108/#comment-14410</guid>
					<description>The most important question seems unanswered:
Why do you want to restructure?

Do the employees stand behind a restructure? How will the restructure influence the business?

What do the customers think?</description>
		<content:encoded><![CDATA[<p>The most important question seems unanswered:<br />
Why do you want to restructure?</p>
<p>Do the employees stand behind a restructure? How will the restructure influence the business?</p>
<p>What do the customers think?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: David Meggitt</title>
		<link>http://www.talash.net/blog/debating-the-organization-structure/108/#comment-14332</link>
		<pubDate>Tue, 24 Apr 2007 13:42:51 +0000</pubDate>
		<guid>http://www.talash.net/blog/debating-the-organization-structure/108/#comment-14332</guid>
					<description>Good points and an ongoing area of difficulty.

Matrix management never really worked...having two bosses is a problem.

Consider instead the thinking behind value networks as applied to project management. Look under Articles of the site www.value-networks.com - Will The Real Project Please Stand Up. This is now published.

Also have a looks at how projects help organisations become fit for purpose. http://tinyurl.com/2z3ok9

David Meggitt
www.meggittbird.net
UK</description>
		<content:encoded><![CDATA[<p>Good points and an ongoing area of difficulty.</p>
<p>Matrix management never really worked&#8230;having two bosses is a problem.</p>
<p>Consider instead the thinking behind value networks as applied to project management. Look under Articles of the site <a href='http://www.value-networks.com' rel='nofollow'>www.value-networks.com</a> - Will The Real Project Please Stand Up. This is now published.</p>
<p>Also have a looks at how projects help organisations become fit for purpose. <a href='http://tinyurl.com/2z3ok9' rel='nofollow'>http://tinyurl.com/2z3ok9</a></p>
<p>David Meggitt<br />
<a href='http://www.meggittbird.net' rel='nofollow'>www.meggittbird.net</a><br />
UK
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
