MIS 2 - Assignment 6

Critical Success Factor

This assignment is for me to identify and discuss the steps for critical success factors. According to Wikipedia and other sources, the following sre the definition of CSF.

Critical Success Factor (CSF) is the term for an element that is necessary for an organization or project to achieve its mission. It is a critical factor or activity required for ensuring the success of your business. The term was initially used in the world of data analysis, and business analysis. For example, a CSF for a successful Information Technology (IT) project is user involvement.
http://en.wikipedia.org/wiki/Critical_success_factor

Critical Success Factors have been used significantly to present or identify a few key factors that organizations should focus on to be successful.
As a definition, critical success factors refer to "the limited number of areas in which satisfactory results will ensure successful competitive performance for the individual, department, or organization”.
http://rapidbi.com/created/criticalsuccessfactors.html#WhatareCSFs

The idea of identifying critical success factors as a basis for determining the information needs of managers was proposed by Daniel (1961) but popularized by Rockart (1979). The idea is very simple: in any organization certain factors will be critical to the success of that organization, in the sense that, if objectives associated with the factors are not achieved, the organization will fail - perhaps catastrophically so. Rockart (1979: 85), by referring to Daniel (1961), gives the following as an example of the CSFs: new product development, good distribution, and effective advertising for the food processing industry - factors that remain relevant today for many firms. The CSFs approach was applied in case studies carried out in the UK universities. It was applied also as a component of a strategic information management (SIM) methodology put forward by Wilson (1992, 1994b). The CSFs approach was combined with the value chain concept by Porter (1985) in order to form an information audit. The methodology was tested in two case studies carried out in very knowledge-intensive sectors of Finnish industry. The process was funded by the Academy of Finland.
http://informationr.net/ir/6-3/paper108.html

Types of Critical Success Factor

There are four basic types of CSF's
They are:
1. Industry CSF's resulting from specific industry characteristics;
2. Strategy CSF's resulting from the chosen competitive strategy of the business;
3. Environmental CSF's resulting from economic or technological changes; and
4. Temporal CSF's resulting from internal organizational needs and changes.

Things that are measured get done more often than things that are not measured.
Each CSF should be measurable and associated with a target goal. You don't need exact measures to manage. Primary measures that should be listed include critical success levels (such as number of transactions per month) or, in cases where specific measurements are more difficult, general goals should be specified (such as moving up in an industry customer service survey).

Definitions

Critical Success Factor
an element of organizational activity which is central to its future success. Critical success factors may change over time, and may include items such as product quality, employee attitudes, manufacturing flexibility, and brand awareness. This can enable analysis.

Critical Success Factor
any of the aspects of a business that are identified as vital for successful targets to be reached and maintained. Critical success factors are normally identified in such areas as production processes, employee and organization skills, functions, techniques, and technologies. The identification and strengthening of such factors may be similar. ..

Critical Success Factor (CSF) or Critical Success Factors
is a business term for an element which is necessary for an organization or project to achieve its mission. For example, a CSF for a successful Information Technology (IT) project is user involvement.
Using the term
The term “Critical Success Factor” is used differently, due to ambiguity of the word “critical”,
back and forth translations into other languages and interpretation when analyzed in portfolios:
1. Definition 1: “critical” = important, key, determining, vital, strategic, etc.
2. Definition 2: “critical” = alarming, anxious, etc. (as shown within the diagram = top left):
Which ever definition you use. make sure that all managers understand the definition.

Five key sources of Critical Success Factors
MAIN ASPECTS OF Critical Success Factors and their use in analysis
CSF's are tailored to a firm's or manager's particular situation as different situations (e.g. industry, division, individual) lead to different critical success factors. Rockart and Bullen presented five key sources of CSF's:

