IS Strategy & MGMT Note - 2
IS Strategy & MGMT Note - 2
IS Strategy & MGMT Note - 2
An IT architecture - is a blueprint.
An IT infrastructure is the implementation of an architecture.
Includes the software, databases, electronic links, and data centres etc.
Managing Essential technologies
1. Managing Distributed Systems
Distributed Systems - Is a collection of independent computers that appear to the users of the
system as a single system. Components located at networked computers communicate and
coordinate their actions only by passing messages.
Today, managing operations is just as likely to mean managing outward; that is, managing
the company’s relationships with IT service providers who have taken over the day-to-day
operational work.
What is Project?
Google Defn: A project is defined as a specific, finite activity that produces an
observable and measurable result under certain present requirements. A Project is a
temporary, unique and progressive attempt or endeavour made to produce some kind of a
tangible or intangible result (a unique product, service, benefit, competitive advantage, etc.).
IS Strategy and Management Note Book -2-
It usually includes a series of interrelated tasks that are planned for execution over a fixed
period of time and within certain requirements and limitations such as cost, quality,
performance, others.
Lemmas Defn: A project is a temporary endeavour undertaken to accomplish a unique
product or service.
IT/IS projects refers to projects involving hardware, software, and networks. Creating new
system or upgrading existing one.
Examples of IT/IS projects: Examples of an IT project include web development, SW
development, mobile app development, network configuration, SW implementation, HW
installation, DB management, and IT emergency recovery.
RA1: Leading an information systems development project is a challenging task.
Agree/Disagree?
Agree: There are five key management challenges in building and using information
systems:
1. Designing systems that are competitive and efficient;
2. Understanding the system requirements of a global business environment;
3. Creating an information architecture that supports the organization's goals;
4. Determining the business value of information systems; and
5. Designing systems that people can control, understand, and use in a socially and
ethically responsible manner.
Why do information system development projects fail?
According to the analysis, the top five factors causing failure are
Underestimated timeline
Weak definitions of requirements and scope
Inadequate project risk analysis
Incorrect assumptions regarding risk analysis and
Ambiguous business needs and unclear vision' (Yeo, 2002: 245).
RA2: Define IS/IT project success
Traditional definition of IT project success is ‘the project met scope, time, and cost goals.
Nowadays IT project success is all about value centric rather than product centric.
IS Strategy and Management Note Book -2-
It is a process that helps in determining and documenting the list of all the
project goals, tasks, deliverables, deadlines, and budgets as a part of the
planning process. (Google)
Managing the project scope is primarily concerned with defining and controlling
what is and is not included in the project.
2. Project time management
Includes the processes required to manage the timely completion of the project.
Involves analysing and developing a schedule and timeline for project
completion. (Google)
Refers to a component of overall project management in which a timeline is analysed
and developed for the completion of a project or deliverable. (Google)
3. Project cost management
Includes the processes involved in planning, estimating, budgeting, financing,
funding, managing, and controlling costs so that the project can be completed within
the approved budget.
It is the process of planning, estimating, budgeting, and controlling project
costs.(Google)
4. Project quality management
Includes the processes and activities of the performing organization that determine
quality policies, objectives, and responsibilities so that the project will satisfy the
needs for which it was undertaken
Includes creating and following policies and procedures in order to ensure that a
project meets the defined needs it was intended to meet from the customer’s
perspective. (Google)
It is the process through which quality is managed and maintained throughout a
project. It is ensuring quality consistency throughout a project. (Google)
5. Project HR Management
Concerned with organizing, managing, and leading a project team.
Making the most effective use of the people involved with a project.
IS Strategy and Management Note Book -2-
- This principle serves as a general reminder that the relationship between inputs and
outputs is not balanced. The Pareto Principle is also known as the Pareto Rule or the
80/20 Rule.
- In business, a goal of the 80-20 rule is to identify inputs that are potentially the most
productive and make them the priority. For instance, once managers identify factors
that are critical to their company's success, they should give those factors the most
focus.
- The 80-20 rule maintains that 80% of outcomes (outputs) come from 20% of causes
(inputs).
- In the 80-20 rule, you prioritize the 20% of factors that will produce the best results.
- A principle of the 80-20 rule is to identify an entity's best assets and use them
efficiently to create maximum value.
Ex: 20 percent of software bugs cause 80 percent of the software’s failures.
20 percent of employees produce 80 percent of a company’s results.
o Software can certainly be changed, but often changes after release can require
an enormous amount of labour.
3. Developer Myths – their myths: You can't assess software quality until the program is
running.
There are static ways to evaluate quality without running a program.
Software reviews can effectively determine the quality of requirements
documents, design documents, test plans, and code.
Solutions for SW Management Myths
A. Development problems can be solved by developing and documenting standards.
Standards have been developed by companies and standards organizations. They
can be very useful. However, they are frequently ignored by developers because
they are incomplete, and sometimes incomprehensible.
B. Development problems can be solved by using state-of-the art tools.
Tools may help, but there is no magic. Problem solving requires more than tools,
it requires great understanding. There is no silver bullet to eliminate the software
development problems.
Solution for SW Customer Myths
A. A general statement of need is sufficient to start coding
For developers to have a chance to satisfy the customers’ requirements, they need
detailed descriptions of these requirements. Developers cannot read the minds of
customers.
Solution for SW developer myths: their myth - The job is done when the code is delivered.
A. Commercially successful software may be used for decades. Thus:
Developers must continually maintain such software: They have to add features
and repair bugs.
Maintenance costs predominate over all other costs; maintenance may be 70% of
the development costs.
Their other myth: Project success depends solely on the quality of the delivered program.
However:
Documentation and software configuration information is very important to the quality.
After functionality, maintainability is of critical importance.
Developers must maintain the software and they need good design documents, test data,
etc. to do their job.