IT8075-UNIT-5-Best-methods-of-staff-selection-Motivation SPM
IT8075-UNIT-5-Best-methods-of-staff-selection-Motivation SPM
Moreover, organization will face less of absenteeism and employee turnover problems.
By selecting right candidate for the required job, organization will also save time and
money. Proper screening of candidates takes place during selection procedure. All the
potential candidates who apply for the given job are tested.
But selection must be differentiated from recruitment, though these are two phases of
employment process. Recruitment is considered to be a positive process as it motivates
more of candidates to apply for the job. It creates a pool of applicants. It is just sourcing
of data.
While selection is a negative process as the inappropriate candidates are rejected here.
Recruitment precedes selection in staffing process. Selection involves choosing the best
candidate with best abilities, skills andknowledge for the required job.
1. Preliminary Interviews- It is used to eliminate those candidates who do not meet the
minimum eligiblity criteria laid down by the organization. The skills, academic and
family background, competencies and interests of the
candidate are examined during preliminary interview. Preliminary interviews are less
formalized and planned than the final interviews. The candidates are given a brief up
about the company and the job profile; and it is also examined how much the candidate
knows about the company.
Preliminary interviews are also called screening interviews.
2. Application blanks- The candidates who clear the preliminary interview are required to
fill application blank. It contains data record of the candidates such as details about age,
qualifications, reason for leaving previous job, experience, etc.
3. Written Tests- Various written tests conducted during selection procedure are aptitude
test, intelligence test, reasoning
Motivation
• Motivation and application can often make up for shortfalls in innate skills
• Taylor’s approach - financial incentives
• Abraham Maslow (1908-1970)
– motivations vary from individual to individual
Maslow’s model implies that people will be motivated by different things at different
times. Also that people always feel dissatisfied, but the focus of the dissatisfaction
changes over time.
Herzberg’s two factor theory
Herzberg suggested two sets of factors affected job satisfaction
1. Hygiene or maintenance factors – make you dissatisfied if they are not right e.g. pay,
working conditions
2. Motivators – make you feel the job is worthwhile e.g. a sense of achievement
Effort
Challenges
Work distributed to contractors- Careful
Procedures-formally expressed
Coordination- difficult
Payment(fixed price/piece-rate)
Lack of trust
Quality Assesment
Differenct time zones Communication and coordination
Communication plan
Communication is important in all projects but a vital matter in case of dispersed projects.
Because of this, consideration of the way that project stakeholders will communicate ought to
be a part of the project planning process.
• Communication Genre
– Refers to the method of communication
• Communication Plan
– Arrangements for communication between project stakeholders can be
documented
Time/place constraints on communication
- One way of categorizing types of communication.
project
– Document in a communication plan
• What. This contains the name of a particular communication event, e.g, ‘kick-
off meeting’, or channel, e.g. ‘project intranet site’.
• Who/target. The target audience for the communication.
• Purpose. What the communication is to achieve.
• When/frequency. If the communication is by means of a single event, then a date
can be supplied. If the event is a recurring one, such as a progress meeting then the
frequency should be indicated.
• Type/method. The nature of the communication, e.g., a meeting or a
distributed document.
• Responsibility. The person who initiates the communication.
These choices are then embodied in a software project management plan. Software
project management addresses both the process of software development and the
desired functional characteristics of the final software product. A complete software
project management plan is the design, implementation, control and test strategy for a
software development process.
operational decisions to be taken during this extended activity. There are many
different approaches to control the complexity of this activity which can be viewed at
two levels.
There are those approaches which are concerned with high level decisions and
processes such as the Capability Maturity Model and the ISO series, and there are
methods which deal with the details of the day to day activities of the project
managers and software development teams.
These latter methods include COCOMO, PRINCE and Function Point Analysis.
Relevant ethical principles must be established in order to identify the ethical issues
associated with software project management.
Ethics comprises both practice and reflection van Luijk, It is sufficient to consider only
ethics practice in this paper because software project management is concerned
primarily with action that guides others towards some common goal rather than
conceptual reflection of the role and value of project management.
An interesting list of generic questions was devised by John McLeod in Parker et al, pp
to help determine the ethical nature of actions within IT. These are relevant to
software project management because they address many of the project management
tasks with the exception of full consideration of the supplier customer relationship.
The software project is concerned with the delivery of an output by a supplier the
project team to a customer under some agreement. It is irrelevant whether this is an
inhouse arrangement or whether it is between two independent organisations or
whether it is a combination of both. According to Velasquez, , such an agreement is
concerned with output quality and moral liability.
Velasquez argues that the principles of due care and social cost must take effect in
these situations so that suppliers accept their obligations to customers and the wider
community to provide goods and services that are adequate and beyond moral
reproach. Whilst it is recognised that the development of a piece of software might
have its own special set of problems and challenges that have to managed there are
many similarities in all software projects that means it is worth considering a generic
approach which will lay down foundations for the management of all software
projects.
How to Run Successful Projects, in the British Computer Society Practitioner Series,
OConnell, provides details of the Structured Project Management SPM approach. He
explains that SPM is a practical methodology that, as De Marco and Lister, state, is a
quotbasic approach one takes to getting a job donequot. This appears to be a generic
approach which is practical rather than conceptual and provides practitioners with
realistic guidance in undertaking the complex activity of project management. SPM
comprises ten steps as shown in Figure .
The first five steps are concerned with planning and the remaining five deal with
implementing the plan and achieving the goal.
OConnell states that most projects succeed or fail because of decisions made during
the planning stage thereby justifying the fact that half of the effort expended in the
SPM approach is on preparation.
In traditional software project management the stated needs of the customer are the
primary item of concern in stating the project objectives. Recently, there has been
some recognition that in defining how software will address those needs the customer
is also presented with a predefined set of constraints which limit the customers
freedom of expression McCarthy, .
There is a mutual incompatibility between some customer needs, for example, the
amount of code required to make a system easy to use makes a system difficult to
modify. The balancing of these items is an ethical dimension in the development of a
software product. But such considerations are limited in scope to the customer.
hey discovered, with the exception of vendors, all stakeholders involved in evaluation were internal to
the organisations. The reason for this restricted involvement is that these are the only stakeholders
originally identified in the traditional project goals
Leadership
Leadership is generally taken to mean the ability to influence others in a group to act in a
particular way to achieve group goals. A leader is not necessarily a good manager or vice versa, as
managers have other roles such as organizing, planning and controlling.
Types of authority/power
Position power
• Expert power: holder can carry out specialist tasks that are in demand
• Information power: holder has access to needed information
• Referent power: based on personal attractiveness or charisma
Leadership styles
• Directive autocrat: makes decisions alone: close supervision of implementation
• Permissive autocrat: makes decisions alone: subordinates have latitude inimplementation
• Directive democrat: makes decisions participatively: close supervision Of implementation
• Permissive democrat: makes decisions participatively: subordinates have latitude in
implementation
Where there is uncertainty about the way job is to be done or staff are inexperienced
they welcome task oriented supervision
Uncertainty is reduced – people orientation more important
Risk that with reduction of uncertainty, managers have time on their hands and
become more task oriented (interfering)
Essentially staff want hands-on management when they need guidance. Once they know
the
job they want to be left to get on with it!
Managing people
Managing People and Organizing Teams
Often the most difficult areas in managing software development projects
“Most managers are willing to concede the idea that they’ve got more people
worries than technical worries. But they seldom manage that way.” (DeMarco &
Lister, Peopleware)
One reason: technical experts become managers
Important areas:
Selectingright people for the job
Motivating people
Working as a team
Suggested Skills for a Project Manager
Communication skills: listening, persuading
Organizational skills: planning,goal-setting, analyzing
Team building skills: empathy, motivation
Leadership skills: set example, energetic, positive, delegates, vision (big picture)
Coping skills: flexibility, creativity, patience, persistence
Technological skills: experience, project knowledge
Negotiation skills: negotiates with management to get good team members, enough
resources and reasonable goals and schedule.
PM’s Role between Management and Project Team
Management/customer might set conflicting/impossible requirements and goals forthe
project
Project team needs goals that are reachable within project schedule
Project manager is a link between the groups and negotiates the resources and the
goals.
How to Build Effective Teams
Team cohesion
Kick-off meeting
Collocation
• The Hawthorne experiments investigated the effect of various factors such as improved
lightning on productivity. It was found that the productivity of the control group (whose
working conditions such as lighting were not changed) increased – the fact that someone
singled them out for observation improved their motivation.
Theory X
Other research found experience better than maths skills as a guide to software
skills
• Some research suggested software developers less sociable than other workers
• Later surveys have found no significant social differences between IT workers and
others – this could be result of broader role of IT in organizations
There is some evidence that there is a very wide variation in software development
skills – going back many years. Some research found that computer people had fewer
social needs than other professionals. Later research has not found any significant
difference – this may be because the ‘ICT profession’ has become broader in scope.
A selection process/Recruitment Process
Organizational Structures
Objectives
• Departments
– Criteria: Staff Specialization, Product Lines, Categories of Customers, Geo.
Location
– Banking, Embedded application, Telecom
– Verticals
• Projects and Teams
– Every department several projects
– Each project has a separate team of developers
Department Structure
• Functional Format
• Project Format
• Matrix Format
• Functional Format
– Tackle Crisis
Team Structure
• Denotes
– Reporting
– Responsibility
– Communication Structures (in Individual projects)
• Different project different styles
• Team Structures
– Chief Programmer
– Democratic
– Mixed Team Organization
Chief Programmer Team
The job characteristics model, designed by Hackman and Oldham, is based on the idea
that the task itself is key to employee motivation. Specifically, a boring and
monotonous job stifles motivation to perform well, whereas a challenging job enhances
motivation. Variety, autonomy and decision authority are three ways of adding
challenge to a job. Job enrichment and job rotation are the two ways of adding variety
and challenge.
It states that there are five core job characteristics (skill variety, task identity, task
significance, autonomy, and feedback) which impact three critical psychological states
(experienced meaningfulness, experienced responsibility for outcomes, and knowledge
of the actual results), in turn influencing work outcomes (job satisfaction, absenteeism,
work motivation, etc.). The five core job characteristics can be combined to form a
motivating potential score (MPS) for a job, which can be used as an index of how likely
a job is to affect an employee's attitudes and behaviors
Hackman and Oldham’s job characteristics theory proposes that high motivation is related to
experiencing three psychological states whilst working:
1. Meaningfulness of work
That labour has meaning to you, something that you can relate to, and does not occur just as a
set of movements to be repeated. This is fundamental to intrinsic motivation, i.e. that work is
motivating in an of itself (as opposed to motivatingonly as a means to an end).
2. Responsibility
That you have been given the opportunity to be a success or failure at your job because
sufficient freedom of action has given you. This would include the abilityto make changes and
incorporate the learning you gain whilst doing the job.
3. Knowledge of outcomes
This is important for two reasons. Firstly to provide the person knowledge on how successful
their work has been, which in turn enables them to learn from mistakes. The second is to
connect them emotionally to the customer of their outputs, thus giving further purpose to the
work (e.g. I may only work on a production line, but I know that the food rations I produce are
used to help people in disaster areas, saving many lives).
In turn, each of these critical states are derived from certain characteristics of the job:
1. Meaningfulness of work
The work must be experienced as meaningful (his/her contribution significantly affects the
overall effectiveness of the organization). This is derived from:
o Skill variety
Using an appropriate variety of your skills and talents: too many might be overwhelming, too
few, boring.
o Task Identity
Being able to identify with the work at hand as more whole and complete, and hence enabling
more pride to be taken in the outcome of that work (e.g. if you just add one nut to one bolt in
the same spot every time a washing machine goes past it is much less motivating than being the
person responsible for the drum attachment and associated work area (even as part of a group).
o Task Significance
Being able to identify the task as contributing to something wider, to society or a group over
and beyond the self. For example, the theory suggests that I will be more motivated if I am
contributing to the whole firm’s bonus this year, looking after someone or making something
that will benefit someone else. Conversely I will be less motivated if I am only making a
faceless owner wealthier, or am making some pointless item (e.g. corporate give-away gifts).
2. Responsibility
Responsibility is derived from autonomy, as in the job provides substantial freedom,
independence and discretion to the individual in scheduling the work and in determining the
procedures to be used in carrying it out)
3. Knowledge of outcomes
This comes from feedback. It implies an employee awareness of how effective he/she is
converting his/her effort into performance. This can be anything from production figures
through to customer satisfaction scores. The point is that the feedback offers information that
once you know, you can use to do things differently if you wish. Feedback can come from
other people or the job itself. Knowing these critical job characteristics, the theory goes, it is
then possible to derive the key components of the design of a job and redesign it:
1. Varying work to enable skill variety
2. Assigning work to groups to increase the wholeness of the product produced and give a group
to enhance significance
3. Delegate tasks to their lowest possible level to create autonomy and hence responsibility
4. Connect people to the outcomes of their work and the customers that receive them so as to provide
feedback for learning
Stress, Health & Safety
WHAT IS STRESS?
Stress is your mind and body’s response or reaction to a real or imagined threat, event
or change.
The threat, event or change are commonly called stressors. Stressors can be internal
(thoughts, beliefs, attitudes or external (loss, tragedy, change).
EUSTRESS
Eustress or positive stress occurs when your level of stress is high enough to motivate you to
move into action to get things accomplished.
DISTRESS
Distress or negative stress occurs when your level of stress is either too high or too low and
your body and/or mind begin to respond negatively to the stressors.
ALARM STAGE
As you begin to experience a stressful event or perceive something to be stressful
psychological changes occur in your body. This experience or perception disrupts your body’s
normal balance and immediately your body begins to respond to the stressor(s) as effectively as
possible.
EXAMPLES
Cardiac - increased heart rate
Respiratory - increased respiration
Skin - decreased temperature
EXAMPLES
Behavior indicators include: lack of enthusiasm for family, school, work or life in general,
withdrawal, change in eating habits, insomnia, hypersomnia, anger, fatigue.
Cognitive Indicators include: poor problem solving, confusion, nightmares, hyper-vigilance.
EXHAUSTION STAGE
During this stage the stressor is not being managed effectively and the body and mind are not
able to repair the damage.
Health & Safety
Mechanisms for Effects of Exercise on Stress Reduction
Distraction
Endorphin
Thermogenic
Self-esteem
Emotion-focused
o Praying
o Relaxing
o Exercising
o Seeking passive social support
Avoidant
Ignoring
Escaping
Appraisal-focused
Cognitive restructuring
Knowledge/skills
Deep breathing
Take mind off of problems
Biofeedback
Utilizes machines that monitor physiological responses
Useful for decreasing tension headaches, asthma attacks, hypertension and
phobias.
Meditation / Imagery
Relies on deep breathing
Facilitated by images of peace and relaxation
Working in teams
Introduction:
Θ Software based systems will be huge, also software tool contains five million lines of
code.
Θ So that the work is shared between individual software developers within teams and
betweengroup of developers.
Θ Team working will enhance the communication between individual developers and
withinteams and across teams.
Θ Team - Group of people who are working together.
- Small group environment
Θ The term Project Team refers all the people working on a project.
Θ The people who are working in project team may sit in different workgroups at some
distance from each other.
Θ These groups can also change over time.
Θ Thus individual developers are transfer between teams during the period of project start
andfinish.
Θ Team is created to do joint assignment
Θ To perform the work assignments which are allocated to the staff, the organization needs
oneform of coordination between groups and individuals within a project.
Θ Communication genres
- refers Method of Communication
- It is selected and developed to deal with particular need for project
coordination.
- The arrangements for communication between stakeholders are
documented in
communication plan
Θ This Team work has an influence on all stages of step wise project planning framework.
Problems occur when there is an imbalance between the role types of people in a group.
Group Performance`
In many projects, some solutions are needed about which tasks are carried out
collectively asa team and which are allotted to individuals.
It is defined by “Some work yields better results if carried out as a team while some
thingsare slowed down if the work is not partitioned on an individual basis”.
The group tasks are categorized into:
o Additive Tasks - Effects of each participant are added to get final
result
- People involved are interchangeable
o Compensatory Tasks - Solutions of individual group members are pooled
• Errors of some are compensated by the inputs
from others
o Disjunctive Tasks - Means there is only one correct answer.
- It depends on someone coming up with one
right answer and others recognizing it as being
correct
o Conjunctive Tasks - Means joining the tasks
- Progress is governed by the rate of slowest
performer
- The overall task is not completed until all
participantshave completed.
Decision Making
• Decisions made by the team as a whole are more likely to be accepted that those
that areimposed
• Complementary skills and expertise
• Communicate freely/get ideas
• Brainstorming techniques
• Aim is to have involvement of end users?
– Prototyping and participatory approaches
– JAD(Joint Application Development)
Barriers to good team decisions
• Inter-personal conflicts –team formation
• Conflicts tend to be a dampened by emergence of group norms – shared group
opinions andattitudes
• Risky shift – people in groups are more likely to make risky decisions than they
would asindividuals
Delphi approach
To avoid dominant personalities intruding the following approach is adopted
1. Enlist co-operation of experts
2. Moderator presents experts with problem
3. Experts send in their recommendations to the moderator
4. Recommendations are collated and circulated to all experts
5. Experts comment on ideas of others and modify their own recommendation if so moved
6. If moderator detects a consensus, stop; else back to 4
Team ‘heedfulness’
• Football Team.
• Where group members are aware of the activities of other members that contribute to
overallgroup success
• Impression of a ‘collective mind’
• Some attempts to promote this:
– Egoless programming
– Chief programmer teams
– XP
– Scrum
Egoless programming
• Gerry Weinberg noted a tendency for programmers to be protective of their code and to
resistperceived criticisms by others of the code
• Fred Brooks was concerned about the need to maintain ‘design consistency’ in large
softwaresystems
• Appointment of key programmers, Chief Programmers, with responsibilities for
definingrequirements, designing, writing and test software code
• Assisted by a support team: co-pilot – shared coding, editor who typed in new or
changedcode, program clerk who write and maintain documentation and tester
• Problem – finding staff capable of the chief programmer role
Extreme programming
XP can be seen as an attempt to improve team heedfulness and reduce the length of
communication paths (the time between something being recorded and it being used)