On Time Technology Implementation presents technology implementation guidelines and lessons learned from over 30 years of successful, hands-on project experience.
@introbul:Key Features @bul:* How to prevent the top 10 reasons for implementation failure
- Over 200 specific guidelines and lessons learned
- How to implement electronic commerce
- Five example companies from banking, insurance, transportation, government, and manufacturing
- How to use intranet and object oriented methods for maximum advantage
- How to cope with the burden of maintenance, enhancement, and production support
- How to implement knowledge management and data warehousing applications
- How to implement Enterprise Resource Planning (ERP) software
- How to develop and implement software on time and within budget
- How to effectively evaluate, select, and implement software packages
- How to control changing requirements and scope
- Critical success factors in system and business process implementation
- How to apply concurrent engineering to software development
- Experience and tips to develop intranet/Internet based applications
Courses in management, business, library science, and engineering dealing with data management, information management, systems and technology; professionals in information systems and business staff & managers involved in strategy and planning to improve and implement business processes, information systems managers, business managers, project leaders, systems and business analysts, process engineers, and human resources.
Part I--Set the Direction: Introduction: Introduction. Business Direction of Information Technology. Business Processes and Technology. Technology and Software Tool Trends. Challenges Facing Information Technology and Management. Critical Success Factors in Systems and Technology. Trends in Software Development. Trends in Software Packages. Trends in Knowledge Management. Techniques of the Past. Where Are the Benefits? A Real World Approach. Organization of the Book. Transition to a New Approach. Examples. Lessons Learned. Summary. What to Do Next.
Develop the Business Process Plan and Strategy: Introduction. Observations on Business Processes. Common Problems with Processes. Steps in Developing the Process Plan and Strategy. How to Build Your First Process Plan. What Can Go Wrong? Reduced Schedule and Low-Cost Approach. Examples. Lessons Learned. Summary. What to Do Next.
Define the New Process, Benefits, and Requirements: Introduction. Step 1: Define the New Business Process. Step 2: Determine Requirements for the New Process. Step 3: Identify Costs and Benefits. Step 4: Present the Results to Management. Step 5: Determine the Technology Approach and Refine Costs and Benefits. Step 6: Make the Buy or Build Decision. What Can Go Wrong? Reduced Schedule and Low-Cost Approach. Examples. Lessons Learned. Summary. What to
- No. of pages:
- © Academic Press 2000
- 19th October 1999
- Academic Press
- Paperback ISBN:
Bennet Lientz has taught and consulted on project management for the past 28 years to more than 5000 people. He developed the concept of the management critical path, acted as project manager of the Internet, and turned around 10 failing projects. This Second Edition is Lientz’ seventh book; he has also written more than 25 articles in various areas of project management.
The John E. Anderson School of Management, University of California, Los Angeles, U.S.A.
Kathryn P. Rea is president and founder of The Consulting Edge, Inc., which was established in 1984. The firm specializes in E-Business, process improvement, project management, and financial consulting. Rea has managed more than 65 major technology-related projects internationally. She has advised on and carried out projects in government, engergy, banking and finance, distribution, trading, retailing, transportation, mining, manufacturing, and utilities. She is the author of eight books and more than 20 articles in various areas of information systems and analysis.
The Consulting Edge, Beverly Hills, California, U.S.A.
"The book is more in tune with the real situation that you find in IT with limited resources and time. The book also gives recognition to the fact that legacy systems will be around for a long time. Many other books assume that these can be replaced or ignored. We spend over half of our programmer time on legacy systems maintenance so that allocating the rest of their time is a major concern-which this book addresses. Another good idea is that in software package evaluation, you do not focus on software features, but instead on what capabilities the packages are lacking. We used this idea to select different accounting software than if we had used features. The book is easy to read and can be used by nontechnical people." @source:--A reader on Amazon.com