Item description for Achieving Project Management Success Using Virtual Teams by Parviz F. Rad & Ginger Levin...
Most books on this subject are limited to a specific industry or market segment. This is an in-depth guide for managing a virtual project team in any industry. The book describes how to build high-performance virtual project teams; shows how to reduce the cost of virtual teams to ensure desired results and includes tools and techniques for assessing the maturity of project teams. It illustrates how to decrease time to market for new products, increase corporate profits and much more.
Promise Angels is dedicated to bringing you great books at great prices. Whether you read for entertainment, to learn, or for literacy - you will find what you want at promiseangels.com!
Est. Packaging Dimensions: Length: 0.5" Width: 6.25" Height: 9.25" Weight: 0.9 lbs.
Publisher J. Ross Publishing, Inc.
ISBN 1932159037 ISBN13 9781932159035
Reviews - What do customers think about Achieving Project Management Success Using Virtual Teams?
Excellent Overview of Mature Project Teams Jan 29, 2008
Though dry, this book provides an excellent overview of how virtual project teams mature. It helped me to identify problem patterns in the processes at my employer, as well as to suggest ways in which the issues may be resolved over time.
The authors also provide a section on worker motivation that I found very useful. In addition to improving how I relate to my peers, the model aided in introspection on my personal working patterns.
Overall this book was well worth my time and I highly recommend it.
Good introduction to managing virtual teams and the difference versus co-located teams Apr 17, 2006
The authors put together a maturity model for virtual teams. It provides at least a way to measure the team and its performance against a base, so it is a good starting point. The model seems to be a take off on the Capability Maturity Model (CMM) used to assess software development procedures and processes, for example a virtual team is defined as being at level 5 when they are involved in continuous improvement or having repeatable processes, similar to obtaining CMM 5. With interest I noted that in order for a team to reach level 3, the project manager cannot also manage a co-located team, or a team located in the same place where he/she is working. I believe this means that if he/she manages a group that is located in Texas and another group located in Ukraine it is okay as long as he/she lives in California; not in Texas or Ukraine. Why this is necessary in order to be at level 3 is not clear to me. To have 30 persons all working in different locations and not have the project manager at least located with some of the team members is not likely to occur in a software development situation.
Achieving Project Management Success Using Virtual Teams is a good introduction to project management and provides a good base for examining the differences between the two types of teams. The authors' state that they wish to provide project management professionals with a book to prepare them for the dissimilarities between traditional and virtual project teams, while highlighting what remains unchanged when one moves from a traditional to a virtual project. Since they spend a lot of time talking about the traditional project team development, they probably hit that objective. They developed a good base, in the form of a chart, of how some of the typical project management procedures change when moving from a traditional team to a virtual team. The assessment tools discussed are also excellent for any type of a team, and having the documents available for download works out well to make the tools useable and easier to pass around amongst a team.
Overall though, more discussion on how to handle the differences between traditional and virtual teams, and backing these areas up with examples and case studies would have strengthened the book. Additionally, two questions which specifically relate to software development situations, kept running through my mind as I was reading this book: How do the virtual team policies and procedures described in the book, change for an outsourced versus an insourced (i.e. all members of the team work for the same company) team? Secondly, how do virtual team policies and procedures change when a virtual team consists of multiple co-located groups? Perhaps subjects for a new book.
Insights for Any Virtual Team Aug 20, 2003
By definition the focus of a project team is the deliverables. It does not matter if the team is collocated or dispersed. That means the focus on cost, risk, change and scope management remains the same.
If the team is dispersed, the authors content, the people side of the effort assumes a different cast. Processes and procedures that deal with client satisfaction, vendor satisfaction and team morale become more complex.
The authors provide a five-step model to assess the maturity of the team. They describe various methods to motivate different personality types to achieve the best project results.
Reliance on virtual teams is growing. If you are attempting to lead one, this book is a must. Its insights, worksheets and assessment tools will save you time, money and aggravation.