1. The industry,
2. Competitive strategy and industry position,
3. Environmental factors,
4. Temporal factors, and
5. Managerial position (if considered from an individual's point of view). Each of these factors is explained in greater detail below.

In reality, identifying your CSFs is a very iterative process. Your mission, strategic goals and CSFs are intrinsically linked and each will be refined as you develop them.

Here are the summary steps that, used iteratively, will help you identify the CSFs for your business or project:

Step One: Establish your business's or project's mission and strategic goals.
Step Two: For each strategic goal, ask yourself "what area of business or project activity is essential to achieve this goal?" The answers to the question are your candidate CSFs.
Step Three: Evaluate the list of candidate CSFs to find the absolute essential elements for achieving success - these are your Criticial Success Factors.

As you identify and evaluate candidate CSFs, you may uncover some new strategic objectives or more detailed objectives. So you may need to define your mission, objectives and CSFs iteratively.

Step Four: Identify how you will monitor and measure each of the CSFs.

Step Five: Communicate your CSFs along with the other important elements of your business or project's strategy.

Step Six: Keep monitoring and reevaluating your CSFs to ensure you keep moving towards your aims. Indeed, whilst CSFs are sometimes less tangible than measurable goals, it is useful to identify as specifically as possible how you can measure or monitor each one.

Key Points
Critical Success Factors are the areas of your business or project that are absolutely essential to its success. By identifying and communicating these CSFs, you can help ensure your business or project is well-focused and avoid wasting effort and resources on less important areas. By making CSFs explicit, and communicating them with everyone involved, you can help keep the business and project on track towards common aims and goals.

Tip: How Many CSFs?
To make sure you consider all types of possible CSFs, you can use Rockart's CSF types as a checklist.
• Industry - these factors result from specific industry characteristics. These are the things that the organization must do to remain competitive.
• Environmental - these factors result from macro-environmental influences on an organization. Things like the business climate, the economy, competitors, and technological advancements are included in this category.
• Strategic - these factors result from the specific competitive strategy chosen by the organization. The way in which the company chooses to position themselves, market themselves, whether they are high volume low cost or low volume high cost producers, etc.
• Temporal - these factors result from the organization's internal forces. Specific barriers, challenges, directions, and influences will determine these CSFs.
http://rapidbi.com/created/criticalsuccessfactors.html

With the steps discussed above critical success factor are probably essential for every organization. The steps in CFS allow an organization to plan of how to attain success without any problems.

MIS 2 - Assignment 5

Organizational Change

Change is an absolutely critical part of business. And yes, your company does need to change—preferably now and not later, when you have no other choice.
The problem is that people hate it when their bosses announce a “transformation initiative.” They run back to their cubicles and start frantically e-mailing one another, complaining that the changes are going to ruin everything
People love familiarity and patterns. They cling to them. The phenomenon is so entrenched it can only be chalked up to human nature. But while managing change can sometimes feel like moving a mountain, it can also be incredibly rewarding, particularly when you start seeing results.

Ultimately, implementing change comes down to embracing the following four practices:
1. Attach every change initiative to a clear purpose or goal. Change for change’s sake is stupid and enervating. Change should be a relatively orderly process, but for that to occur, people have to understand why change is necessary and how changes will affect them. This is easier, of course, when the problems are obvious—earnings are collapsing or a competitor has dropped prices 20 percent.
But sometimes the need for change isn’t immediately apparent. Competitive threats seem to be emerging, but you don’t know for certain, and still, you have to respond. In those cases, relentless communication about the business rationale for change, reinforced with lots of data, is the best ammunition you have.
The larger your company, the more challenging it will be to communicate the need for change. In big companies, calls for change are often greeted noncommittally. After all, if the company has been through enough change programs, employees will assume you’ll go away if they just wait long enough.
Stick to your guns—your solid, persuasive business case. Over time, logic will win out.

2. Hire and promote only true believers and get-on-with-it types. Everyone in business claims to like change. To say otherwise would be career suicide. But by my estimate, less than 10 percent of all businesspeople are true change agents. Once the next group—about 70 to 80 percent of people working in business—is convinced that change is necessary, they’ll say, “OK already, get on with it.” The rest are resisters.
To make change happen, companies must actively hire and promote only true believers and get-on-with-its. But with everyone claiming to like change, how can you tell who is for real?
Luckily, change agents usually make themselves known. They’re typically brash, high-energy and more than a little paranoid about the future. They often invent change initiatives on their own or ask to lead them. Invariably, they are curious and forward-looking.
These people have a certain fearlessness about the unknown. If they fail, they know they can pick themselves up, dust themselves off and move on. They’re thick-skinned about risk, which allows them to make bold decisions without a lot of data.

3. Ferret out and remove the resisters, even if their performance is satisfactory. This is the hardest of the four practices to implement. It’s tough to let anyone go, but it’s particularly difficult to fire people who are not actually screwing up and may in fact be doing quite well.
But in any organization, there are people who will not accept change, no matter how sound your case is. They are so invested—emotionally, intellectually, or politically—in the status quo that they cannot see a way to improve anything. These people usually have to go.
That may sound harsh, but you’re not doing anyone a favor by keeping resisters in your organization. They foster an underground resistance and lower the morale of the people who support change. They’re wasting their own time: They’re working at a company where they don’t agree with or share in the vision, and they should be encouraged to find one where they do.

4. Look at car wrecks. Most companies capitalize on obvious opportunities. When a competitor fails, they move in on their customers. When a new technology emerges, they invest in it and create product line extensions.
But to be a real change organization, you also have to have to look at bolder, scarier, more unpredictable events, assess the opportunities they present and make the most of them. Fostering this capability takes a certain determination, but the rewards can be huge.
Take the 1997 Asian financial crisis. Currency traders certainly capitalized on this awful event; they live on exploiting change. But they’re not the only ones who should do this. GE had real success buying undervalued Thai auto loans in this period. Others prospered by buying real estate at fire sale prices.
Bankruptcies are another type of calamity that reveals all kinds of opportunities. Of course, they’re tragic to the employees. Jobs are lost, and pensions disappear into thin air. But jobs and futures can also be created from the cinders.
With all the noise out there about change, it’s easy to get overwhelmed and confused. But these are the only four practices that matter. That’s it. There’s nothing to be afraid of.
Jack and Suzy Welch are the authors of the international bestseller Winning (Collins). Their latest book is Winning: The Answers: Confronting 74 of the Toughest Questions in Business Today (Collins). They are eager to hear about your career dilemmas and challenges at work and look forward to answering your questions in future columns. Please visit their new web site at www.welchway.com and submit questions through the online form at welchway.com/Contact-Us.aspx. Please include your name, occupation, city and country.
http://www.businessmirror.com.ph/home/pf/17334-principles-of-organizational-change.html

To really understand organizational change and begin guiding successful change efforts, the change agent should have at least a broad understanding of the context of the change effort. This includes understanding the basic systems and structures in organizations, including their typical terms and roles. This requirement applies to the understanding of leadership and management of the organizations, as well. That is why graduate courses in business often initially include a course or some discussion on organizational theory. This topic includes several links to help you gain this broad understanding. The following links (broadly reviewed in the following order) might be helpful to establish some sense about organizations, and their leadership and management.
http://managementhelp.org/org_chng/org_chng.htm

Major Types of Organizational Change
Typically, the phrase “organizational change” is about a significant change in the organization, such as reorganization or adding a major new product or service. This is in contrast to smaller changes, such as adopting a new computer procedure. Organizational change can seem like such a vague phenomena that it is helpful if you can think of change in terms of various dimensions as described below.

Organization-wide Versus Subsystem Change
Examples of organization-wide change might be a major restructuring, collaboration or “rightsizing.”
Usually, organizations must undertake organization-wide change to evolve to a different level in their life cycle, for example, going from a highly reactive, entrepreneurial organization to one that has a more stable and planned development. Experts assert that successful organizational change requires a change in culture – cultural change is another example of organization-wide change.
Examples of a change in a subsystem might include addition or removal of a product or service, reorganization of a certain department, or implementation of a new process to deliver products or services.

Transformational Versus Incremental Change
An example of transformational (or radical, fundamental) change might be changing an organization’s structure and culture from the traditional top-down, hierarchical structure to a large amount of self-directing teams. Another example might be Business Process Re-engineering, which tries to take apart (at least on paper, at first) the major parts and processes of the organization and then put them back together in a more optimal fashion. Transformational change is sometimes referred to as quantum change.
Examples of incremental change might include continuous improvement as a quality management process or implementation of new computer system to increase efficiencies. Many times, organizations experience incremental change and its leaders do not recognize the change as such.

Remedial Versus Developmental Change
Change can be intended to remedy current situations, for example, to improve the poor performance of a product or the entire organization, reduce burnout in the workplace, help the organization to become much more proactive and less reactive, or address large budget deficits. Remedial projects often seem more focused and urgent because they are addressing a current, major problem. It is often easier to determine the success of these projects because the problem is solved or not.
Change can also be developmental – to make a successful situation even more successful, for example, expand the amount of customers served, or duplicate successful products or services.
Developmental projects can seem more general and vague than remedial, depending on how specific goals are and how important it is for members of the organization to achieve those goals.
Some people might have different perceptions of what is a remedial change versus a developmental change. They might see that if developmental changes are not made soon, there will be need for remedial changes. Also, organizations may recognize current remedial issues and then establish a
Adapted from “Field Guide to Consulting and Organizational Development” – to obtain the entire book, select “Publications” at http://www.authenticityconsulting.com
Copyright; Authenticity Consulting, LLC 175 developmental vision to address the issues. In those situations, projects are still remedial because they were conducted primarily to address current issues.

Unplanned Versus Planned Change
Unplanned change usually occurs because of a major, sudden surprise to the organization, which causes its members to respond in a highly reactive and disorganized fashion. Unplanned change might occur when the Chief Executive Officer suddenly leaves the organization, significant public relations problems occur, poor product performance quickly results in loss of customers, or other disruptive situations arise.
Planned change occurs when leaders in the organization recognize the need for a major change and proactively organize a plan to accomplish the change. Planned change occurs with successful implementation of a Strategic Plan, plan for reorganization, or other implementation of a change of this magnitude.
Note that planned change, even though based on a proactive and well-done plan, often does not occur in a highly organized fashion. Instead, planned change tends to occur in more of a chaotic and disruptive fashion than expected by participants.

The levels of organizational change
Perhaps the most difficult decision to make is at what "level" to start. There are four levels of organizational change:
shaping and anticipating the future (level 1)
defining what business(es) to be in and their "core competencies” (level 2)
reengineering processes (level 3)
incrementally improving processes (level 4)

First let's describe these levels, and then under what circumstances a business should use them.
Level 1- shaping and anticipating the future
At this level, organizations start out with few assumptions about the business itself, what it is "good" at, and what the future will be like.
Management generates alternate "scenarios" of the future, defines opportunities based on these possible futures, assesses its strengths and weaknesses in these scenarios changes its mission, measurement system etc. More information on this is in the next article, "Moving from the Future to your Strategy."
Level 2 - defining what business(es) to be in and their "Core Competencies
Many attempts at strategic planning start at this level, either assuming that 1) the future will be like the past or at least predictable; 2) the future is embodied in the CEO's "vision for the future"; or 3) management doesn't know where else to start; 4) management is too afraid to start at level 1 because of the changes needed to really meet future requirements; or 5) the only mandate they have is to refine what mission already exists.
After a mission has been defined and a SWOT (strengths, weaknesses, opportunities and threats) analysis is completed, an organization can then define its measures, goals, strategies, etc. More information on this is in the next article, "Moving from the Future to your Strategy."
Level 3 - Reengineering (Structurally Changing) Your Processes
Either as an aftermath or consequence of level one or two work or as an independent action, level three work focuses on fundamentally changing how work is accomplished. Rather than focus on modest improvements, reengineering focuses on making major structural changes to everyday with the goal of substantially improving productivity, efficiency, quality or customer satisfaction. To read more about level 3 organizational changes, please see "A Tale of Three Villages."
Level 4 - Incrementally Changing your Processes
Level 4 organizational changes are focusing in making many small changes to existing work processes. Oftentimes organizations put in considerable effort into getting every employee focused on making these small changes, often with considerable effect. Unfortunately, making improvements on how a buggy whip for horse-drawn carriages is made will rarely come up with the idea that buggy whips are no longer necessary because cars have been invented. To read more about level 4 organizational changes and how it compares to level 3, please see "A Tale of Three Villages."

