Assignment 6
Assignment 6
Assignment 6
ASSIGNMENT 6:
1. Organizational structure, team structure and working in team?
Organizational structure:
Introduction:
Any operating organization should have its own structure in order to operate
efficiently. For an organization, the organizational structure is a hierarchy of
people and its functions.
Bureaucratic Structures:
Bureaucratic structures maintain strict hierarchies when it comes to people
management. There are three types of bureaucratic structures:
2
1 - Pre-bureaucratic structures:
This type of organizations lacks the standards. Usually this type of structure can be
observed in small scale, start-up companies. Usually the structure is centralized
and there is only one key decision maker.
The communication is done in one-on-one conversations. This type of structures is
quite helpful for small organizations due to the fact that the founder has the full
control over all the decisions and operations.
2 - Bureaucratic structures:
These structures have a certain degree of standardization. When the organizations
grow complex and large, bureaucratic structures are required for management.
These structures are quite suitable for tall organizations.
3 - Post-bureaucratic Structures:
The organizations that follow post-bureaucratic structures still inherit the strict
hierarchies, but open to more modern ideas and methodologies. They follow
techniques such as total quality management (TQM), culture management, etc.
3
Team structure:
Generalist:
This team structure includes people with broad skills and experience. The
generalists are saddled with the end-to-end development of an individual feature or
complete project. Most outsourcing companies adopt this team structure.
Let's weigh the pros and cons
Pros:
Everyone in the team knows how the product works so it is easier to focus on
product development.
Every team member is competent to complete the task assigned independently
without the need to depend on others.
4
Cons:
Since no one has specific knowledge, there's always a need to onboard new team
members while the project is active.
Specialist structure:
A specialist structure incorporates experts with highly specialized skills and who
are experienced in dealing with narrow tasks and responsibilities. Every team
member is proficient in one niche and is saddled with the responsibilities required
in that area as it contributes to the overall project. Most software development
teams adopt this arrangement.
Pros:
Astounding knowledge of specific project areas.
Ability to develop high-quality systems without lags.
Cons:
Since every team member works independently, it is possible the parts may not fill
into the whole.
Communication gaps may also exist due to the absence of general knowledge.
Hybrid:
A hybrid team structure combines the generalist and the specialist structure. While
a hybrid team focuses on the whole, they can also become specific anytime there is
a need for it. This hybrid is the best of both structures.
Pros:
The team consists of specialists who develop specific elements and generalists who
ensure every part fits into the whole.The development process is highly effective.
5
Cons:
It is most times challenging to manage individuals with different work approaches
It takes time and a huge cost to build a hybrid team.
Ideally, every organization would have specialists and generalists, and of them will
collaborate without any hassle. This is not the same in the real business world.
Every business has its challenges, is time-bound, and budget-constrained. That's
the more reason most software development project teams go for the generalist
structure.
So what are the roles that exist in these teams?
Let's explore them.
Client:
He or she is the owner of the idea. He or she shares foresight and expectation with
the developers. He or she is also responsible for preparing detailed documentation
of his or her idea and clarifies the what's and the whys'. He or she can also
collaborate with technical experts to prepare the product documentation.
6
UX/UI Designer:
This is the person that designs how users interact with the product. He or she
ensures that every feature and functionality addresses the pain point of users and
impacts their bottom line.
Their core responsibilities are functionality and usability.