Escolar Documentos
Profissional Documentos
Cultura Documentos
There is no reason anyone would want a computer in their home. Ken Olsen, President and Founder of Digital Equipment Corp., 1977 640k ought to be enough for anybody Bill Gates in 1981 Everything that can be invented has been invented. Charles H.
Duell, Commissioner, U.S. Office of Patents, 1899.
4. 5.
Sustaining Technologies
Sustaining innovative technologies...
Actually help the firm by fostering improved product performance or cost effectiveness Align with the desired value proposition of established customers.
Disruptive Technologies
Disruptive Technologies
Does not have the performance or quality characteristics based on the value system used by the existing customer. Are often less expensive, simpler, smaller, and easier to use. Are first used in insignificant or narrow markets. The customers of the existing firm often dont value or cant use a disruptive technology.
As a result, technological capacity outpaces what the market needs Disruptive technologies fill in the over performance gap and become performancecompetitive.
Disruption
Time
In a nutshell
disruptive technologies are "simple, convenient-to-use innovations that initially are used by only unsophisticated customers at the low end of markets." Christiansen, 1997
Value Networks
Customers rank-order product attributes Firms operate with specific cost structures needed to provide valued products and services The success of an innovation depends upon the perceived needs of known network actors A new entrants advantage is that their agility (e.g., smaller size, openness to different perspectives, etc.) makes it easier for them to identify & make strategic commitments to develop emerging market opportunities
How to Respond?
Firms need to learn how to deal with disruptive technologies (e.g., develop internally or spin-out a separate organization)
Create an environment supportive of the different value network and this networks customers Match the size of the spin-off organization to the size of the market.
Discovery-driven planning
Realize that the basis of competition changes when the rate of technological improvement exceeds that demanded by the market.
When disruptions occur, actions must be taken before plans can be made. So, plans need to be made for learning rather than implementation
Discovery-driven planning
Identify the assumptions upon which business plans are based
Test market assumptions before expensive commitments are made Agnostic marketing where no one knows exactly why, how, or to what degree a disruptive technology will be used
Dont talk to the same people Explore the boundaries of the market
Performance oversupply results in a change in the basis of competition in a products market along four dimensions:
Functionality Reliability Convenience Price
BUSINESS PROCESSES
Business process a set of work activities and resources
Process
Collection of activities that takes one or more kinds of input and creates an output that is of value to the customer
BUSINESS PROCESSES
Business Process Redesign Business process reengineering (BPR) radical business redesign initiatives that attempt to achieve dramatic improvements in business processes by questioning the assumptions, or business rules, that underlie the organizations structures and procedures
Page 362
BUSINESS PROCESSES
Business Process Redesign
BUSINESS PROCESSES
Business Process Redesign
5. 6.
BUSINESS PROCESSES
Business Process Redesign
Definition Phase:
End user and systems analysts conduct analysis of current system and business processes Analysis is:
Process-oriented Data-oriented
Construction Phase:
System designed, built, and tested System logically described, then physically Technology chosen Programs, inputs, and outputs designed Software programmed and tested User acceptance testing conducted
Implementation Phase:
Business managers and IS professionals install new system Data and procedures from old system converted
Provides a baseline for the new system Includes both logical and physical models
Fundamental
Why do we do what we do? Why do we do it the way we do?
Radical
Getting to the root of things: not making superficial changes or fiddling with what is already in place Disregarding all existing structures and procedures and inventing completely new ways of accomplishing work
Dramatic
Reengineering isnt about making marginal or incremental improvements but about achieving quantum leaps in performance Dramatic improvement demands blowing up the old and replacing it with something new
. . no one wants to be reengineered. No one wants to hear dictums like, Carry the wounded but shoot the stragglers No one wants to see 25-year-old MBAs in their first year of consulting making $80,000 per year with $30,000 signing bonuses, being billed out at six times their salaries, putting the companys veterans through their paces like theyre just another group of idiots who cant think out of the box.
The most profound lesson of business process reengineering was never reengineering, but business processes. Processes are how we work. For technologists, the lesson from reengineering is a reminder of an old truth: information technology is only useful if it helps people do their work better and differently. Companies are still throwing money at technology -- instead of working with the people in the organization to infuse technology.
Reengineer slowly
To maintain momentum you must produce results quickly.
IT PROJECT MANAGEMENT
IT Project management requires knowledge of system development methodologies:
SDLC Prototyping RAD Purchasing life cycle
IT PROJECT MANAGEMENT
IT PROJECT MANAGEMENT
Most projects share common characteristics:
1. Risk and uncertainty highest at project start 2. Ability of stakeholders to influence project greatest at project start 3. Cost and staffing levels lower at project start and higher toward end
(PMI, 1996)
IT PROJECT MANAGEMENT
Project:
Temporary endeavor to create unique product or service Typically a one-time initiative Can be divided into multiple tasks Requires coordination and control Has a definite beginning and end
IT PROJECT MANAGEMENT
Project:
Temporary endeavor to create unique product or service Typically is a one-time initiative Can be divided into multiple tasks Requires coordination and control Has a definite beginning and end
IT PORTFOLIO MANAGEMENT
IT Portfolio set of IT project initiatives currently in progress, as well as requests for IT projects that have not yet been funded
IT PORTFOLIO MANAGEMENT
PROJECT INITIATION
Project charter Scope statement Feasibility analyses
Economic Operational Technical
PROJECT PLANNING
Three major components:
Schedule Budget Staff (project team)
PROJECT PLANNING
Scheduling
PROJECT PLANNING
Scheduling Timeboxing organizational practice in which a system module is to be delivered to user within a set time limit, such as 6 months
Work breakdown a basic management technique that systematically subdivides blocks of work down to the level of detail at which the project will be controlled
PROJECT PLANNING
Staffing
PROJECT PLANNING
Planning Documents Two typical planning documents: Statement of Work (SOW)
For the customer High-level document that describes what project delivers and when Contract between project manager and executive sponsor
Project Plan
Used by project manager to guide, monitor, and control execution of project Reviewed by managers or committees that oversee project
PROJECT PLANNING
Planning Documents Two typical planning charts: PERT (or CPM) Gantt
Page 429
PROJECT PLANNING
Planning Documents
(Reprinted from Valacich, George, and Hoffer, Essentials of Systems Analysis & Design, Prentice Hall, 2001)
(Reprinted from Valacich, George, and Hoffer, Essentials of Systems Analysis & Design, 1st Edition, Copyright 2001. Reprinted by permission of Pearson Education, Inc. Upper Saddle River, NJ)
PM Goal:
Manage risk of failing to achieve project objectives Human error Project scope changes Unanticipated technology changes Internal politics
Causes of Risk:
PROJECT CLOSING
IT project deliverables completed Formal user acceptance obtained or failed project terminated Common questions for team members:
What went right on this project? What went wrong on this project? What would you do differently on the next project, based on your experience with this project?
Introduction
Network effects: When the value of a product or service increases as its number of users expands
Also known as network externalities or Metcalfes Law
6-81
Complementary benefits: Products or services that add additional value to the network
6-82
6-83
Two-sided markets
Network markets comprised of two distinct categories of participant, both of which that are needed to deliver value for the network to work Have cross-side exchange benefits
When an increase in the number of users on one side of the market creates a rise in the other side
6-84
6-87
6-88
6-89