One organization we consulted with has had a more positive experience with the incremental approach. We trained an internal facilitator, helped them deliver training in a just-in-time fashion, and had them focus on specific technical problems. The teams management formed reduced initial quality defects by 48%.
The disadvantages of such an incremental approach include avoiding structural, system-wide problems, and assumes existing processes need modest improvement. In addition, using incremental approaches can be frustrating to employees and management if (pick a buzzword) does not catch on in the organization. As a result of these disadvantages, many organizations experience a high risk of failure in the long run.
http://www.organizedchange.com/decide.htm

Business process reengineering (BPR) is, in computer science and management, an approach aiming at improvements by means of elevating efficiency and effectiveness of the business process that exist within and across organizations. The key to BPR is for organizations to look at their business processes from a "clean slate" perspective and determine how they can best construct these processes to improve how they conduct business.
Business process reengineering is also known as BPR, Business Process Redesign, Business Transformation, or Business Process Change Management. Reengineering is a fundamental rethinking and radical redesign of business processes to achieve dramatic improvements in cost, quality, speed, and service. BPR combines a strategy of promoting business innovation with a strategy of making major improvements to business processes so that a company can become a much stronger and more successful competitor in the marketplace.
The main proponents of reengineering were Michael Hammer and James A. Champy. In a series of books including Reengineering the Corporation, Reengineering Management, and The Agenda, they argue that far too much time is wasted passing-on tasks from one department to another. They claim that it is far more efficient to appoint a team who are responsible for all the tasks in the process. In The Agenda they extend the argument to include suppliers, distributors, and other business partners.
Re-engineering is the basis for many recent developments in management. The cross-functional team, for example, has become popular because of the desire to re-engineer separate functional tasks into complete cross-functional processes. Also, many recent management information systems developments aim to integrate a wide number of business functions. Enterprise resource planning, supply chain management, knowledge management systems, groupware and collaborative systems, Human Resource Management Systems and customer relationship management systems all owe a debt to re-engineering theory.
http://en.wikipedia.org/wiki/Business_process_reengineering

