<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Project Management</title>	<link>http://tc.eserver.org/dir/Project-Management</link>
	<description>A listing of the most recently indexed works about Project Management in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Project Management</title>
		<link>http://tc.eserver.org/dir/Project-Management</link>
	</image>
	<item>
		<title>Alfresco Share for Streamlining Project Management And Collaboration</title>
		<link>http://tc.eserver.org/35779.html</link>
		<guid>http://tc.eserver.org/35779.html</guid>
		<description>Alfresco integrates easily with existing behaviors, is nimble enough to be adapted to fluid processes, facilitates project communication, and proactively provides the right information to the right people.</description>
	</item>
	<item>
		<title>Agile User Experience Projects</title>
		<link>http://tc.eserver.org/35715.html</link>
		<guid>http://tc.eserver.org/35715.html</guid>
		<description>Agile projects aren&apos;t yet fully user-driven, but new research shows that developers are actually more bullish on key user experience issues than UX people themselves.</description>
	</item>
	<item>
		<title>Websites: Designed by Dogs, Managed by Cats</title>
		<link>http://tc.eserver.org/35631.html</link>
		<guid>http://tc.eserver.org/35631.html</guid>
		<description>Websites are generally designed by dogs. There’s a lot of optimism. The dogs look at the website and think of it as an endless attic. No matter how much stuff you into it, there’s always room for more. The dogs approach each design step with a ‘have gigabytes, must fill’ enthusiasm. And then cats have to manage the website. The dogs let everyone publish and the cats are certainly not going to review all this stuff. The dogs created an architecture where everyone can find everything and now nobody can find anything. The cats shake their heads.</description>
	</item>
	<item>
		<title>Managing International Assignments</title>
		<link>http://tc.eserver.org/35636.html</link>
		<guid>http://tc.eserver.org/35636.html</guid>
		<description>The traditional concept of an ‘international assignment’ is rapidly becoming a misnomer. Certainly the situation whereby an individual (with or without accompanying family) is sent to an overseas location for two or three years still occurs – despite the recent downturn in business. However, today there are all sorts of permutations of business activities that can result in business people working with international colleagues and clients. It may be that people are on short-term assignments (e.g. one to six months) in another country or that they are frequent business travelers visiting subsidiaries and clients or even that they are managers of long-distance teams working on developing new products for third country markets.</description>
	</item>
	<item>
		<title>More With Less: the 80/20 Rule of Project Management</title>
		<link>http://tc.eserver.org/35681.html</link>
		<guid>http://tc.eserver.org/35681.html</guid>
		<description>Every project manager has probably thought at some point, “If only I had more time, I would be better at my job.” Unfortunately, most of us aren’t lucky enough to be given more time to do our jobs. Time is usually the project constraint that is the least flexible. We are constantly forced to prioritize our work, but don’t always make the right choices.</description>
	</item>
	<item>
		<title>From Drawing Board to Working Code: Software in the Real World</title>
		<link>http://tc.eserver.org/35621.html</link>
		<guid>http://tc.eserver.org/35621.html</guid>
		<description>Some of my designs never make it to market due to lack of funding prior to release and the company slips quietly away or gets bought and I lose contact. Other times by the time the software is released, the person who hired me has left the company and moved onto other pastures. So it&apos;s always a treat when someone calls me back to say &quot;Would you like to come in and see the software? We&apos;re nearly done.&quot;</description>
	</item>
	<item>
		<title>Symphony or Jazz Band Metaphor for Software Development</title>
		<link>http://tc.eserver.org/35623.html</link>
		<guid>http://tc.eserver.org/35623.html</guid>
		<description>One of the online lists I read frequently has been debating the proper metaphor for the software development environment. The building trade has been used quite often in the past. In fact, we use the term &quot;architect&quot; quite frequently, although ten software engineers will probably give you ten different definitions of what an architect actually should do. I think there is no single metaphor for software development roles because there is not a single software development environment.</description>
	</item>
	<item>
		<title>Going Viral</title>
		<link>http://tc.eserver.org/35609.html</link>
		<guid>http://tc.eserver.org/35609.html</guid>
		<description>Our plan was to market Project Dragonfly virally. Going out now meant that we were a little early and many details were still on the to-do list. As a user centered design practitioner working with an Agile Development process, I was comfortable working in an iterative manner to engage users quickly so that we think through details and bring solutions forward. Yet something about this situation seemed different to me. We wanted the world to broadcast about the benefits of Project Dragonfly while our marketing efforts simply facilitated the conversation.</description>
	</item>
	<item>
		<title>How Soon is Now?</title>
		<link>http://tc.eserver.org/35586.html</link>
		<guid>http://tc.eserver.org/35586.html</guid>
		<description>One common complaint a lot of technical writers have is that they aren’t included early enough in lifecycle of a project. The downsides are that by the time work hits your desk you don’t have a full picture of who the customer is, why they want whatever it is you are building, and how they want it provided to them. All of which directly impacts the information being created.</description>
	</item>
	<item>
		<title>Managing a Documentation Project Successfully: More Jelly and Ice Cream</title>
		<link>http://tc.eserver.org/35530.html</link>
		<guid>http://tc.eserver.org/35530.html</guid>
		<description>This video on simplifying business, using the metaphor of organising a children’s party, made me smile and consider how successful documentation projects are managed. The presenter is suggesting managers need to, in complex systems, give up rigid control from above. Instead, they should watch for organisational patterns, encouraging the good and discouraging the bad.</description>
	</item>
	<item>
		<title>Managing Documentation Projects: Keeping the Plates Spinning</title>
		<link>http://tc.eserver.org/35434.html</link>
		<guid>http://tc.eserver.org/35434.html</guid>
		<description>A product is only as good as its information. With good information, customers can use the product--be it a piece of software, a hand-held electronic device, or a supersonic aircraft--and are more likely to hold a good opinion of its manufacturer. Without good information, no matter how good the product is, customers will be frustrated and will probably look elsewhere. It&apos;s not a stretch to say that the documentation project manager is instrumental in determining whether a product succeeds.</description>
	</item>
	<item>
		<title>Managing a Documentation Project: A Guide</title>
		<link>http://tc.eserver.org/35436.html</link>
		<guid>http://tc.eserver.org/35436.html</guid>
		<description>This a short video overview of managing a documentation project. It&apos;s something we put together as a test of some of the functionality of Techsmith&apos;s Camtasia software.</description>
	</item>
	<item>
		<title>Organizational Culture 101: A Practical How-To For Interaction Designers</title>
		<link>http://tc.eserver.org/35231.html</link>
		<guid>http://tc.eserver.org/35231.html</guid>
		<description>It’s happened to all of us. We walk into what we think is a Web redesign project, only to find we have unwittingly ignited the fires of WW III in our client’s organization. What begins as a simple design project descends – quickly – into an intra-organizational battle, with the unprepared interaction designer caught in the crossfire.&#xD;&#xD;What is it about design projects that seem to attract such power struggles? Contrary to what you might think, being stuck in the middle of an internecine battle is actually an opportunity to effect meaningful change on your client’s organization. But it requires a set of practical tools to negotiate these battles and a more sophisticated language and knowledge to exploit these events to create meaningful change.</description>
	</item>
	<item>
		<title>Too Many Inputs Freak Out the Technical Writer</title>
		<link>http://tc.eserver.org/35208.html</link>
		<guid>http://tc.eserver.org/35208.html</guid>
		<description>In such a scenario, this article presents some of the practices that have helped me track and address inputs effectively – regardless of their volume and importance.</description>
	</item>
	<item>
		<title>Legal Requirements in the New Age</title>
		<link>http://tc.eserver.org/35185.html</link>
		<guid>http://tc.eserver.org/35185.html</guid>
		<description>Consider a plan that identifies who in your company will address phone or other inquiries if something goes viral (read the article and you’ll see what I mean).</description>
	</item>
	<item>
		<title>Information Overload: Conversation with Ricardo Amigo</title>
		<link>http://tc.eserver.org/35193.html</link>
		<guid>http://tc.eserver.org/35193.html</guid>
		<description>Dealing with information overload can be a huge stressor in life. Not only trying to keep up with the constant deluge of information that comes at you daily, but also managing that information in an organized way — so that you can find and implement it — can put your sanity in question. In this podcast, I talk with Ricardo Amigo, a translator in Costa Rica, about different ways to manage information overload.</description>
	</item>
	<item>
		<title>Integrating Prototyping Into Your Design Process</title>
		<link>http://tc.eserver.org/35176.html</link>
		<guid>http://tc.eserver.org/35176.html</guid>
		<description>Prototyping is a big deal right now. We get wrapped up in mailing list threads, new tools are released at an astonishing pace, books are being published, and articles show up on Boxes &amp; Arrows. Clients are even asking for prototypes. But here’s the thing… prototyping is not a silver bullet.&#xD;&#xD;There is no one right way to do it.&#xD;&#xD;However, prototyping is a high silver content bullet. When aimed well, a prototype can answer design questions and communicate design ideas. In this article, I talk about the dimensions of prototype fidelity and how you can use them to choose the most effective prototyping method for the questions you need answered.</description>
	</item>
	<item>
		<title>The Content Conundrum</title>
		<link>http://tc.eserver.org/35177.html</link>
		<guid>http://tc.eserver.org/35177.html</guid>
		<description>There’s often an unsettling discrepancy between the stakeholder approved wireframes and visual comps and the actual product in production. What you see in those environments is sometimes a far cry from those polished wireframes and those shiny, pixel-perfect visualizations that were filled with placeholder content (such as lorem ipsum text, dummy copy, and image blocks). What you’re seeing in production environments now holds the real content. The imagery doesn’t support the interactions, is meaningless, useless, or worse, contradictory to the design intent. The copy, headers, and labels are unclear, too long, too short, or simply irrelevant. What happened?</description>
	</item>
	<item>
		<title>Project Management is Not Overhead!</title>
		<link>http://tc.eserver.org/35151.html</link>
		<guid>http://tc.eserver.org/35151.html</guid>
		<description>Practicing good project management in the area of initiation, planning and execution will increase the performance of your project execution. Resources will be better utilized and the team will be more motivated and organized. This will reduce any duplication of effort and ensure that dependencies are dealt with in an optimal manor.</description>
	</item>
	<item>
		<title>What’s Wrong with PowerPoint as a Document Authoring Tool?</title>
		<link>http://tc.eserver.org/35078.html</link>
		<guid>http://tc.eserver.org/35078.html</guid>
		<description>It is our position that use of PowerPoint for document planning negatively impacts all potential collaborative authoring and review outcomes. Though PowerPoint is commonly used because it is a familiar tool, it is not the most effective tool for managing knowledge either intellectually or financially.</description>
	</item>
	<item>
		<title>Making Spaces in Cluttered Houses and Cluttered Lives</title>
		<link>http://tc.eserver.org/35023.html</link>
		<guid>http://tc.eserver.org/35023.html</guid>
		<description>Putting Pedersen’s advice to practice, step one is to make a place for everything in our lives. Figure out where it belongs. Just as you can’t organize a house if you have no where to put things, you can’t organize your life if you have no way space for the activities. If something doesn’t fit, it’s time for a trip to the figurative Salvation Army (we call them Deseret Industries here). In other words, simplify.</description>
	</item>
	<item>
		<title>Fifteen Steps to a More Productive Workday</title>
		<link>http://tc.eserver.org/35011.html</link>
		<guid>http://tc.eserver.org/35011.html</guid>
		<description>Freelance designers, as well as those who work for small design studios, often face the challenge of getting the most productivity out of their time and achieving maximum efficiency. While this can be a struggle for anyone in a more “typical” job, freelancers have added distractions, unique challenges, and no one to hold them accountable. To be a successful freelancer you’ll have to place a priority on productivity and find ways that work for you.</description>
	</item>
	<item>
		<title>Stasis Theory as a Strategy for Workplace Teaming and Decision Making</title>
		<link>http://tc.eserver.org/34988.html</link>
		<guid>http://tc.eserver.org/34988.html</guid>
		<description>Current scholarship tells us that skills in teaming are essential for students and practitioners of professional communication. Writers must be able to cooperate with subject-matter experts and team members to make effective decisions and complete projects. Scholarship also suggests that rapid changes in technology and changes in teaming processes challenge workplace communication and cooperation. Professional writers must be able to use complex software for projects that are often completed by multidisciplinary teams working remotely. Moreover, as technical writers shift from content developers to project managers, our responsibilities now include useradvocacy and supervision, further invigorating the need for successful communication. This article offers a different vision of an ancient heuristic—stasis theory—as a solution for the teaming challenges facing today&apos;s professional writers. Stasis theory, used as a generative heuristic rather than an eristic weapon, can help foster teaming and effective decision making in contemporary pedagogical and workplace contexts.</description>
	</item>
	<item>
		<title>Information Technologies as Discursive Agents: Methodological Implications for the Empirical Study of Knowledge Work</title>
		<link>http://tc.eserver.org/34989.html</link>
		<guid>http://tc.eserver.org/34989.html</guid>
		<description>Work activities that are mediated by information rely on the production of discourse-based objects of work. Designs, evaluations, and conditions are all objects that originate and materialize in discourse. They are created and maintained through the coordinated efforts of human and non-human agents. Genres help foster such coordination from the top down, by providing guidance to create and recreate discourse objects of recurring social value. From where, however, does coordination emerge in more ad hoc discursive activities, where the work objects are novel, unknown, or unstable? In these situations, coordination emerges from simple discursive operations, reliably mediated by information and communication technologies (ICTs) that appear to act as discursive agents. This article theorizes the discursive agency of ICTs, explores the discursive operations they mediate, and the coordination that emerges. The article also offers and models a study methodology for the empirical observation of such interactions.</description>
	</item>
	<item>
		<title>Why Good Projects Go Bad</title>
		<link>http://tc.eserver.org/34877.html</link>
		<guid>http://tc.eserver.org/34877.html</guid>
		<description>The number of IT projects that end in failure is staggering. According to a 2007 study by researcher Market Dynamics, 62% of all IT projects miss their deadlines, 49% go over budget and 41% fail to deliver the benefits that were expected. That is worrying enough for IT departments. But for consultants and software vendors, keenly aware that project failure could well result in litigation, it is a constant concern.</description>
	</item>
	<item>
		<title>Lying in a Hammock, or, Having a Single Goal without a Purpose</title>
		<link>http://tc.eserver.org/34890.html</link>
		<guid>http://tc.eserver.org/34890.html</guid>
		<description>When you live in the moment, completing the activity itself is the success. And because writing is so multifaceted in effect — the effect both on me and others — having an open purpose doesn’t limit the results. I’m not narrow-mindedly searching for a specific achievement to happen. Instead, I’m open to unconsidered possibilities, if any of those possibilities decide to unravel.</description>
	</item>
	<item>
		<title>What&apos;s the Right Answer? Team Problem-Solving in Environments of Uncertainty</title>
		<link>http://tc.eserver.org/34834.html</link>
		<guid>http://tc.eserver.org/34834.html</guid>
		<description>Whether in the workplace or the classroom, many teams approach problem-solving as a search for certainty—even though certainty rarely exists in business. This search for the one right answer to a problem creates unrealistic expectations and often undermines teams&apos; effectiveness. To help teams manage their problem-solving process and communication better, I teach a systematic comparison approach that transforms the search for certainty into a search for the best alternative based on clearly defined and weighted criteria. With this method, team members realize that all problem- solving involves subjective judgments, but that making that subjectivity transparent increases the chances that an adopted solution will in fact solve the business problem at hand.</description>
	</item>
	<item>
		<title>Create Effective Project Milestone Sheets</title>
		<link>http://tc.eserver.org/34772.html</link>
		<guid>http://tc.eserver.org/34772.html</guid>
		<description>The project milestone sheet is an incredibly important document for freelancers and their clients. It defines all the most important tasks, who is assigned to them, and when they are due. In other words, it serves as the map for your entire work process.</description>
	</item>
	<item>
		<title>Three Questions to Start Thinking Like a Content Strategist</title>
		<link>http://tc.eserver.org/34754.html</link>
		<guid>http://tc.eserver.org/34754.html</guid>
		<description>A content strategist looks at all the content from a holistic point of view, treating everything as content, and analyzing whether each aspect of the content aligns with the company’s messaging, branding, and intent. The content strategist is acutely aware of the multifaceted nature of the user experience. It’s not just the user interface that influences the user, or the marketing material, or the training — it’s all of this and more, working together as one. The whole user experience is the content strategist’s domain, not just help materials or written text.</description>
	</item>
	<item>
		<title>Is This Meeting Really Necessary?</title>
		<link>http://tc.eserver.org/34750.html</link>
		<guid>http://tc.eserver.org/34750.html</guid>
		<description>In a world of virtual tools—blogs, wikis, feeds, forums, listservs, e-mail, IM, chat, Twitter, social networks—one would think that the traditional sit-down, face-to-face meetings had been relegated to a place in a historical museum among other old, discarded traditions (like wearing cravats). But even in the 21st century, many people still believe that if you want to accomplish serious planning and discussion, you need an in-person meeting.</description>
	</item>
	<item>
		<title>Innovation Workshops: Facilitating Product Innovation</title>
		<link>http://tc.eserver.org/34644.html</link>
		<guid>http://tc.eserver.org/34644.html</guid>
		<description>Innovation workshops can both help you come up with great ideas and align your multidisciplinary product team around them. Innovation workshops facilitate collaboration, foster trust, and promote free expression. They provide a venue for engaging a cross-functional team in brainstorming and creative ideation, filtering a large set of ideas, collaborating on design, rapidly gathering user feedback and iterating designs, and getting the consensus you need to drive an innovative product to market.</description>
	</item>
	<item>
		<title>Reusing the User Experience</title>
		<link>http://tc.eserver.org/34645.html</link>
		<guid>http://tc.eserver.org/34645.html</guid>
		<description>As a rule of thumb, the earlier in the development process reuse can occur, the more efficient reuse becomes. Like software component reuse, the reuse of UX design elements can be a very efficient form of reuse—particularly because this form of reuse occurs very early in the product development cycle. The ability to reuse prior work effectively is one characteristic of a mature discipline.</description>
	</item>
	<item>
		<title>Why Businesses (Don&apos;t) Collaborate: Meeting Management, Group Input and Wiki Use</title>
		<link>http://tc.eserver.org/34583.html</link>
		<guid>http://tc.eserver.org/34583.html</guid>
		<description>Today, content professionals are tugged in multiple directions, expected to multi-task their way through an increasing amount of work with the help of software tools designed to make them more productive. This survey aims to explore how you and your co-workers utilize software tools and determine, in various scenarios, whether they are actually a help or a hindrance.</description>
	</item>
	<item>
		<title>Managing Product Translation: One Technical Communicator’s Experiences</title>
		<link>http://tc.eserver.org/34596.html</link>
		<guid>http://tc.eserver.org/34596.html</guid>
		<description>As Documentation Manager, I was recently responsible for selecting a subcontracting company to localize one of our applications and its related manuals into three European languages: French, German, and Spanish. Concomitantly, R &amp; D hired quality control testers, with fluency in each of the three languages.</description>
	</item>
	<item>
		<title>Obtaining Alfresco Web Content Management</title>
		<link>http://tc.eserver.org/34578.html</link>
		<guid>http://tc.eserver.org/34578.html</guid>
		<description>In this article you looked at a simple application of Alfresco to create a web project and define web forms using XML Schema to allow non-technical users to create content.</description>
	</item>
	<item>
		<title>Components, Patterns, and Frameworks! Oh My!</title>
		<link>http://tc.eserver.org/34562.html</link>
		<guid>http://tc.eserver.org/34562.html</guid>
		<description>In our research, we&apos;ve found that teams that build out a re-use strategy see tangible benefits: They are more likely to get a completed design sooner, with all the little nuances and details that make for a great experience. Their designs are more likely to meet users expectations by behaving consistently across the entire functionality. Plus, the teams iterate faster (always a good thing), giving them a chance to play with the design while it&apos;s still malleable.</description>
	</item>
	<item>
		<title>Hunkering: Putting Disorientation into the Design Process</title>
		<link>http://tc.eserver.org/34565.html</link>
		<guid>http://tc.eserver.org/34565.html</guid>
		<description>After talking to several dozen craftspeople about why they hunker, we think we have a pretty good idea what&apos;s happening here. As they&apos;re building their design, they have a solid picture in their mind of what they are creating. However, when they put the physical pieces into the basic form, things aren&apos;t quite right.&#xD;&#xD;In essence, it&apos;s disorienting. Once the craftsperson has disoriented themself, they go through a process of reconciliation. Either the work-in-progress needs correction or the design in their head needs adjustment.</description>
	</item>
	<item>
		<title>Eight Liberating Strategies for Clearing the Queues in Your Life</title>
		<link>http://tc.eserver.org/34555.html</link>
		<guid>http://tc.eserver.org/34555.html</guid>
		<description>Our lives are filled with queues, from email inboxes to your to-do lists to voice and text messages to a variety of different inboxes in social networks. For many people, managing all these queues is stressful, never-ending, and complex. Let’s look at how to simplify things, how to clear your queues, and how to let go of the stress of managing them all.</description>
	</item>
	<item>
		<title>Guidelines for Conducting Effective and Efficient Meetings</title>
		<link>http://tc.eserver.org/34505.html</link>
		<guid>http://tc.eserver.org/34505.html</guid>
		<description>This article puts forth a simple process that you can utilize for conducting effective and efficient meetings (where you work in a framework that aims at accomplishing the goal of the meeting and time is well utilized) at your organization.</description>
	</item>
	<item>
		<title>Five Ways to Reduce Costs With User Centred Design</title>
		<link>http://tc.eserver.org/34458.html</link>
		<guid>http://tc.eserver.org/34458.html</guid>
		<description>User centred design can be a useful and speedy way of increasing efficiency and hence reducing costs. More often that not, design is seen as a way of increasing sales, attracting eyeballs or retaining customers. However at Frontend we&apos;ve noticed that some of our most successful projects concentrate on cost-reduction and business efficiency. Here&apos;s a few ways we&apos;ve used user centred design to help our clients save money.</description>
	</item>
	<item>
		<title>Follow the Recipe</title>
		<link>http://tc.eserver.org/34469.html</link>
		<guid>http://tc.eserver.org/34469.html</guid>
		<description>Following a software design process can offer the same kinds of benefits you gain from following a recipe when cooking: getting reliable results. For example, if I have a recipe for gingerbread, but I don’t follow the recipe, should I still expect to get gingerbread? It depends, of course, on how much I choose to deviate from the recipe.</description>
	</item>
	<item>
		<title>How to Run a Successful DITA Pilot Project</title>
		<link>http://tc.eserver.org/34422.html</link>
		<guid>http://tc.eserver.org/34422.html</guid>
		<description>How do you mitigate the risk of a major technology change such as DITA? This presentation shares lessons learned in the first DITA pilot project at IBM Internet Security Systems. How to pick the right opportunity for a user assistance pilot project. How to specify appropriate proof-of-concept requirements. How to use a wiki and collaborative walkthroughs to transfer knowledge and set standards.</description>
	</item>
	<item>
		<title>Writing Quality Requirements</title>
		<link>http://tc.eserver.org/34276.html</link>
		<guid>http://tc.eserver.org/34276.html</guid>
		<description>This article describes several characteristics of high quality software requirement statements and specifications. We will examine some less-than-perfect requirements from these perspectives and take a stab at rewriting them. I’ve also included some general tips on how to write good requirements. You might want to evaluate your own project’s requirements against these quality criteria.</description>
	</item>
	<item>
		<title>Introduction to Requirements: The Critical Details That Make or Break a Project</title>
		<link>http://tc.eserver.org/34277.html</link>
		<guid>http://tc.eserver.org/34277.html</guid>
		<description>Every project has requirements. It doesn&apos;t matter if it&apos;s building hardware solutions, developing software solutions, installing networks, protecting data, or training users. For the project to be a success, knowing what the requirements are is an absolute must.&#xD;&#xD;Requirements exist for virtually any components of a project or task. For example, a project may require specific methods, expertise levels of personnel, or the format of deliverables. This whitepaper will discuss the various kinds of information technology requirements, their importance, the different requirement types, the concept of requirements engineering, and the process for gathering requirements.</description>
	</item>
	<item>
		<title>Finding Solutions by Being Aware of the Way You Think</title>
		<link>http://tc.eserver.org/34278.html</link>
		<guid>http://tc.eserver.org/34278.html</guid>
		<description>It is the task of the project manager to be aware of the larger environment in which a project is operating. One approach that helps achieve this insight is systems thinking.</description>
	</item>
	<item>
		<title>How to Talk to Your Boss about Social Media (So She’ll Approve the Budget)</title>
		<link>http://tc.eserver.org/34232.html</link>
		<guid>http://tc.eserver.org/34232.html</guid>
		<description>The use of social media for business is certainly a hot topic. For today’s post, Comet Branding’s new partner, Sara Meaney shares her first Comet Branding Blog post with us and dives into the big question on many people’s minds - “How do I convince with my boss that social media is right for our company?”</description>
	</item>
	<item>
		<title>Differentiating Your Design: A Visual Approach to Competitive Reviews</title>
		<link>http://tc.eserver.org/34234.html</link>
		<guid>http://tc.eserver.org/34234.html</guid>
		<description>A common activity at the outset of many design projects is a competitive review. As a designer, when you encounter a design problem, it’s a natural instinct to try to understand what others are doing to solve the same or similar problems. However, like other design-related activities, if you start a competitive review without a clear purpose and strategy for the activity, doing the review may not be productive.</description>
	</item>
	<item>
		<title>Successful Project Management: Using Time Management Tools</title>
		<link>http://tc.eserver.org/34094.html</link>
		<guid>http://tc.eserver.org/34094.html</guid>
		<description>In this introductory column, I’ll discuss time management and some ways in which you can use quick-reference sheets and project-management tools to help you maintain some semblance of sanity in your busy life.</description>
	</item>
	<item>
		<title>XML Project Management Best Practices</title>
		<link>http://tc.eserver.org/33978.html</link>
		<guid>http://tc.eserver.org/33978.html</guid>
		<description>Three panellists talk about the challenges of managing an XML publishing and documentation project. After brief introductory remarks from each speaker, there will be a general discussion with the audience about the challenges of XML project management in the publishing world.</description>
	</item>
	<item>
		<title>Getting Real About Agile Design</title>
		<link>http://tc.eserver.org/33640.html</link>
		<guid>http://tc.eserver.org/33640.html</guid>
		<description>Agile is here to stay. The economic difficulties of the past months have finally put waterfall out of its misery; now more than ever, long requirements phases and vaporous up-front documentation aren’t acceptable. Software must be visible and valuable from the start.&#xD;&#xD;For many designers, Agile is already a fact of life (and for those less accustomed, some recommended reading follows at the foot of this article). We are reaching the point where we must either acclimatize or risk being bypassed. The good news is that Agile does allow us to still do the things we hold dear—research, develop a vision, and test and improve our designs—we just need new techniques. Now is the time to get real, and prove design can adapt, if we want to stay relevant in these increasingly unreal times.</description>
	</item>
	<item>
		<title>When Trust Becomes a Characteristic Flaw in a Project</title>
		<link>http://tc.eserver.org/33551.html</link>
		<guid>http://tc.eserver.org/33551.html</guid>
		<description>As hard as it may seem, lesson one of technical writing is to break the rules and contact the end user. Conduct a mini-ethnography. Sit with the users. Call them on the phone. Send them emails. Do not let it get to the point where you feel you must go through the PM to communicate with the end user. As hard and uncomfortable as it may be, the consequences of not talking to the end user can be crippling to your help.</description>
	</item>
	<item>
		<title>Project Management, Critical Praxis, and Process-Oriented Approach to Teamwork</title>
		<link>http://tc.eserver.org/33552.html</link>
		<guid>http://tc.eserver.org/33552.html</guid>
		<description>To help alleviate issues of free-riding and conflicts in team projects, this study proposes the systematic incorporation of project management methods to introduce a process-oriented approach to and a critical praxis in team projects. We examined how the systematic use of project management methods influenced students&apos; performance in team projects. The findings demonstrate that such an approach enables the documentation and evaluation of and reflection on both individual and team work. Our findings indicate that project management tools enhance team member accountability and help reduce free-riding.</description>
	</item>
	<item>
		<title>The UX Designer’s Place in the Ensemble: Directing the Vision</title>
		<link>http://tc.eserver.org/33482.html</link>
		<guid>http://tc.eserver.org/33482.html</guid>
		<description>What does directing have to do with creating a user interface design? Well, we know a director is responsible for the strategic vision of creative work. That’s a given. But, did you know he is also responsible for ensuring a successful outcome that both meets his vision and is in line with the producer’s desires and budget? To make that happen, a director works with the cast, crew, costume and set designers, and everyone else who contributes to a successful theatrical production to pull together a cohesive product, without losing site of his vision. It’s a complicated job.</description>
	</item>
	<item>
		<title>Setting Priorities</title>
		<link>http://tc.eserver.org/33490.html</link>
		<guid>http://tc.eserver.org/33490.html</guid>
		<description>Nearly every company I’ve worked with since becoming a web professional six years ago has lacked an efficient way to decide which things to do first. Put 10 people into a room for an hour, and they’ll surely come up with a wish list a mile long.</description>
	</item>
	<item>
		<title>Agile Development Projects and Usability</title>
		<link>http://tc.eserver.org/33454.html</link>
		<guid>http://tc.eserver.org/33454.html</guid>
		<description>Agile methods aim to overcome usability barriers in traditional development, but pose new threats to user experience quality. By modifying Agile approaches, however, many companies have realized the benefits without the pain.</description>
	</item>
	<item>
		<title>God and the Technical Writer</title>
		<link>http://tc.eserver.org/33393.html</link>
		<guid>http://tc.eserver.org/33393.html</guid>
		<description>A short play featuring the God of Software (played by the Product Manager) and the Technical Writer (played by a technical writer).</description>
	</item>
	<item>
		<title>Twenty Signs You Don’t Want that Web Design Project</title>
		<link>http://tc.eserver.org/33342.html</link>
		<guid>http://tc.eserver.org/33342.html</guid>
		<description>Most clients are good clients, and some clients are great clients. But some jobs are just never going to work out well. Herewith, a few indicators that a project may be headed to the toilet.</description>
	</item>
	<item>
		<title>Ten Rules for Project Managers</title>
		<link>http://tc.eserver.org/33349.html</link>
		<guid>http://tc.eserver.org/33349.html</guid>
		<description>In his Weblog, operations management consultant Hal Macomber derides those x-numbered lists of qualities that consultants turn into overpuffed business books. He does, however, have a more-than-usually useful list of his own: 10 Rules for Project Managers.</description>
	</item>
	<item>
		<title>Early and Often: How to Avoid the Design Revision Death Spiral</title>
		<link>http://tc.eserver.org/33364.html</link>
		<guid>http://tc.eserver.org/33364.html</guid>
		<description>A critical component to the success of an interaction design project is close collaboration with clients or stakeholders. Without careful planning and structure this type of collaboration can turn into a significant barrier to project success. Dave Cronin&apos;s article, originally presented at the DUX 2005 design conference, discusses the strategies and methods Cooper has adopted to get maximum benefit as a consultancy from clients&apos; feedback and expertise while maintaining creative momentum and achieving deadlines.</description>
	</item>
	<item>
		<title>You Need a Five-Year Plan for Your Website</title>
		<link>http://tc.eserver.org/33279.html</link>
		<guid>http://tc.eserver.org/33279.html</guid>
		<description>Websites change the way an organization communicates with its staff, customers, investors and general public. A change in communication is a major shift for the organization. To effectively implement such a change will take time. You need a five-year plan for your website.</description>
	</item>
	<item>
		<title>Web Content Management a Process, Not a Project</title>
		<link>http://tc.eserver.org/33280.html</link>
		<guid>http://tc.eserver.org/33280.html</guid>
		<description>When something is new, we need to approach it in an exploratory manner. We need to experiment and try things out. And so it has been with the Web. That period is now over. We need to move from seeing our websites as a series of projects, to managing them as a well-planned process.</description>
	</item>
	<item>
		<title>My Tip for Productivity: Tear Up the To-Do List</title>
		<link>http://tc.eserver.org/33287.html</link>
		<guid>http://tc.eserver.org/33287.html</guid>
		<description>We all lead extremely busy lives. We have goals, commitments, and an almost endless amount of tasks to complete. Are there any productivity tips that work for you?</description>
	</item>
	<item>
		<title>Deconstructing the Design Process</title>
		<link>http://tc.eserver.org/33213.html</link>
		<guid>http://tc.eserver.org/33213.html</guid>
		<description>The way to overcome the pressure of a new design is by breaking the process into smaller parts, and defining a step by step strategy that allows you to address each issue of the design separately rather than as a daunting whole. Instead of one monolithic problem, you have lots of small, more manageable problems. Breaking each problem out will also help you arrive at better design results as you will have given close consideration to all aspects of the problem.</description>
	</item>
	<item>
		<title>Electronic Document and Records Management System Implementation Toolkit</title>
		<link>http://tc.eserver.org/33215.html</link>
		<guid>http://tc.eserver.org/33215.html</guid>
		<description>he objective of this toolkit is to provide institutional Records Managers and other information professionals with a &apos;one-stop shop&apos; for impartial, detailed and practical advice of use during all the stages of a proposed or actual EDRM system implementation that is free from vendor bias and specific to the needs of the FE/HE sector.&#xD;&#xD;This toolkit represents an attempt to synthesise some twenty years of experience of assisting public sector organisations to define their requirements for Electronic Document and Records Management solutions plus all the data gathered from some four months of fact finding in the further and higher education sector.</description>
	</item>
	<item>
		<title>Your Website is for Your Most Important Customers</title>
		<link>http://tc.eserver.org/33162.html</link>
		<guid>http://tc.eserver.org/33162.html</guid>
		<description>Well-managed websites tend to be those that are narrow in their focus. They do a few things really well rather than attempt to do lots and lots of things.</description>
	</item>
	<item>
		<title>How to Scope an Intranet Release</title>
		<link>http://tc.eserver.org/33058.html</link>
		<guid>http://tc.eserver.org/33058.html</guid>
		<description>When developing intranet releases, intranet teams often find themselves very constrained by both time and resources. The challenge then becomes delivering sufficient content and capabilities to meet business and user expectations, within the project constraints. This briefing introduces a simple approach to scoping a release that takes all of these factors into account.</description>
	</item>
	<item>
		<title>Adopting User-Centered Design Within An Agile Process: A Conversation</title>
		<link>http://tc.eserver.org/32997.html</link>
		<guid>http://tc.eserver.org/32997.html</guid>
		<description>eXtreme Programming and other agile processes provide a middle ground between chaos and over-elaborate processes sometimes referred to as &apos;death by documentation&apos;. A particular attrtactive aspect of the agile approach for many teams is its willingness to accomodate change no matter how advanced development might be. However, this very flexibility can cause user interface design issues and ensuing usability problems. Adopting a user-centered approach to user interface design can address these issues, as the following simulated conversation between a user-centered design consultant and an XP team leader will explain.</description>
	</item>
	<item>
		<title>An Eight-Step Implementation Model</title>
		<link>http://tc.eserver.org/32879.html</link>
		<guid>http://tc.eserver.org/32879.html</guid>
		<description>The inaccessibility of web content can have a significant impact on the lives of individuals with disabilities. Many people without disabilities are ignorant of the importance of the issue to those who are directly affected. They are also often ignorant of the tremendous benefit that accessible web content can be. Accessible web sites offer independence to individuals with disabilities that would otherwise not have it.</description>
	</item>
	<item>
		<title>The KJ-Technique: A Group Process for Establishing Priorities</title>
		<link>http://tc.eserver.org/32923.html</link>
		<guid>http://tc.eserver.org/32923.html</guid>
		<description>In design, our resources are limited. Priorities become a necessity. We need to ensure we are working on the most important parts of the problem. How do we assess what is most important?</description>
	</item>
	<item>
		<title>Feature Presentation</title>
		<link>http://tc.eserver.org/32790.html</link>
		<guid>http://tc.eserver.org/32790.html</guid>
		<description>A spiral of complexity, often called “feature creep,” costs consumers time, but it also costs businesses money. Product returns in the U.S. cost a hundred billion dollars a year, and a recent study by Elke den Ouden, of Philips Electronics, found that at least half of returned products have nothing wrong with them. Consumers just couldn’t figure out how to use them. Companies now know a great deal about problems of usability and consumer behavior, so why is it that feature creep proves unstoppable?</description>
	</item>
	<item>
		<title>Where Design Really Fits</title>
		<link>http://tc.eserver.org/32724.html</link>
		<guid>http://tc.eserver.org/32724.html</guid>
		<description>As a designer, do you know where your work really fits in the process of design? If Web design is your business, then you must make certain you are in the right mindset and you use the right process when it comes to your work. You don&apos;t want your designs to fail, but, unfortunately, there is a strong chance that they will do exactly that. Lets take a step back for a minute and define what a failing design is, and why it fails.</description>
	</item>
	<item>
		<title>Ten Ways to Save Money When Publishing a Manual</title>
		<link>http://tc.eserver.org/32691.html</link>
		<guid>http://tc.eserver.org/32691.html</guid>
		<description>Several hints on how to produce professional documentation less expensively.</description>
	</item>
	<item>
		<title>Why Do Web Startups Die? Lack of Alphalpha</title>
		<link>http://tc.eserver.org/32646.html</link>
		<guid>http://tc.eserver.org/32646.html</guid>
		<description>Internet startups are generally as successful as a nerd in a singles bar. Ventures that get off the ground rarely get knee-high. Why?    You don’t need a deckful of scatter charts to do this, but you do need the willingness to make some difficult decisions now—and stick to them later.The biggest problem I’ve seen isn’t lack of talent, enthusiasm or even funding. It lies in skipping a critical early stage of development I call the “alpha-alpha” stage, or “alphalpha” for short.</description>
	</item>
	<item>
		<title>Technical Communication Outsourcing: The Twelve Driver Framework Tutorial</title>
		<link>http://tc.eserver.org/32374.html</link>
		<guid>http://tc.eserver.org/32374.html</guid>
		<description>Almost all IT, engineering research, financial analysis, and manufacturing industries are confronted with a question: to outsource or not? The outsourcing and offshoring trend is inspired by success stories of huge cost savings, decreased time-to-market, and better quality. Simultaneously, outsourcing-gone-bad stories highlight how hidden costs exceed benefits, cross-cultural problems impact quality, and intellectual property risks shadow project lifecycles. Managers in companies are presented with a confusing picture for which there are no easy answers. Companies, vendors, and policymakers need a framework to understand the outsourcing phenomenon and plan implementation strategies for outsourced projects. At present, many companies go with the gut based on the experience of others and media reports. But very rarely are two technical documentation tasks alike and never are the concerns of two technical communication tasks the same. This tutorial presents the twelve driver framework and the driver-model percentage matrix to assess the benefits and risks of outsourcing a technical communication task. In the end, qualitative decision-making will determine an organization&apos;s decision about outsourcing, but the use of such a framework and related metrics will greatly enhance the quality of the final choice.</description>
	</item>
	<item>
		<title>The Myth of Multitasking</title>
		<link>http://tc.eserver.org/32354.html</link>
		<guid>http://tc.eserver.org/32354.html</guid>
		<description>Today, our collective will to pay attention seems fairly weak. We require advice books to teach us how to avoid distraction. In the not-too-distant future we may even employ new devices to help us overcome the unintended attention deficits created by today’s gadgets.</description>
	</item>
	<item>
		<title>If You Want Something Done, Ask a Busy Person</title>
		<link>http://tc.eserver.org/32313.html</link>
		<guid>http://tc.eserver.org/32313.html</guid>
		<description>Effective use of personal time management skills and techniques can ensure a successful balance between work and personal life. This article suggests ways of analysing how time is spent, and offers advice on making plans for the future in a business and personal environment.</description>
	</item>
	<item>
		<title>When Good Projects Go Bad</title>
		<link>http://tc.eserver.org/32255.html</link>
		<guid>http://tc.eserver.org/32255.html</guid>
		<description>Learn how to recognize and address problems in a project before it is too late.</description>
	</item>
	<item>
		<title>Look at it Another Way</title>
		<link>http://tc.eserver.org/32237.html</link>
		<guid>http://tc.eserver.org/32237.html</guid>
		<description>Seeing the same thing from different perspectives is much praised but little practiced. We don’t often realize what we can gain by seeing another scene in the picture.</description>
	</item>
	<item>
		<title>The Business Analyst in Model-Driven Architecture</title>
		<link>http://tc.eserver.org/32243.html</link>
		<guid>http://tc.eserver.org/32243.html</guid>
		<description>From a software development viewpoint, model-driven architecture (MDA) encourages efficient use of system models. It also encourages reusing best practices as families of systems are produced. One of the main aims of MDA is to separate design from architecture, which places the business analyst in a unique and potentially powerful position within the organization. Learn how you as a business analyst can take an active role in this type of architecture.</description>
	</item>
	<item>
		<title>Requirements Planning: Overlooked and Undervalued</title>
		<link>http://tc.eserver.org/32244.html</link>
		<guid>http://tc.eserver.org/32244.html</guid>
		<description>This article takes a high-level look at project requirements and the requirements cycle to help you understand the role of the business analyst in requirements planning.</description>
	</item>
	<item>
		<title>Why Technical Publishing Shouldn&apos;t Be Art</title>
		<link>http://tc.eserver.org/32174.html</link>
		<guid>http://tc.eserver.org/32174.html</guid>
		<description>The work may start with the author, but to get it from the author to the end reader means it also has to go through an editor, copy editor, book designer, typesetter, printer, sales and marketing team, distributor, book buyer, and, eventually, a retail store.</description>
	</item>
	<item>
		<title>Topic-Based Writing to the Rescue: Project Considerations for Managers</title>
		<link>http://tc.eserver.org/32176.html</link>
		<guid>http://tc.eserver.org/32176.html</guid>
		<description>The purpose of this case study is neither to simply rehash the project nor to provide a pressure-cooker story that others can use as a comparative benchmark. This article looks at the decision points within the project and provides an analysis from a real-life, practical approach that other technical communication managers can use when called upon to engage in a rescue project of their own.</description>
	</item>
	<item>
		<title>Managing the Change Most Forget</title>
		<link>http://tc.eserver.org/32199.html</link>
		<guid>http://tc.eserver.org/32199.html</guid>
		<description>Unless your organization is large enough to support dedicated organizational development and/or performance specialists, you will need to bring in a consultant to help you manage the real change. The change most people forget about, until it’s too late.</description>
	</item>
	<item>
		<title>Herding Chickens: Innovative Techniques for Project Management</title>
		<link>http://tc.eserver.org/32124.html</link>
		<guid>http://tc.eserver.org/32124.html</guid>
		<description>Herding Chickens: Innovative Techniques for Project Management is a different take on managing people and projects. Although the authors do pay homage to The Project Management Body of Knowledge (PMBOK), published by the Project Management Institute, you will not in any way confuse their ideas and tips with the approach you find in the PMBOK.</description>
	</item>
	<item>
		<title>Ten Ways to Speed Up Website Building</title>
		<link>http://tc.eserver.org/32053.html</link>
		<guid>http://tc.eserver.org/32053.html</guid>
		<description>As a freelance web developer, time is money. I use many different tricks to increase my productivity and these are my top selections for saving time.</description>
	</item>
	<item>
		<title>Conducting Effective Team Technical Reviews</title>
		<link>http://tc.eserver.org/31975.html</link>
		<guid>http://tc.eserver.org/31975.html</guid>
		<description>Mention team technical reviews to a group of tech writers and chances are good that you will either get a loud, collective groan, or the group will vie to tell the best review horror story. On the one hand, technical reviews are a vital part of our jobs because they help us to produce high quality product documents. On the other hand, technical reviews gone wrong are the bane of our existence. The good news is that we have the power to conduct consistently effective technical reviews.&#xD;&#xD;This article summarizes why we do reviews and what often goes wrong in reviews, and then summarizes steps to take before, during, and after technical reviews that can help you conduct effective team technical reviews. Although your process and team may differ from what&apos;s described here, you can apply the information in part or in whole to improve your current review process.</description>
	</item>
	<item>
		<title>Why Content Management Projects Fail: Interview with Rahel Bailie</title>
		<link>http://tc.eserver.org/31896.html</link>
		<guid>http://tc.eserver.org/31896.html</guid>
		<description>Many content management projects fail because organizations are either too focused on tools before properly researching their needs and processes, or because they underestimate the difficulty of migrating and restructuring their content to fit the new content management system.&#xD;&#xD;In this podcast, Rahel Bailie explains these pitfalls and what companies can do to avoid them, as well as how companies can climb out of problems they’re currently in. Rahel also talks about how technical communicators can influence business executives and other key stakeholders to make better decisions about content management.</description>
	</item>
	<item>
		<title>Why Writing Deadlines May Be (Almost) As Good As Money</title>
		<link>http://tc.eserver.org/31902.html</link>
		<guid>http://tc.eserver.org/31902.html</guid>
		<description>As much as we all like and/or need money, getting paid may not be enough to keep a writer motivated. Deadlines often are just as important. Although some of us fear — or even hate — them, the truth is that without them many of us simply wouldn’t write anything. And you can count me among those many.</description>
	</item>
	<item>
		<title>Be Productive When a Project Stalls</title>
		<link>http://tc.eserver.org/31849.html</link>
		<guid>http://tc.eserver.org/31849.html</guid>
		<description>With more and more companies adopting the Darwin Information Typing Architecture, Baril discusses how to choose a compatible content management system that also supports your company&apos;s processes. </description>
	</item>
	<item>
		<title>Project Management for Creative Teams: Art and Science</title>
		<link>http://tc.eserver.org/31853.html</link>
		<guid>http://tc.eserver.org/31853.html</guid>
		<description>The definition of a Project Manager varies widely, especially in the creative fields. Like the approaches and outcomes of a creative project, the team member’s project roles —including the project manager’s — change from one project to the next and from one firm to another. The purpose of this essay is to explore the practice of project management specifically in regards to working with creative teams and their specific needs and challenges.</description>
	</item>
	<item>
		<title>Making the Case for Explicit Documentation Requirements</title>
		<link>http://tc.eserver.org/31832.html</link>
		<guid>http://tc.eserver.org/31832.html</guid>
		<description>Clearly defined documentation requirements are instrumental in ensuring the appropriate documents are created accurately and in a timely manner. This article will make a case for using explicit documentation requirements and will recommend a method for putting it into practice.</description>
	</item>
	<item>
		<title>Gantt to Glory: Evolving from Project Management to Successful Web Operations</title>
		<link>http://tc.eserver.org/31745.html</link>
		<guid>http://tc.eserver.org/31745.html</guid>
		<description>Is the sheer possession of a PMP intended to be the Holy Grail of successful web projects, known to fail at a startling rate, or simply a way to divorce oneself from whatever outcome may result from the web project?</description>
	</item>
	<item>
		<title>Paradigm Shifts are Never Pretty: Advice on Making the Move to XML Authoring</title>
		<link>http://tc.eserver.org/31742.html</link>
		<guid>http://tc.eserver.org/31742.html</guid>
		<description>Most people are risk-averse, and profound changes such as the move to structured authoring require new skills and workflows. To ensure a successful transition, XML implementers need to assess their team members, identify allies, and build their implementation strategy around the staff members who embrace change. </description>
	</item>
	<item>
		<title>It&apos;s In the Numbers: Using Metrics to Plan Documentation Projects</title>
		<link>http://tc.eserver.org/31715.html</link>
		<guid>http://tc.eserver.org/31715.html</guid>
		<description>It&apos;s in the numbers. Creating documentation is not an exact science, yet as communication leaders, we are expected to provide real estimates for how much time we need to document a project, or what we can produce given a predetermined timeline.</description>
	</item>
	<item>
		<title>A Structured Approach to Selling</title>
		<link>http://tc.eserver.org/31670.html</link>
		<guid>http://tc.eserver.org/31670.html</guid>
		<description>High-value goods and services are not impulse purchases. Both the purchaser and vendor may need to invest significant time in the purchasing process. When I first started working for myself, I wasted much time. Now I make the process as efficient as possible, both for myself, and for enquirers.</description>
	</item>
	<item>
		<title>Why Did You Hire Me?</title>
		<link>http://tc.eserver.org/31616.html</link>
		<guid>http://tc.eserver.org/31616.html</guid>
		<description>Remembering why you were hired—and identifying whether or not you belong—is just as important as getting the gig. To sustain career and mental health, you must work within your means and know how to navigate ambiguous workplace situations. Using client and project management techniques is one part of the solution. Using your talent is the other.</description>
	</item>
	<item>
		<title>Everything in Moderation: Using Content Units to Manage UX</title>
		<link>http://tc.eserver.org/31598.html</link>
		<guid>http://tc.eserver.org/31598.html</guid>
		<description>I’ve found that separating client requests into content units removes uncertainty and offers clearer direction, while helping your client recognize each individual request as a deliverable, requiring assignments and responsibilities. To do this, I follow a four-step process that helps delineate what content units each section of a Web site must cover—as opposed to content that acts as filler, or filler units.</description>
	</item>
	<item>
		<title>Laws of Web Site Management and Digital Branding</title>
		<link>http://tc.eserver.org/31508.html</link>
		<guid>http://tc.eserver.org/31508.html</guid>
		<description>We urgently need a quick crash course on web site management; otherwise, connecting with potential customers will become a very tough challenge. Lucky are those who have a unique domain name without the additional baggage of extraneous language, numbers, dashes or slashes. Studies have shown that 90 percent of business names are problematic. These problems are serious issues for achieving higher visibility. </description>
	</item>
	<item>
		<title>Ten Tips for Managing a Successful Web Redesign</title>
		<link>http://tc.eserver.org/31507.html</link>
		<guid>http://tc.eserver.org/31507.html</guid>
		<description>Processes evolve. Over time and several redesigns, a few points screamed to be kept in mind: communicate with the client, be scalable, plan to plan, test your assumptions, analyze your current site, and so on. We ran these mini-philosophies by industry leaders and newbies alike. The result? Our collection of things to think about evolved into—drum roll, please—10 EXPERT TIPS TO A SUCCESSFUL REDESIGN. Redesign is happening. Address the need. And stay on track while you do it. </description>
	</item>
	<item>
		<title>Agile: What is it Anyway?</title>
		<link>http://tc.eserver.org/31040.html</link>
		<guid>http://tc.eserver.org/31040.html</guid>
		<description>Agile methodologies have had a lot of press in recent years. To listen to some people, agile methodologies are the answer to all the ailments that have ever plagued software development from the beginning of the computer age. But what are they, really? And do they really deliver on that promise? The answer is: (drumroll, please) it depends.</description>
	</item>
	<item>
		<title>Documents That No Project Cannot Be Without</title>
		<link>http://tc.eserver.org/31035.html</link>
		<guid>http://tc.eserver.org/31035.html</guid>
		<description>Short deadlines force project teams to quickly design, test, and release the product with little or no design documentation. If these documents are written, they generally are not well-written and are not comprehensive. The fact of the matter is that most project teams do not have enough staff to design the product, let alone write and manage documentation. This situation creates an ideal opportunity for technical writers to assist the project team in more ways than writing a user guide.</description>
	</item>
	<item>
		<title>Service-Oriented Project Management</title>
		<link>http://tc.eserver.org/30802.html</link>
		<guid>http://tc.eserver.org/30802.html</guid>
		<description>The primary reason most projects fail is because the focus of the execution and the measurement of projects is too narrow and inwardly directed.</description>
	</item>
	<item>
		<title>Good Money After Bad</title>
		<link>http://tc.eserver.org/30581.html</link>
		<guid>http://tc.eserver.org/30581.html</guid>
		<description>Many software projects that suffer a lingering death should have been canceled much earlier. Although it is hard to pull the plug on a project with a weak business case, failing to do so does throw good money after bad. Karl Wiegers gives some tips on decision making that can help you avoid this outcome. Karl also shows how to use decision points to keep a good project moving along.</description>
	</item>
	<item>
		<title>When Requirements Collide</title>
		<link>http://tc.eserver.org/30582.html</link>
		<guid>http://tc.eserver.org/30582.html</guid>
		<description>Could it be that not every set of business requirements has the customer&apos;s best interest in mind? Karl Wiegers had always believed that implemented software functionality should enable users to accomplish their goals and help the business achieve its objectives. But a recent experience with a less-than-helpful parking meter system suggested to him that conflicts sometimes might exist between business and user requirements.</description>
	</item>
	<item>
		<title>Project and Quality Management for Beginners</title>
		<link>http://tc.eserver.org/30545.html</link>
		<guid>http://tc.eserver.org/30545.html</guid>
		<description>This discussion is intended for people who have recently assumed project management responsibilities (or want to). Project and quality management is about developing a plan, working the plan, and evaluating the results.</description>
	</item>
	<item>
		<title>Project Management for Writers</title>
		<link>http://tc.eserver.org/30546.html</link>
		<guid>http://tc.eserver.org/30546.html</guid>
		<description>Project management skills are part of every writer&apos;s life, in some form or another. However, the more you use these skills to manage your daily work, the more you will grow as a writer. Estimating, controlling scope, and tracking your progress are all part of delivering the product that your &quot;customer&quot; wants. Your primary tool is your documentation plan. In this workshop, we will discuss why these processes are important to you and how to implement them on your job.</description>
	</item>
	<item>
		<title>Publications Project Management A Toolkit for Overcoming Common Pitfalls</title>
		<link>http://tc.eserver.org/30549.html</link>
		<guid>http://tc.eserver.org/30549.html</guid>
		<description>Traditional project management &apos;science&apos; and generic tools rarely match the unique needs of publications projects. The high-degree of human interaction and creativity involved in publication projects makes managing them more and than a science. This discussion/demonstration focuses on the unique challenges involved in managing publications projects and common pitfalls to avoid. We explain why we at Comprose, Inc. created the Documentation Blueprint Project Management Toolkit for managing publications projects, and we demonstrate how technical communicators can use these Custom-designed tools to make any publication project run more smoothly -- whether your project involves just one person or twenty.</description>
	</item>
	<item>
		<title>Information Metrics: Keeping Your Writing Projects On Track</title>
		<link>http://tc.eserver.org/30510.html</link>
		<guid>http://tc.eserver.org/30510.html</guid>
		<description>Keeping information metrics for documentation projects gives managers the ability to more accurately estimate future projects. Publications departments can develop their own tools or they can use existing tools to track such things as page size, hours-per-page spent writing, illustrating, editing, and producing manuals; and the dependencies of each manual. This kind of information can help to determine development schedules, show how late changes affect the documentation process, and accurately determine what it will take to complete quality documentation on time and within budget.</description>
	</item>
	<item>
		<title>Managing Your Documentation Monster: Project Management for the 90&apos;s</title>
		<link>http://tc.eserver.org/30521.html</link>
		<guid>http://tc.eserver.org/30521.html</guid>
		<description>If you&apos;ve ever had trouble figuring out what your boss wants or needs, and how to deliver the project in a timely manner, this is the demonstration for you! From a nuts and bolts approach to developing an iron clad project plan, to managing the process and marching the completed project in a timely and professional manner, this demonstration covers a lot of ground in a short time. Tips, tricks, and checklists will be available to each attendee.</description>
	</item>
	<item>
		<title>Hello, My Name is Doug and I&apos;m a Workaholic</title>
		<link>http://tc.eserver.org/30460.html</link>
		<guid>http://tc.eserver.org/30460.html</guid>
		<description>It&apos;s important to be able to distinguish between workaholics and people who are simply wrapped up in their work--either because they enjoy it so much or because, temporarily, they have decided to make it a priority to win a promotion or attain the kind of lifestyle that they want. For a workaholic, work is the end, not the means. While it may bring wealth or power, what matters most is simply working. Just as alcoholics drink because they must--not always because they enjoy it--so a workaholic is addicted to working even when there is no rational reason for doing so.</description>
	</item>
	<item>
		<title>Featuritis (or Creeping Featurism)</title>
		<link>http://tc.eserver.org/30442.html</link>
		<guid>http://tc.eserver.org/30442.html</guid>
		<description>Featuritis or creeping featurism is the tendency for the number of features in a product (usually software product) to rise with each release of the product. What may have been a cohesive and consistent design in the early versions may end up as a patchwork of added features. And with extra features comes extra complexity.</description>
	</item>
	<item>
		<title>How to Present a Business Case for Web Site Investments</title>
		<link>http://tc.eserver.org/30441.html</link>
		<guid>http://tc.eserver.org/30441.html</guid>
		<description>How can you convince others that Web investments are a wise decision in a slow economy?</description>
	</item>
	<item>
		<title>Developing Tools to Manage Projects</title>
		<link>http://tc.eserver.org/30431.html</link>
		<guid>http://tc.eserver.org/30431.html</guid>
		<description>Coordinating the resources and tasks involved in a large documentation development effort requires the ability to gather meaningful project information at critical junctures so that appropriate decisions can be made. Project managers need the right tools to help them make sense out of the sometimes overwhelming and chaotic flow of project activities. When appropriate tools are not available, documentation project managers must adapt and invent to obtain what they need.</description>
	</item>
	<item>
		<title>Fixed Quotes and Broken Promises</title>
		<link>http://tc.eserver.org/30353.html</link>
		<guid>http://tc.eserver.org/30353.html</guid>
		<description>How to tie down the details of a project and protect yourself from unexpected changes that can drag a &apos;peach project&apos; into the &apos;pits of despair and financial ruin.&apos;</description>
	</item>
	<item>
		<title>Control Costs of Translation with Advance Plan</title>
		<link>http://tc.eserver.org/30343.html</link>
		<guid>http://tc.eserver.org/30343.html</guid>
		<description>The liability of a translated manual is several times greater than the English version. This increased liability can be tied directly to the accuracy of the translation.</description>
	</item>
	<item>
		<title>How to Plan On-line and Paper Versions of a Software Manual</title>
		<link>http://tc.eserver.org/30314.html</link>
		<guid>http://tc.eserver.org/30314.html</guid>
		<description>On projects for which you must produce both on-line and paper documentation, there are many things you should consider before you start.</description>
	</item>
	<item>
		<title>The Six Biggest Mistakes Project Managers Make with Documentation and How to Avoid Them</title>
		<link>http://tc.eserver.org/30262.html</link>
		<guid>http://tc.eserver.org/30262.html</guid>
		<description>Professional business writers, such as technical authors, typically break a document down into small, discrete units of information, organised around a skeleton of topic headings. If you use this &apos;component&apos; or &apos;modular&apos; approach, you can plan and structure the document using the heading &apos;labels&apos; that describe each section.</description>
	</item>
	<item>
		<title>Playing to Win: Building a Strategic Plan</title>
		<link>http://tc.eserver.org/30240.html</link>
		<guid>http://tc.eserver.org/30240.html</guid>
		<description>This workshop uses games to provide an overview of strategic planning. The first step in strategic planning is identifying the objectives of your project. Participants play a version of musical chairs to identify and prioritize objectives. The second step is developing a vision of meeting those objectives. Participants play a version of darts. The third step is building the plan that fulfills the vision. Participants play a board game to create the best plan with limited resources.</description>
	</item>
	<item>
		<title>High-Cost Usability Sometimes Makes Sense</title>
		<link>http://tc.eserver.org/30195.html</link>
		<guid>http://tc.eserver.org/30195.html</guid>
		<description>Computing the net present value (NPV) lets you estimate the most profitable level of usability investment. For big projects, expensive usability can pay off.</description>
	</item>
	<item>
		<title>Managing a Large Web Page Project</title>
		<link>http://tc.eserver.org/30166.html</link>
		<guid>http://tc.eserver.org/30166.html</guid>
		<description>Web page projects can be completed in minimal time if you have your team&apos;s buy-in. You need a team leader that finds creative ways to energize the team and has excellent organizational and communication skills. Standards, spreadsheets, and databases, and a knowledgeable technical and creative group provide essential tools to success. But, enthusiasm and synergy are the key components that make the project work, with upper management behind you all the way. Completion of the project finds excellent bonuses for a job well done!</description>
	</item>
	<item>
		<title>Tools and Models for Managing Project</title>
		<link>http://tc.eserver.org/30179.html</link>
		<guid>http://tc.eserver.org/30179.html</guid>
		<description>Project management is as much art as science. But even artists follow recognized approaches to creating their work, and they rely on practical tools to do so. Three elements of project management--regardless ofproject size or scope--will determine success: creative estimating; project planning; and effective tracking. These three elements don&apos;t need to be complex, and they don&apos;t need to be time consuming. Building a standard approach and simple, reusable tools can streamline the project management process with minimal overhead while assuring the necessary control.</description>
	</item>
	<item>
		<title>Effective Project Planning</title>
		<link>http://tc.eserver.org/30147.html</link>
		<guid>http://tc.eserver.org/30147.html</guid>
		<description>Our roles as technical communicators are often dictated to us by other people. Clients come to us after their product has already been developed, saying, &apos;I need a manual,&apos; or &apos;I&apos;ve written the necessary procedures--just make them look nice. &apos; It&apos;s easy to fall into the trap of just doing what we&apos;re told when we&apos;re told to do it.</description>
	</item>
	<item>
		<title>Top Ten Tips for a Successful Content Management Proof-of-Concept</title>
		<link>http://tc.eserver.org/29946.html</link>
		<guid>http://tc.eserver.org/29946.html</guid>
		<description>Are you looking to buy a single-source content management system and want to take it for a test drive? Great idea! Choose your favorite system and do a proof-of-concept. Here are ten tips to prepare for a proof-of-concept and ensure its success.</description>
	</item>
	<item>
		<title>Information Modeling: A Practical Approach</title>
		<link>http://tc.eserver.org/29913.html</link>
		<guid>http://tc.eserver.org/29913.html</guid>
		<description>Information models are a critical component of single sourcing, enterprise content management, and dynamic content management. The information model is your blueprint for the effective writing, structuring, and delivery of reusable content. This session explains how to design information models, including information product models and element models. It also explains the role of metadata and how to effectively design it.</description>
	</item>
	<item>
		<title>Usability Requirements: Making User Satisfaction a Measure of Product Success</title>
		<link>http://tc.eserver.org/29905.html</link>
		<guid>http://tc.eserver.org/29905.html</guid>
		<description>Defining usability requirements at the beginning of the project increases the chances that the end product will meet the users&apos; goals and create a satisfying user experience. Unfortunately, such requirements are often not considered with the same priority as functional or other technical requirements. This presentation defines usability requirements, proposes guidelines for creating measurable requirements, and elaborates the components of a well-constructed usability requirement.</description>
	</item>
	<item>
		<title>WebWorks Publisher In Action: A Project Management Perspective</title>
		<link>http://tc.eserver.org/29910.html</link>
		<guid>http://tc.eserver.org/29910.html</guid>
		<description>From October 2001 through August 2002, a team of two technical authors converted the documentation for a Web Content Management System from a series of static manuals to a single-sourced, dynamically delivered context-sensitive online help/print manual combination. This paper covers the challenges encountered and overcome when resources became more scarce and demands rose. It offers some technical insight in the application of Adobe FrameMaker and WebWorks Publisher Professional to achieve the goal of manageable documentation.</description>
	</item>
	<item>
		<title>Encouraging Innovation in Your Organization</title>
		<link>http://tc.eserver.org/29772.html</link>
		<guid>http://tc.eserver.org/29772.html</guid>
		<description>In today&apos;s environment we often find ourselves drowning in our work. We don&apos;t take the time to stop and assess what we are doing. Are there better ways to do what we do? Are we making the biggest and best contribution we can make? Can you manage innovation? This paper will discuss the importance of innovation and one method we used to drive innovation.</description>
	</item>
	<item>
		<title>Avoiding Client/Contractor Nightmares: Best Practices for Contractor Management</title>
		<link>http://tc.eserver.org/29739.html</link>
		<guid>http://tc.eserver.org/29739.html</guid>
		<description>You&apos;ve secured the budget to produce some badly needed, high visibility deliverables. Part of that budget includes funding for contractors. To help manage and guide the communications between your contractors, your staff, and your management, you want to use your company&apos;s best practices.  The best practices of the contractor or provider firm you employ should closely match your own company&apos;s best practices. Beginning on the &quot;same page&quot; will eliminate headaches and expenses during the lifecycle of the project. A quick comparison of practices and procedures enables you to proceed with the project confident that you are using competent outside resources.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Project-Management.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>