Sponsored links

Valid XHTML 1.0!
Valid CSS!

Product: Book - Paperback
Title: CWNA Certified Wireless Network Administrator Official Study Guide (Exam PW0-100), Third Edition (Planet3 Wireless)
Publisher: McGraw-Hill Osborne Media
Authors: Planet3 Wireless
Rating: 5/5
Customer opinion - 5 stars out of 5
CWNA Certified as of 2/11/05

Well....were do I start. I took this exam twice before passing it. I think the problem was that I really didn't read the book from cover-to-cover. So on the third try I read this book 6 times.

In short READ this book from cover to cover. A hint: foucs alot on chapter 11 because it hits about 30 percent of the objectives and you cannot check your answers after you move on to the next question. Now thier are some questions that are not in the book like 802.3af standard(s), so read some white papers.

This exam is very hard. The question all seem to be right so you MUST know the aswner like you have worked in the field and that is why this certification is a good one to get.

Well....good luck in your testing and take your time.

Product: Book - Paperback
Title: Developing J2EE Applications with WebSphere Studio: IBM Certified Enterprise Developer (IBM Certification Study Guides)
Publisher: Mc Press
Authors: Howard Kushner, Colin Yu, Doug Weatherbee, Gene Van Sant
Rating: 3/5
Customer opinion - 3 stars out of 5

I initially got this book mainly as a prep for the IBM Cert exam but then discovered that there's tons of great stuff for development and testing. I've usually had to dig into a number of sources for this stuff, if I could even find the info. It's all here in this book. I especially found the profling chapter informative. I'd wondered about WSAD's profiler and usefulness but couldn't find much info on it. This book's got tons in it. Worth getting if you're doing any serious dev in WSAD 5.

Product: Book - Paperback
Title: Microsoft Visual Basic .NET Step by Step--Version 2003 (Step By Step (Microsoft))
Publisher: Microsoft Press
Authors: Michael Halvorson
Rating: 1/5
Customer opinion - 1 stars out of 5
Not for developers

As posted above, this book is not for developers. It's not a big book, but what it covers could fit in a handbook. I would recommend "Programming Microsoft Visaul Basic .NET" by Francesco Balena instead.

Product: Book - Paperback
Title: Waltzing With Bears: Managing Risk on Software Projects
Publisher: Dorset House Publishing Company, Incorporated
Authors: Tom Demarco, Timothy Lister
Rating: 5/5
Customer opinion - 5 stars out of 5
Born to Become a Classic

Unlike other risk management books, DeMarco and Lister's book is written in a casual, provocative style - you always have the feeling the authors are talking to you and not to their peers. If you prefer a formal and structured style read, for example, Elaine Hall's "Managing Risk", also an excellent book but for other reasons. If you like new, creative, challenging, less structured ideas, this book is for you.
The first part of the book explains why risk has to be faced and managed. Risks and benefits always go hand in hand: "If a project has no risks, don't do it." Companies that choose to take risks grow; those that avoid them have to struggle to stay even. I like the idea that "Risk management is project management for adults". While children can be excused from thinking about unpleasant things like war, rape, or injustice, adults do not have that choice. Taking note of bad things that can happen and planning for them is a mark of maturity. Among several reasons given by the authors for adopting risk management, the one I like best is: "Risk management decriminalizes risk."
Part II addresses why risk management would not work for some organizations. In some corporate cultures "It's okay to be wrong, but not okay to be uncertain." However, ignoring risks tends to make one depend on luck. And when luck is a part of your strategy, you're in trouble.
Part III is about implementing risk management. DeMarco and Lister provide us with an excellent explanation on how to build a risk diagram and also give us hints on identifying project risks based on previous projects. For those who like structured methods, the authors present a nine-step risk management process that is refined later in the book. I liked the nice and clear explanation of Monte Carlo simulation as applied to risk management. The authors describe a simple Excel-based tool for risk management - Riskology. The tool can be freely downloaded from the their website. A whole chapter is dedicated to the 5 core risks of software projects: schedule flaw, requirements inflation, turnover, specification breakdown, and under-performance. Another chapter details a defined process for risk discovery. It was nice to see the Win Win Spiral Model mentioned in the book. Barry Boehm's Win Win Spiral Model is an excellent tool for negotiating software and system requirements as well as architectural solutions from a risk-driven point of view. In the remainder of Part III the authors discuss risk management activities that must be active throughout a project's lifecycle, the use of measures of completeness such as Earned Value, and the virtues of incremental development with respect to risk management.
Part IV addresses the difficulties encountered in quantifying costs and benefits to determine how much should be invested in risk management.
Part V presents guidelines that can be used to find out whether or not risk management is being practiced in an organization.
This is an invaluable book for anyone seeking to understand and learn risk management. Its style and content will please both the beginner and the experienced risk manager. The authors of the acclaimed classic "Peopleware" have shown us they continue to be great writers. This book is bound to become another classic.