Business process reengineering (often referred to by the acronym BPR) is the main way in which organizations become more efficient and modernize. Business process reengineering transforms an organization in ways that directly affect performance.

The impact of BPR on organizational performance
The two cornerstones of any organization are the people and the processes. If individuals are motivated and working hard, yet the business processes are cumbersome and non-essential activities remain, organizational performance will be poor. Business Process Reengineering is the key to transforming how people work. What appear to be minor changes in processes can have dramatic effects on cash flow, service delivery and customer satisfaction. Even the act of documenting business processes alone will typically improve organizational efficiency by 10%.

How to implement a BPR project
The best way to map and improve the organization's procedures is to take a top down approach, and not undertake a project in isolation. That means:
• Starting with mission statements that define the purpose of the organization and describe what sets it apart from others in its sector or industry.
• Producing vision statements which define where the organization is going, to provide a clear picture of the desired future position.
• Build these into a clear business strategy thereby deriving the project objectives.
• Defining behaviours that will enable the organization to achieve its' aims.
• Producing key performance measures to track progress.
• Relating efficiency improvements to the culture of the organization
• Identifying initiatives that will improve performance.
Once these building blocks in place, the BPR exercise can begin.

Tools to support BPR
When a BPR project is undertaken across the organization, it can require managing a massive amount of information about the processes, data and systems. If you don't have an excellent tool to support BPR, the management of this information can become an impossible task. The use of a good BPR/documentation tool is vital in any BPR project.

The types of attributes you should look for in BPR software are:
• Graphical interface for fast documentation
• "Object oriented" technology, so that changes to data (eg: job titles) only need to be made in one place, and the change automatically appears throughout all the organization's procedures and documentation.
• Drag and drop facility so you can easily relate organizational and data objects to each step in the process
• Customizable meta data fields, so that you can include information relating to your industry, business sector or organization in your documentation
• Analysis, such as swim-lanes to show visually how responsibilities in a process are transferred between different roles, or where data items or computer applications are used.
• Support for Value Stream mapping.
• CRUD or RACI reports, to provide evidence for process improvement.
• The ability to assess the processes against agreed international standards
• Simulation software to support 'what-if' analyses during the design phase of the project to develop LEAN processes
• The production of word documents or web site versions of the procedures at the touch of a single button, so that the information can be easily maintained and updated.
The software we use by choice is Protos, a very comprehensive Dutch system that has been translated into English. Protos meets all the above requirements, and many more, and is better than any system originated in English that we have seen.
Conclusion
To be successful, business process reengineering projects need to be top down, taking in the complete organization, and the full end to end processes. It needs to be supported by tools that make processes easy to track and analyze.
http://www.teamtechnology.co.uk/business-process-reengineering.html

SAD 1 - Assignment 1

A good Systems Analyst

A systems analyst is responsible for researching, planning, coordinating and recommending software and system choices to meet an organization's business requirements. The systems analyst plays a vital role in the systems development process. A successful systems analyst must acquire four skills: analytical, technical, managerial, and interpersonal. Analytical skills enable systems analysts to understand the organization and its functions, which helps him/her to identify opportunities and to analyze and solve problems. Technical skills help systems analysts understand the potential and the limitations of information technology. The systems analyst must be able to work with various programming languages, operating systems, and computer hardware platforms. Management skills help systems analysts manage projects, resources, risk, and change. Interpersonal skills help systems analysts work with end users as well as with analysts, programmers, and other systems professionals.

Because they must write user requests into technical specifications, the systems analysts are the liaisons between vendors and the IT professionals of the organization they represent. They may be responsible for developing cost analysis, design considerations, and implementation time-lines. They may also be responsible for feasibility studies of a computer systems before making recommendations to senior management.

