3.10+IT+systems+in+organizations

=**Introduction**= This topic builds on the concepts introduced in “Introduction to project management” and provides students with a more in-depth understanding of the development of IT systems. Most organizations, at some stage in their development, require the introduction of a new IT system as well as the maintenance and eventual retirement of their current systems. The ability of the organization to manage this change can determine the future viability of the organization. Students should consider the interrelationship between stakeholders, IT systems, data, processes and policies, which provides the framework for the different project management approaches needed in order to accomplish the specified task. For example, students should research real examples of the role of IT professionals who maintain legacy or develop new IT systems, to reinforce the theoretical concepts addressed in this topic.

=**IT concepts to address in this topic**=

=Information systems, people and teams=

Link to Information Systems Google Doc
• The role and need for IT in organizations • Organizational IT policies • IT personnel and organizational structure: for example, information system (IS) managers, support staff, network manager, database administrator • Development personnel: for example, manager, programmer, analyst, project manager

=The system development life cycle (SDLC)=

Link to SDLC Google Doc
• Analysis of current situation • Organizational requirements • Methods of data collection: questionnaires, interviews, observation, literature searches • Feasibility study • Identification of possible IT solutions • Requirements specification • Justification of preferred IT solution • Project plan (who, why, what, when and how part of the project) • Project goals, scope and constraints, such as financial, time, technical, human-resource-related, risks, communication, procurement, quality • Project initiation document • Design considerations • Inputs, data structure, processes, outputs, user interface • Prototyping • Development of the IT solution • Initial testing, alpha testing • Quality assurance and quality control • Implementation • Training and support of staff, documentation to support the new IT system • Changeover methods: direct, phased and parallel running • Beta testing • Maintenance • Phase out

=Project management issues=

Link to Project Management Issues Google Doc
• Need for project management • Development methodologies: agile development and waterfall development • Project management methodologies: for example, PRINCE2 (projects in controlled environments 2), SSADM (structured systems analysis and design method), PMBoK (project management body of knowledge), CMMI (capability maturity model integration) • Iteration • Time constraints, tasks, resources and milestones; Gantt and Pert charts • Modelling systems: for example, entities, entity relationship diagrams (ERD), data flow diagrams • Maintenance of legacy systems • System support: for example, internal support, maintenance contract • Incident management and escalation

rss url="http://www.diigo.com/rss/user/Mjb000/3.10_IT_sys_organizations" link="true" number="10"