System Analyst and Project Manager

A systems analyst acts as a consultant to a business, specifically hired to address information systems issues.

They draw on professional expertise concerning computer hardware and software and serve as a resource rather than directly managing the project.

They help organisations transform by focusing on effectiveness, improvement, and development, acting as a catalyst for change.

Systems thinking, organisation knowledge, problem identification, and problem analysis & solution.

Resource management, change management, risk management, and project management.

Constant re-education to keep skills up-to-date and understanding a wide variety of technologies.

Communication, ability to work alone or with a team, managing user/manager expectations, and facilitating groups.

Threat to job security, reduction in social satisfaction, and reduction of self-esteem and reputation.

Withholding facts, providing inaccurate data, showing indifference, or spreading negativity through commotions or a combative attitude.

Keep people informed, transfer employees if necessary, extend training, and seek employee participation.

Completion on time, within budget, meeting requirements, and satisfying users.

Project planning, scheduling, monitoring and controlling, and reporting.

Identifying all project tasks and estimating their completion time and cost.

Creating a timetable showing tasks, dependencies, critical tasks, and assigning resources appropriately.

Guiding, supervising, and coordinating the team’s workload to meet quality standards.

A review of a project team member’s work by other team members.

Creating regular progress reports for management, users, and the project team.

Regular updates are given to discuss project status, issues, problems, and opportunities.

Written progress reports often including Gantt charts to show project status graphically.

Ensuring the system provides a solution to a business problem or opportunity.

Projects gradually expanding beyond their initial scope.

Cost overruns from unrealistic estimates, poor forecasts, or slow responses to warning signs.

Problems with timetables and milestones due to poor monitoring, missed dependencies, confusion, or personnel turnover.

"Adding manpower to a late software project makes it later."