A systems analyst performs the following tasks:

* Interact with the customers to know their requirements
* Interact with designers to convey the possible interface of the software
* Interact/guide the coders/developers to keep track of system development
* Perform system testing with sample/live data with the help of testers
* Implement the new system
* Prepare High quality Documentation

Many systems analysts have morphed into business analysts. And, the Bureau of Labor Statistics reports that "Increasingly, employers are seeking individuals who have a master’s degree in business administration (MBA) with a concentration in information systems."
http://en.wikipedia.org/wiki/Systems_analyst

Nature of Computer Systems Analyst Work

All organizations rely on computer and information technology to conduct business and operate efficiently. Computer systems analysts help organizations to use technology effectively and to incorporate rapidly changing technologies into their existing systems. The work of computer systems analysts evolves rapidly, reflecting new areas of specialization and changes in technology.

Computer systems analysts solve computer problems and use computer technology to meet the needs of an organization. They may design and develop new computer systems by choosing and configuring hardware and software. They may also devise ways to apply existing systems’ resources to additional tasks. Most systems analysts work with specific types of computer systems—for example, business, accounting, or financial systems or scientific and engineering systems—that vary with the kind of organization. Analysts who specialize in helping an organization select the proper system software and infrastructure are often called system architects. Analysts who specialize in developing and fine-tuning systems often are known as systems designers.

To begin an assignment, systems analysts consult managers and users to define the goals of the system. Analysts then design a system to meet those goals. They specify the inputs that the system will access, decide how the inputs will be processed, and format the output to meet users’ needs. Analysts use techniques such as structured analysis, data modeling, information engineering, mathematical model building, sampling, and cost accounting to make sure their plans are efficient and complete. They also may prepare cost-benefit and return-on-investment analyses to help management decide whether implementing the proposed technology would be financially feasible.

When a system is approved, systems analysts determine what computer hardware and software will be needed to set it up. They coordinate tests and observe the initial use of the system to ensure that it performs as planned. They prepare specifications, flow charts, and process diagrams for computer programmers to follow; then they work with programmers to debug, or eliminate errors, from the system. Systems analysts who do more in-depth testing may be called software quality assurance analysts. In addition to running tests, these workers diagnose problems, recommend solutions, and determine whether program requirements have been met.

In some organizations, programmer-analysts design and update the software that runs a computer. They also create custom applications tailored to their organization’s tasks. Because they are responsible for both programming and systems analysis, these workers must be proficient in both areas. As this dual proficiency becomes more common, analysts are increasingly working with databases, object-oriented programming languages, clientserver applications, and multimedia and Internet technology.

One challenge created by expanding computer use is the need for different computer systems to communicate with each other. Systems analysts work to make the computer systems within an organization, or across organizations, compatible so that information can be shared. Many systems analysts are involved with these networking tasks, connecting all the computers internally, in an individual office, department, or establishment, or externally, as when setting up e-commerce networks to facilitate business among companies.

Work environment. Computer systems analysts work in offices or laboratories in comfortable surroundings. They usually work about 40 hours a week—about the same as many other professional or office workers. Evening or weekend work may be necessary, however, to meet deadlines or solve specific problems. Many analysts telecommute, using computers to work from remote locations.

Like other workers who spend long periods typing on a computer, computer systems analysts are susceptible to eyestrain, back discomfort, and hand and wrist problems such as carpal tunnel syndrome or cumulative trauma disorder.
http://www.searchbydegree.com/computer-systems-analyst-career.html

These skill I got from the reporters of the first chapter in SAD 1.

A successful systems analyst must acquire four skills:

1. Analytical skills is the ability to visualize, articulate, and solve complex problems and concepts, and make decisions that make sense based on available information. Such skills include demonstration of the ability to apply logical thinking to gathering and analyzing information, designing and testing solutions to problems, and formulating plans.

To test for analytical skills one might be asked to look for inconsistencies in an advertisement, put a series of events in the proper order, or critically read an essay. Usually standardized tests and interviews include an analytical section that requires the examine to use their logic to pick apart a problem and come up with a solution.

Although there is no question that analytical skills are essential, other skills are equally required as well. For instance in systems analysis the systems analyst should focus on four sets of analytical skills: systems thinking, organizational knowledge, problem identification, and problem analyzing and solving.

It also includes the way we describe a problem and subsequently finding out the solutions.

Analytical skills enable systems analysts to understand the organization and its functions, which helps him/her to identify opportunities and to analyze and solve problems.

2. Technical skills help systems analysts understand the potential and the limitations of information technology. The systems analyst must be able to work with various programming languages, operating systems, and computer hardware platforms.

3. Management skills in all business and human organisation activity is simply the act of getting people together to accomplish desired goals and objectives. Management comprises planning, organizing, staffing, leading or directing, and controlling an organization (a group of one or more people or entities) or effort for the purpose of accomplishing a goal. Resourcing encompasses the deployment and manipulation of human resources, financial resources, technological resources, and natural resources.

Management can also refer to the person or people who perform the act(s) of management.

Management skills help systems analysts manage projects, resources, risk, and change.

4. Interpersonal skills refers to mental and communicative algorithms applied during social communications and interaction to reach certain effects or results. The term "interpersonal skills" is used often in business contexts to refer to the measure of a person's ability to operate within business organizations through social communication and interactions. Interpersonal skills are how people relate to one another.

