- Paperback: 648 pages
- Publisher: Wiley US; 1 edition (8 December 2006)
- Language: English
- ISBN-10: 0471777110
- ISBN-13: 978-0471777113
- Product Dimensions: 18.8 x 3.4 x 23.4 cm
- Boxed-product Weight: 816 g
- Average Customer Review: Be the first to review this item
- Amazon Bestsellers Rank: 200,917 in Books (See Top 100 in Books)
Information Development: Managing Your Documentation Projects, Portfolio, and People Paperback – 8 Dec 2006
|New from||Used from|
Customers who bought this item also bought
From the Back Cover
The 1994 bestselling classic Managing Your Documentation Projects set the industry standard for technical documentation. However, since then, much has changed in the world of information development. With this new title, JoAnn Hackos looks beyond the structured project of the 1980s and 1990s. Instead, she focuses on the rapidly changing projects of the 21st century and addresses how to introduce agile information development without neglecting the central focus of planning information design and development around the needs of information users.
As an information-development manager, you are expected to reduce costs and project time, do more work with fewer resources and less money, and increase the value of the information you deliver. Recognizing this, Hackos has carefully designed this book to help you do precisely that. She helps you make strategic decisions about information development and directs the discussion of project management toward smarter decision-making.
An update of the original 1994 Information Process Maturity Model (IPMM) presents you with a method by which you can compare the state of your organization to others, evaluate your current status, and then consider what is necessary in order to move to the next level.
Information Development offers a completely new look at best practices for all phases of the document development lifecycle, including:
- Managing a corporate information portfolio
- Evaluating process maturity
- Partnering with customers and developing user scenarios
- Developing team effectiveness and collaboration
- Planning and monitoring information projects
- Managing translation and production
- Evaluating project performance
- Managing for quality, efficiency, and cost-effectiveness
The companion Web site includes electronic versions of the templates and checklists featured in the book.
Wiley Technology Publishing Timely. Practical. Reliable.
Visit our Web site at www.wiley.com/compbooks/
About the Author
No customer reviews
|5 star (0%)||0%|
|4 star (0%)||0%|
|3 star (0%)||0%|
|2 star (0%)||0%|
|1 star (0%)||0%|
Review this product
Most helpful customer reviews on Amazon.com
The book is about project management, not product development. It is about "what" needs to be done to delivery the product. Not "how" to develop the product itself. Project management (the tasks for running a project and conserving the people who work on it) wraps around every type of product development, including Agile development.
Project management has been around since at least the pyramids. But this author was the first to tailor the practice to Technical Communication. Project Management is structured common sense applied to delivering a product. And common sense in any field is usually obvious to everyone once they hear it. But it is a revelation when you are at the start of your career and almost everything is "new".
I have used this methodology since it was published in 1994. It is scalable from a product due in a few hours to the products from a 1,000 work year project.
It works for a "team of one" - especially in solo practice - to managing large teams of technical writers and Subject Matter Experts. It works for single books, a set of books and Tender responses. It works irrespective of the type of documentation product - paper, electronic, multimedia and so on. I have used it for all of the above.
If you are new to the discipline of Technical Communication, this is logically the third step in your development. First you need to learn the tools you will use so you can work productively. Second you need to learn some of the techniques of this profession so you can work effectively. By then you are ready to learn how to work efficiently. But if you can read this book in parallel with the other two steps, you will understand and learn so much more from what is going on around you.
Thank you JoAnn. I wish you had a training class... I would be there!!!!
Under information planning, this book only tells you that you should do it. Gee, thanks. Under estimating and scheduling - you should estimate future project resources and you should request new resources and fund innovation. Oh, boy. Yippee.
This book is an exercise in stating the blatantly obvious. I expected to see information on the nuts and bolts of producing technical documentation...I expected to see examples of budgets, examples of ways to create efficient systems for document production using single-sourcing, and to see examples of specific, important techniques for planning a document production process that allows for easy translation, revision, re-usability and transfer to different mediums. I expected to get a reference that would become well-worn on my desk. This book is as far from such a tome as it could possibly get while still being written in the English language.
I want to improve the efficiency of my documentation projects. I'd like to know about technologies (XML?, VBA?) that might help me with separating content from layout and improving reusability. Is that here? Nope. But you do get way too much talk about how you should acquire good tools that support your business goals. There is nothing about what those tools should be or what specifically would make them good.
One page tells you the difference between a "traditional" project and an "agile" project...things like: An agile project "responds to change" and has "minimal process documentation" as well as "reduced development schedules". That's nice. Who cares?
Implementing a Topic Architecture is the only section that even makes a move in the direction of specific, concrete, useful material. But even it leaves you thinking, "Well, duh...yathink?"
To sum up, this book tells you all the obvious things you ought to do...but that's it. It doesn't have anything to say about HOW you would actually do those things. I doubt the author has the foggiest idea how because I doubt she has a single hard skill to speak of. She definitely didn't write about any.