Teamwork to Improve IT Productivity

Dr. Chung LeeVP, Professor of CS

Huree ICT University

Table of Contents

• What, why and how of Teamwork• Theory and model• Group Affinity• CMMI-Team• Conclusion

What is Team?

• Small Group Theory• Multiple member composition small enough.

– Everyone is important.– Everyone is contributing.– Each has different role and responsibility.– One member’s failure is fatal to total team.– Shared responsibility– No one is ignored.

Factors of Team TheorySmall group principle

Group compositionGroup balancingGroup dynamics

Personality Self OrientedTask OrientedPerson Oriented

Size determinationPolya modelColeman model

Balanced vs unbalanced relationshipCompetitive but cooperative as a single unit.Size consideration : 4 - 6

Size Factor

Decision Making Method

Dictatorship -- done by a single individual in chargeOligarchy - By joint response of n membersUnanimity -- Decision made only after every member agreesFixed -- decision made by exactly n membersQuorum -- if minimum n members agree, the decision is

made.Minimal Quorum -- decision made if minimum 1 member

agrees.Independent -- The decision is pre-made regardless of vote.

Teamwork ModelsA) Controlled Centralized (CC) --Chief programmer Team

(Baker, 1972) Chief programmer -- Backup programmer Support staff, Programmers, Specialist,

Support Technician, LibrarianB) Controlled Decentralized (CD) – e.g Synchronized and

Stabilize One leader who coordinates whole project. Give full

liberty to each sub-team C) Democratic Decentralized (DD) Egoless team --

(Weinburg, 1971)

Models

• CC CD DD

Steps of Team formation

• Forming• Storming• Norming• Performing• Adjourning

Detail1. Forming : Initial stage -- first meeting Orientation, introduction, exchange of logistic information2. Storming -- Display of ideas, get ready to work conflict resolution, brainstooming--agree on the general

strategy and procedures Selection of leader and decision of roles. 3. Norming -- Group interaction and effort (90% of group work) Coordinated work Standardized(accepted) behavior and approaches to the

task Increase group cohesion 4. Performing -- Production phase (on-going) Necessary documents are finalized and the team is ready to

work.

Formation

• Balanced vs unbalanced relationship• Competitive but cooperative as a single unit.• • Size consideration : 4 - 6

Result

• Team affinity changes a lot.• Personal relationship is important in deciding

the team performance.• One bad member makes whole team’s

performance suffer.

CMM-CMMICMM –Capability Maturation ModelBy Humphrey of SEI-CMU in 1980’s

5 levels 1. Initial : Producing 2. Repeatable : Consistent production 3. Defined : Organized and documented 4. Managed : Properly monitored and controlled 5. Optimized : Producing

CMMI Model Representations

So Many Models, So Little Time

SoftwareCMM

SoftwareCMM

SystemsSecurity

Engr CMM

SystemsSecurity

Engr CMM

SystemsEngrCMM

SystemsEngrCMM People

CMMPeopleCMM

IPDCMMIPD

CMMSoftware

AcqCMM

SoftwareAcq

CMM

EIA 731EIA 731

• Different structures, formats, terms, ways of measuring maturity

• Causes confusion, especially when using more than one model

• Hard to integrate them in a combined improvement program

• Hard to use multiple models in supplier selection

Conclusion

• Modern IT is complex and teamwork is essential.

• Team need be properly managed.• Group dynamics is important.• More focus on teamwork is essential.

Thank you !!

Баярлалаа!