As an illustration, it is generally understood that communicating respect for other people or professionals within will enable one to reduce conflict and increase participation or assistance in obtaining information or completing tasks.

Interpersonal skills help systems analysts work with end users as well as with analysts, programmers, and other systems professionals.

System Analyst is the person who is responsible for the development of an information system. Systems analysts design and modify systems by turning user requirements into a set of functional specifications, which are the blueprint of the system. They design the database or help design it if data administrators are available. They develop the manual and machine procedures and the detailed processing specifications for each data entry, update, query and report program in the system.

Systems analysts are the architects, as well as the project leaders, of an information system. It is their job to develop solutions to users' problems, determine the technical and operational feasibility of their solutions, as well as estimate the costs to develop and implement them.

They develop prototypes of the system along with the users, so that the final specifications are examples of screens and reports that have been carefully reviewed. Experienced analysts leave no doubt in users' minds as to what is being developed, and they insist that all responsible users review and sign off on every detail.

Systems analysts require a balanced mix of business and technical knowledge, interviewing and analytical skills and a good understanding of human behavior.

1. The system analyst must be able to communicate in writing and orally.
2. The analyst must easily get along with people.
3. The analyst must be a good listener and be able to react to what people say.
4. The analyst must be knowledgeable of technology. The analyst is not expected to know the intricacies of programming, but a decent general knowledge of concepts and terms is essential.
5. The analyst must be knowledgeable of business. The analyst is not expected to be an expert in business but a decent understanding of the client's world is required.
http://answers.yahoo.com/question/index?qid=20080725042042AA2MqMh

From these characteristics of a systems analyst communication skills for me is most important and what I should always practice. I really don not know which among I am good with. Honestly! But for me having the communication skills to be able to interact with clients or coworkers is most important. It would be most desirable if a system analyst is also knowledgeable on the programming side and so as business side because systems analyst serves as the bridge between the programmers and the one in charge of business tasks.

MIS 2 - Assignment 3

Causes of Frustration

What are the two most frequently experienced causes of frustration of IS professionals and users while working on an IS plan? note: you are required to interview an IS professional/s for your answer ...(at least 3000 words)

When we say frustration we mean disappointment. The following is a definition I got from Wikipedia.
Frustration a common emotional response to opposition. Related to anger and disappointment, it arises from the perceived resistance to the fulfillment of individual will. The greater the obstruction, and the greater the will, the more the frustration is likely to be. Causes of frustration may be internal or external. In people, internal frustration may arise from challenges in fulfilling personal goals and desires, instinctual drives and needs, or dealing with perceived deficiencies, such as a lack of confidence or fear of social situations. Conflict can also be an internal source of frustration; when one has competing goals that interfere with one another, it can create cognitive dissonance. External causes of frustration involve conditions outside an individual, such as a blocked road or a difficult task. While coping with frustration, some individuals may engage in passive-aggressive behavior, making it difficult to identify the original cause(s) of their frustration, as the responses are indirect. A more direct, and common response, is a propensity towards aggression.
http://en.wikipedia.org/wiki/Frustration

I just want to share this article on how to deal with frustrations.

The emotion you’re feeling is “Frustration”.

With a capital “F”. Maybe even add in some anger because you’ve been working really hard towards your goal or on a project and it just isn’t working. Or you feel like you’re stuck in a dead-end job and can’t find another one. And you may not even really know why. All you know is that you seem to be stuck and no matter how hard you try, you don’t seem to get anywhere. You’re just spinning your wheels in the mud and all you feel is pure frustration. Sound familiar?
This is the point where a lot of people will just say, “I Quit” and give up. Before you do though, here’s 8 ways you can blast through any frustration:

1. Ask Yourself, “What Is Working in This Situation?”
Even if feels like nothing is working, look closely and you will probably find at least something that is going right. So, that’s good. You’ve found something that’s working. Now, how do you improve it? By asking this question, you’ve taken yourself out of the negative mindset of “it’s hopeless” and are back to focusing on the positive.
There's something that’s working and that will give you a clue of what direction to focus on. You may find that even if your previous issues come up you’ll be able to resolve them in the process of concentrating on your improvements.

2. Keep an Accomplishments Log
Write down everything you accomplish in a log. If you do it in a monthly format you will be able to see all that you have accomplished in just one month. You may be surprised by how much you have done. If you realize there’s not much on the list, it may open your eyes to the fact that you may be procrastinating more than working or that you are using too much of your energy going in too many directions and that you need to focus more. Hopefully, you will have lots of items on your list then you can see that even though it may not feel like it, you are moving forwards. The log will also help to highlight where you were the most effective and where you need to work harder.

3. Focus On What You Want to Happen
Go back to the big picture. What is the desired outcome? Sometimes, we get so wrapped up in one problem and trying to solve it that we forget what we were originally trying to accomplish. Try not to ask yourself, “Why did this happen?” Asking questions like that will keep you rooted in the past. It doesn’t offer a solution to the problem. The important thing is knowing the answer to the following two questions:
- What do you want to happen differently this time?”
- What do you need to do in order to get there?

4. Remove the “Noise” and Simplify
When you’re trying to solve a problem, you can get so wrapped up in trying to find a solution that you add unnecessary clutter, noise, and tasks to a project because you thought they “might” be a solution.
Working on this website, I get bombarded by offer after offer of “easy ways to run your website”, “get more traffic”, “make more money” etc. They’re just noise though and usually a waste of my time even reading them. These people are just trying to make money off of me. They have no interest in whether I succeed or not. When people are frustrated by how slow the hard work process is taking, they get tempted by these “here’s what you’ve been missing” and “I’ll make it easy for you” offers. Usually, it ends up that if you do get tempted by the offers you discover 6 months down the road that if you had just stuck with your first plan and just kept working at it, you’d be a lot further ahead by now. Not to mention richer from not having spent money on the Get Rich Quick schemes. Believe in yourself. Simplify and go back to the basics. Determine what is really necessary and remove everything else. Anything that takes your time and effort that isn’t adding value, should be eliminated.

