System Analyst and Project Manager – Comprehensive Study Notes

Learning Outcomes

  • By the end of this lesson you should be able to:
    • Describe and differentiate the roles & skills of a Systems Analyst (SA) and a Project Manager (PM).
    • Explain the phenomenon of resistance to change including:
    • Reasons (root causes)
    • Observable effects in the workplace
    • Practical methods to overcome or mitigate the resistance

Key Terms

  • System Analyst
  • Project Manager
  • Project Management

Systems Analyst

Definition & General Purpose

  • Acts as the middle‐man who liaises between customers, the IT team and stakeholders.
  • Integrates business requirements with appropriate technologies to ensure smooth business operations.
  • Analyzes business processes, computer systems and infrastructure to craft effective strategies that satisfy daily organisational needs.
  • Designs information-system architectures that are:
    • Aligned with user requirements (serve as a blueprint for programmers).
    • Easy to upgrade or scale in the future.

Core Responsibilities & Relationship-Building

  • Build and maintain good client rapport to extract complete requirements.
  • Translate requirements into clear, complete specifications for the development team.
  • Continuously know what clients want – both stated and latent needs.

Major Roles (Internal & External)

  • Consultant (usually external)
    • Hired specifically to tackle information-system issues.
    • Advantages: fresh, unbiased perspectives.
    • Disadvantages: unfamiliar with organisational culture; relies heavily on second-hand information.
  • Supporting Expert (internal)
    • Advises on hardware, software, small modifications that affect limited scope (e.g.
      single department).
    • Not responsible for overall project management.
  • Agent of Change (can be internal or external)
    • Serves as a catalyst to optimise information-system use.
    • Drives improvements in:
    • Business process effectiveness & efficiency
    • Customer satisfaction
    • Production/output levels
    • Data management & information quality

Skill Sets Required

Analytical Skills
  • Systemic vision: ability to see the organisation as an interrelated system.
  • Problem identification & solution:
    • Compare current vs desired situations.
    • Devise multiple solution paths, then select optimal approach.
  • Organisational knowledge:
    • Understand how work officially & informally gets done.
    • Be aware of regulations, policies, strategy, competitive & regulatory environment.
  • Systems Thinking:
    • Visualise inputs → processes → outputs and feedback loops.
    • Convert complex real-world operations into abstract models/diagrams for design.
Technical Skills
  • Stay up-to-date with technologies such as:
    • Computers: PCs, minis, mainframes
    • Networks: LAN, WAN, VPN – plus administration & security
    • Operating Systems: Unix, Mac OS, Windows
    • Data-exchange protocols: ftp, http, etc.
    • Programming languages: C++, Java, XML …
    • IS applications: databases, MIS, DSS, etc.
    • Development environments & tools: report generators, office automation, etc.
  • Understand potentials & limitations so proposed solutions are feasible.
Interpersonal & Communication Skills
  • Clearly explain significance of the information system to non-technical stakeholders.
  • Convince clients of efficiency / effectiveness gains.
  • Conduct fact-finding techniques (interviews, surveys, observation, document analysis).
  • Teamwork: communicate accurate information to PM, programmers, UI/UX designers, QA, etc.
  • Expectation management:
    • Keep clients updated on progress.
    • Collaborate with PM to refine timeline & budget.

Resistance to Change

Reasons People Resist Technology-Driven Change

  1. Threat to job security
    • Automation may replace traditional tasks
    • Distrust towards management motives
  2. Reduction in self-esteem & reputation
    • Fear of lacking necessary skills
    • Anxiety caused by the unknown/fear of failure
    • Poor communication about the change; perceived effort to learn is high
  3. Reduction in social satisfaction
    • Not consulted; feel excluded
    • Unclear benefits or rationale for change

Observable Effects When Resistance Occurs

  • Withholding facts – vital data not provided to the SA.
  • Providing inaccurate data – data manipulation, sabotage.
  • Displaying indifference – lack of cooperation, passive resistance.

Methods to Overcome Resistance

  1. Transparent Communication
    • Keep people informed; emphasise ease of use and personal impact.
  2. Job Reassignment
    • Transfer staff to departments where roles remain relevant.
  3. Retraining & Support
    • Provide customised training: e-learning for tech-savvy, group workshops for others.
  4. Employee Participation
    • Involve end-users from the start; demonstrate that technology supplements rather than substitutes their skills.

Project Manager

Definition & Success Criteria

  • Person in charge of planning & executing a project.
  • A project is considered successful when it:
    Meets Requirements∧Stays Within Budget∧Is Delivered On Time∧Satisfies Users\text{Meets Requirements} \land \text{Stays Within Budget} \land \text{Is Delivered On Time} \land \text{Satisfies Users}

Core Functions & Activities

Project Planning
  • Identify tasks, resources, costs, team members.
  • Produce high-level work breakdown structure (WBS).
Project Scheduling
  • Develop timetables showing task dependencies & critical path.
  • Determine:
    • Duration of each activity
    • Logical order / prerequisite relationships
    • Start & end times (no activity starts before predecessors finish)
    • Resource allocation to balance workloads
Monitoring & Controlling
  • Guide, supervise & coordinate team workload.
  • Weekly meetings, checkpoint reviews.
  • Structured walkthroughs – peer review of deliverables to ensure quality.
Reporting
  • Prepare progress reports for management, users & team.
  • Hold status meetings to surface issues & opportunities.
  • Use Gantt Charts to illustrate schedule vs actual progress.

Leadership Qualities

  • Wise & good leadership is essential.
  • Must motivate, negotiate conflicts, manage stakeholder expectations, & make timely decisions.

Project Management Issues

Business Issues

  • Systems must solve real business problems or seize opportunities.
  • Failure → lower morale & productivity.
  • Project creep (scope creep) – uncontrolled scope growth after project initiation.

Budget Issues

  • Cost overruns stem from:
    • Unrealistic estimates
    • Incomplete life-cycle cost forecasting
    • Poor progress monitoring / slow reaction to warning signs
    • Schedule delays, unforeseen factors
    • HR problems: high turnover, inadequate training, low motivation

Schedule Issues

  • Missed timetables & milestones due to:
    • Ignoring task dependencies
    • Confusing effort with progress
    • Weak monitoring & control
    • Personality conflicts or staff turnover

Critical Recovery & Brooks’ Law

  • PM’s handling of problems is critical when issues arise.
  • Sometimes trimming less-critical requirements can still deliver on time & budget.
  • Brooks’ Law: Adding manpower to a late software project makes it later\text{Adding manpower to a late software project makes it later}
    • Extra coordination overhead outweighs added labor.

Recap / Bottom Line

  • Every successful information system must:
    • Support business requirements
    • Stay within budget
    • Be delivered on schedule
  • Effective project management employs classic management skills: planning, organising, leading & controlling.

Next Session Preview

  • Systems Development Life Cycle (SDLC) will be covered next, building on the roles & project-management foundations outlined above.