<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Web Design&gt;Project Management</title>	<link>http://tc.eserver.org/dir/Articles/Web-Design/Project-Management</link>
	<description>A listing of the most recently indexed works about Articles and Web Design and 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>Articles&gt;Web Design&gt;Project Management</title>
		<link>http://tc.eserver.org/dir/Articles/Web-Design/Project-Management</link>
	</image>
	<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>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>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>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>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>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>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>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>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>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>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>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>Are We There Yet?</title>
		<link>http://tc.eserver.org/28359.html</link>
		<guid>http://tc.eserver.org/28359.html</guid>
		<description>It&apos;s true: even simple projects get messy. Christina Wodtke comes clean on Swiss Army knives, the writing on the wall, and the untidy glory of the Boxes and Arrows redesign contest.</description>
	</item>
	<item>
		<title>Five Questions to Ask Your Web Development Team</title>
		<link>http://tc.eserver.org/27637.html</link>
		<guid>http://tc.eserver.org/27637.html</guid>
		<description>As a client or manager responsible for a web development project you don&apos;t need to know anything about how a standards based web site is created. However you do need to know that your project is addressing these five important issues.</description>
	</item>
	<item>
		<title>Use Cases Part II: Taming Scope</title>
		<link>http://tc.eserver.org/25257.html</link>
		<guid>http://tc.eserver.org/25257.html</guid>
		<description>The use-case model can be a powerful tool for controlling scope throughout a project&apos;s life cycle. Because a simplified use-case model can be understood by all project participants, it can also serve as a framework for ongoing collaboration and a visual map of all agreed-upon functionality. Use it to plan, to negotiate, and to prevent scope creep.</description>
	</item>
	<item>
		<title>What&apos;s the Problem?</title>
		<link>http://tc.eserver.org/25261.html</link>
		<guid>http://tc.eserver.org/25261.html</guid>
		<description>One of the biggest problems in creating and delivering a site is how to decide, specify, and communicate exactly what we’re building and why. Use cases can help answer these questions by providing a simple, fast means to decide and describe the purpose of your project. In this quick-reading article, Messieurs Carr and Meehan introduce use cases and their, uh, uses.</description>
	</item>
	<item>
		<title>Planning a Web Site Redesign in Six Steps</title>
		<link>http://tc.eserver.org/24636.html</link>
		<guid>http://tc.eserver.org/24636.html</guid>
		<description>True Web site redesigns focus on much more than visuals. Brink and Regenold&apos;s redesign process will help technical communicators rethink a site from the ground up.</description>
	</item>
	<item>
		<title>Big Architect, Little Architect</title>
		<link>http://tc.eserver.org/21727.html</link>
		<guid>http://tc.eserver.org/21727.html</guid>
		<description>First came the primordial soup. Thousands of relatively simple single-celled web sites appeared on the scene, and each one was quickly claimed by a multi-functional organism called a &quot;webmaster.&quot;&#xD;&#xD;A symbiotic relationship quickly became apparent. Webmaster fed web site. Web site got bigger and more important. So did the role of the webmaster. Life was good.&#xD;&#xD;Then, bad things started to happen. The size and complexity and importance of the web sites began to spiral out of control. Mutations started cropping up.&#xD;&#xD;Strange new organisms with names like interaction designer, usability engineer, customer experience analyst, and information architect began competing with the webmaster and each other for responsibilities and rewards. Equilibrium had been punctuated and we entered the current era of rapid speciation and specialization.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Web-Design/Project-Management.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>