5. Multiple Solutions
You always have options. You just need to brainstorm and figure them out. Tell yourself you need to come up with 8 possible options to what you’re dealing with. Just knowing that you have lots of options will help to make you feel better. You won’t feel like you are trapped in one negative situation. From your list, figure out the best direction and go for it.

6. Take Action
When you get into serious frustration with a problem, you tend not to want to work on it anymore. It’s hard, it’s frustrating, and you’re not getting anywhere. So, anything to avoid having to be in that situation may be far more attractive. Procrastination may start to set in. If you can keep taking steps forwards, you will probably make it past this temporary hump. As Thomas Edison said, “Many of life's failures are people who did not realize how close they were to success when they gave up” and “Surprises and reverses can serve as an incentive for great accomplishment.”
The other thing that can happen is that you start to spend a lot of time worrying. Worrying is a definite way of energy and does not move you in a forwards direction. Only taking action will. Once you start moving forwards again, you will most likely find that you worried for no reason.

7. Visualize a Positive Outcome to the Situation
A lot of times you can get stuck on focusing on what you don’t want to happen or fearing the absolute worst thing that could happen. The top athletes of the world will imagine themselves competing flawlessly over and over again. There is no room for failure in their minds. This is what you need to focus on as well. See yourself achieving your desired outcome. What will it look like? What will it feel like? What will you say? How will you feel? Take the time to visualize it and really feel it. It will inspire you to keep moving forwards.

8. Stay Positive
Things are usually not as bad as they first appear. Sometimes, things seem much worse simply because we’re tired or mentally drained. Taking a break and remembering to keep your sense of humour can also help. This time of frustration will pass. A positive mind is far more open to solutions and answers than a negative one that thinks it’s just “hopeless” and thinks “what’s the use?” A closed mind will not be able to see the possible solutions when they do come along. Stay positive.
As with any problem, the solution is to figure out what your options are, decide on a plan, focus, and then take action. By using the above 8 steps, you should find that you’re running into fewer problems and feeling less frustration. Instead, you may find that you’re running into opportunities and you know exactly how to take advantage of them.
http://www.life-with-confidence.com/frustration.html

Now what is IS planning?

Strategic Information Systems Planning (SISP) is the process of aligning an organization's business strategy with effective computer-based information systems to achieve critical business objectives. SISP is a top concern of major executives and considerable resources (time and money) are spent in SISP activities. Many SISP initiatives are not successful due to the difficulty of implementing the recommendations. A significant problem is the Specification Gap between the description of the recommended systems and the detail needed for actual system implementation. Existing SISP methods do not provide sufficiently rigorous representations to specify detailed system recommendations. Box structures are proposed as a solution to this problem and a SISP process with embedded box structure methods is presented. We have used this innovative process in two SISP projects with large organizations. Partial results from one of the projects are presented as a case study to illustrate the use of box structures and their benefits
http://www.computer.org/portal/web/csdl/doi/10.1109/HICSS.2000.926735

So what would be the two most frequent causes of frustration for IT professional and user while working on an IS plan. I am not a fully pledge IT professional yet but if I will be asked with this question I would answer change and failure. Well when working on an IS plan or any other plan you should always think of what is the plan for, what should be done and how to develop the plan. Change is the only thing that is constant in this world and so we have to cope with it. As a person develops a plan there are always changes that occur which we do not expect and this causes frustration. Another is failure to follow the plan.

There are six externalities that bring about change. They are regulation, capital markets, competition, technology, globalization and customers. When any of these external contexts changes radically and the company is either unable or unwilling to change, it often results in failure.

Company success is very much like human behavior—a result of nature and nurture. But managers refuse to say that they were blessed from above, and so they take all the credit for themselves. They succeed as long as the environment doesn't’t change. The underlying theory is that many people in business succeed by accident and not by plan.
But, unfortunately, people end up believing what they will succeed forever, and they become resistant to change. They get locked into one paradigm or one way of life.

Not meeting what you have planned for signifies failure and would cause frustration. Well this is what they call plan to fail but I guess it is unpredictable that each plan would work out as it is planned. We should just look forward of what would best go with what we want to happen. As an IT professional one should have great patience to be able to cope up with frustrations.

I guess the main cause of frustration is not meeting the goal of any work done. When working on a plan encountering problems is one main reason for frustration, of course who would want their plan to fail or not work. Another is that when other part of the plan resist to the changes. If ever the user himself resists to have such change for the improvement of his work then the plan would not work because the user itself does not support. Though there are a lot of causes of frustrations, one should have the patience and perseverance to cope up with it and straighten up things to achieve the goal.

MIS 2 - Assignment 2

Business Plan and the IS Plan

To start of with I had first defined what a business plan and IS plan is.

A business plan is a formal statement of a set of business goals, the reasons why they are believed attainable, and the plan for reaching those goals. It may also contain background information about the organization or team attempting to reach those goals.

