Dirty-Work Group Based Organizational Structure

Dirty-Work Group Organization Structure

Introduction

A team does not and can not exist as an island. In an organizational setup, it has to indulge in intra-organizational and external communications. How does the concept of Dirty-work group provide a solution to this and how would an organization based on this idea look like?

In this article, we introduce the concept of interfaces to a Dirty-Work Group and propose an organizational structure.

Interfaces

As a Dirty-Work group‘s organization is internal to a group, from the outside it would look like a black box. Proper interfaces should be defined for various kinds of interactions. The most apparent communications are of following types:

Internal - Dirty-Work Group  Internal:  This interface is one point contact for all intra-company communications. Any request for information from other teams, dissemination of information, etc to the Dirty-Work Group is through this interface. Any member can pick this activity as their Good-Work (Good Work Group) and if none exits then as a Dirty-Work (Dirty Work Group).

External - Dirty-Work Group  External:  This interface is one point contact for all external communications. Any request for information from the press, other companies, agencies, etc to the Dirty-Work Group is through this interface. Any member can pick this activity as their Good-Work and if none exits then as a Dirty-Work.

Hierarchical - Dirty-Work Group  Hierarchical:  This interface is one point contact for all reporting to the higher level of management and their communication to the group. Any member can pick this activity as their Good-Work and if none exits then as a Dirty-Work.

Dynamics

Consider an organization named Any Organization Ltd. Its top management can be a Dirty-Work Group of all or some of these people:

  • CFO: Chief Financial Officer
  • CIO: Chief Information Officer
  • CTO: Chief Technology Officer
  • CMSO: Chief Marketing and Sales Officer
  • CHRO: Chief Human Resources Officer
  • CLO: One who manages buildings, offices, infrastructure, canteen, transportation and all that none of the above have to worry about – the ‘Handy Man’ officer.

Let there be three Dirty-Work Group working on various projects. One of them is a high visibility project about which business community is also interested.

Dirty-Work Group Organization Structure

Each member of each group after picking the Good-Work and the Dirty-Work will also pick whether to be an interface. And if yes, then what kind of interface. Internal, External or Hierarchical. The teams which do not need to interact may not pick an External interface or pick one when needed.

More Reading

Setting Up Web Server in Mac OS X (macOS Sierra 10.12)

Setting Up Web Server in Mac OS X (macOS Sierra 10.12)

Was setting up a web server in my Mac OS X after a long time. Apple has removed ‘Web Server’ from Sharing in Settings. So, thought will share the steps to save you folks some time:

Step 1: Check if Web Server is up and running

$ sudo apachectl status

Password:

Go to http://localhost:80/server-status in the web browser of your choice.

Note that mod_status must be enabled for this to work.

Looks OK. But if you ever wanted to start / stop / restart, the ‘apachectl’ command works fine.

$ sudo apachectl stop

$ sudo apachectl start

Step 2: Your Web Directory

It is located at:

$  cd /Library/WebServer/Documents/

The default permissions are for user ‘root’ and group ‘wheel’. I changed them to my user logged user so as to make file editing easier (very useful during development).

$sudo chgrp -R staff Documents/

$  sudo chown -R dinker Documents/

Then I make a soft link to this fir from my home dir to make it easy to navigate to Documents/

$ cd

$ ln -s /Library/WebServer/Documents/ www

The default index file is index.html.en. You can edit it to test changes. To access the local webserver, you need to access http://localhost from your browser.

Step 3: Enabling PHP

If you rename index.html.en to index.php, you will get this error:

Mac OS X Forbidden You don't have permission to access / on this web server.

 

“Forbidden You don’t have permission to access / on this server.” This means web server is looking specifically for index.html.

Usually, when that happens, it will list the files in that directory. By default, apache setting do not allow listing. Hence this error.

You can see this in the error logs too:

$ cd /var/log/apache2/

$ tail error_log 

[Thu Nov 16 12:39:28.151000 2017] [autoindex:error] [pid 16262] [client ::1:62248] 
AH01276: Cannot serve directory /Library/WebServer/Documents/: No matching 
DirectoryIndex (index.html) found, and server-generated directory index forbidden by 
Options directive

To fix:

$ sudo vi /etc/apache2/httpd.conf

Search for php to find this line:

# LoadModule php5_module libexec/apache2/libphp5.so

and uncomment it by removing #. Then restart apache server.

$ sudo apachectl restart

Reload http://localhost and you should be good!