Friday, January 23, 2009

Organization Development at Work or Technology Acquisition

Organization Development at Work (Practicing Organizational Development Series): Conversations on the Values, Applications, and Future of OD

Author: National OD Network

Organization Development at Work—a title in The Practicing OD Series—is a collection of conversations among leaders, practitioners, and educators in the organization development (OD) field. Throughout the book experienced professionals share their best thinking about principles, practices, values, and the future of OD. In this valuable resource, nearly 100 contributors share their operating principles, successful models, tools, application tips, and important insights from their years of practice. Written for organization development practitioners, consultants, and anyone who is considering a career in OD, Organization Development at Work will highlight the points of view that define the "values controversy" so you will be better able to clarify your own position on values-based work. As you read contributors stories, you will be able to compare your career path with others in the field. In addition, this book offers perspective on the debate about global work, with advice for practitioners seeking to do work on foreign soil. You will feel as if you are in a conversation with friends, mentors, and colleagues who are freely sharing their experiences, questions, and concerns.



See also: Das Verstehen von Handlungsweisen für Wirksamen Leaderhsip

Technology Acquisition

Author: Allen Eskelin

With proven, step-by-step solutions, this unique and practical book shows information technology (IT) project managers how to acquire the right technology from the right vendor at the right price for their business. There are numerous project management books on how to build technology, but the increase in project failure, limited resources, and accelerated change in systems and platforms has forced IT managers to move from building to buying technology, thereby shifting substantial risks to third parties. Allen Eskelin, drawing on his own experience managing acquisition projects, thoroughly explains each task required to buy technology successfully from outside vendors.

Technology Acquisition covers all facets of technology acquisition management, including the "people dynamics" that can make or break a project. The book offers useful templates, example documents, checklists, and schedules that guide you through the entire procedure, as well as case studies to illustrate the processes described. These processes include:

  • Initiation--creating and chartering a project to address your business needs
  • Planning--organizing teams; defining and prioritizing requirements; identifying vendors
  • Research--gathering information on vendors and their technologies
  • Evaluation--interpreting the results of research; selecting a vendor
  • Negotiation--defining a negotiating strategy; planning the negotiation; negotiating successfully
  • Implementation--developing, testing, and deploying vendor solutions
  • Operations--managing an ongoing process to extend the life of the product

Booknews

This guide for information technology (IT) project managers describes best practices for business technology acquisition from outside vendors. Eskelin, an IT manager at Starbucks, presents suggestions for each stage of the acquisition process, from planning and research through evaluation, negotiations, implementation and operations. The text is accompanied by templates, sample documents, checklists, schedules, and illustrative case studies. Annotation c. Book News, Inc., Portland, OR (booknews.com)



Table of Contents:
Acknowledgments
Reference Map
Introduction
1Initiation1
2Planning23
3Research61
4Evaluation123
5Negotiations133
6Implementation147
7Operations157
Resources167
Index169

1 comment:

Unknown said...

The procedure should be a continuous one for every organization. It allows control to keep its beat on its own industry, but also be conscious of what is occurring in nearby marketplaces. In technological innovation, this is particularly crucial as so often technologies overlap and meet to fix different discomfort factors differently. Acquisitions should be considered as a complement to, rather than a replace development and value development. But many are often created under short-term demands to demonstrate development.

Technology Acquisition