The business goals may be defined for for-profit or for non-profit organizations. For-profit business plans typically focus on financial goals, such as profit or creation of wealth. Non-profit and government agency business plans tend to focus on organizational mission which is the basis for their governmental status or their non-profit, tax-exempt status, respectively—although non-profits may also focus on optimizing revenue. In non-profit organizations, creative tensions may develop in the effort to balance mission with "margin" (or revenue). Business plans may also target changes in perception and branding by the customer, client, tax-payer, or larger community. A business plan having changes in perception and branding as its primary goals is called a marketing plan.

http://en.wikipedia.org/wiki/Business_plan

Information has emerged as an agent of integration and the enabler of new competitiveness for today’s enterprise in the global marketplace. However, has the paradigm of strategic planning changed sufficiently to support the new role of information systems and technology? We reviewed the literature for commonly used or representative information planning methodologies and found that a new approach is needed. There are six methodologies reviewed in this paper. They all tend to regard planning as a separate stage which does not connect structurally and directly to the information systems development. An integration of planning with development and management through enterprise information resources - which capture and characterize the enterprise – will shorten the response cycle and even allow for economic evaluation of information system investment.

For a long time relationship between information system functions and corporate strategy was not of much interest to Top Management of firms. Information Systems were thought to be synonymous with corporate data processing and treated as some back-room operation in support of day-to-day mundane tasks (Rockart, 1979). In the 80’s and 90’s, however, there has been a growing realization of the need to make information systems of strategic importance to an organization. Consequently, strategic information systems planning (SISP) is a critical issue. In many industry surveys, improved SISP is often mentioned as the most serious challenge facing IS managers (Pavri and Ang, 1995, Beath and Orlikowski, 1994; Martin, 1993; Porter and Miller,

1985).

Planning for information systems, as for any other system, begins with the identification of needs. In order to be effective, development of any type of computer-based system should be a response to need--whether at the transaction processing level or at the more complex information and support systems levels. Such planning for information systems is much like strategic planning in management. Objectives, priorities, and authorization for information systems projects need to be formalized. The systems development plan should identify specific projects slated for the future, priorities for each project and for resources, general procedures, and constraints for each application area. The plan must be specific enough to enable understanding of each application and to know where it stands in the order of development. Also the plan should be flexible so that priorities can be adjusted if necessary. King (King, 1995) in his recent article has argued that a strategic capability architecture - a flexible and continuously improving infrastructure of organizational capabilities – is the primary basis for a company's sustainable competitive advantage. He has emphasized the need for continuously updating and improving the strategic capabilities architecture.

http://viu.eng.rpi.edu/publications/strpaper.pdf

Every year, $300-700 million dollar corporations spend about 5% of their gross income on information systems and their supports. That's from about $15,000,000 to $35,000,000! A significant part of those funds support enterprise databases, a philosophy of database system applications that enable corporations to research the past, control the present, and plan for the future.

Even though an information system costs from $1,000,000 to $10,000,000, and even through most chief information officers (CIOs) can specify exactly how much money is being spent for hardware, software, and staff, CIOs cannot however state with any degree of certainty why one system is being done this year versus next, why it is being done ahead of another, or finally, why it is being done at all.

Many enterprises do not have model-based information systems development environments that allow system designers to see the benefits of rearranging an information systems development schedule. Consequently, the questions that cannot be answered include:

• What effect will there be on the overall schedule if an information system is purchased versus developed?
• At what point does it pay to hire an abnormal quantity of contract staff to advance a schedule?
• What is the long term benefit from 4GL versus 3GL?
• Is it better to generate 3GL than to generate/use a 4GL?
• What are the real costs of distributed software development over centralized development?

If these questions were transformed and applied to any other component of a business (e.g., accounting, manufacturing, distribution and marketing), and remained unanswered, that unit's manager would surely be fired!

We not only need answers to these questions NOW!, we also need them quickly, cost effectively, and in a form that they can be modeled and changed in response to unfolding realities. This paper provides a brief review of a successful 10-step strategy that answers these questions.

Too many half-billion dollar organizations have only a vague notion of the names and interactions of the existing and under development information systems. Whenever they need to know, a meeting is held among the critical few, an inventory is taken, interactions confirmed, and accomplishment schedules are updated.

This ad hoc information systems plan was possible only because all design and development was centralized, the only computer was a main-frame, and the past was acceptable prologue because budgets were ever increasing, schedules always slipping, and information was not yet part of the corporation's critical edge.

Well, today is different, really different! Budgets are decreasing, and slipped schedules are being cited as preventing business alternatives. Confounding the computing environment are different operating systems, DBMSs, development tools, telecommunications (LAN, WAN, Intra-, Inter-, and Extra-net), and distributed hard- and software.

Rather than having centralized, long-range planning and management activities that address these problems, today's business units are using readily available tools to design and build ad hoc stop-gap solutions. These ad hoc systems not only do not interconnect, support common semantics, or provide synchronized views of critical corporate policy, they are soon to form the almost impossible to comprehend confusion of systems and data from which systems order and semantic harmony must spring.

Not only has the computing landscape become profoundly different and more difficult to comprehend, the need for just the right--and correct--information at just the right time is escalating. Late or wrong information is worse than no information.

Information systems managers need a model of their information systems environment. A model that is malleable. As new requirements are discovered, budgets modified, new hardware/software introduced, this model must be such that it can reconstitute the information systems plan in a timely and efficient manner.

http://www.tdan.com/view-articles/5262

Planning is essential for every organization. It is the point were they organize the following steps to be done and what are to be followed to be able to reach a goal. It is also important for an organization to have both Business plan and Information system plan and both should coincide with one other to achieve a definite goal.