Project Management is the discipline of planning, organizing, and managing resources to bring about the successful completion of specific project goals and objectives.
Laws of Web Site Management and Digital Branding
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.
Javed, Naseem. Communication World Bulletin (2004). Articles>Web Design>Project Management>Marketing
Lean Interaction Design and Implementation
Lean UI development in Feature Driven Development is achieved through right-first-time implementation of the interaction designer's intent using David Harel's Statechart notation to model the interaction design.
Anderson, David J. UIdesign (2003). Design>Web Design>Project Management>Interaction Design
Lessons Learned the Hard Way in an Architectural Document Disaster 
Delivering project reports in radically different formats gave the client a bad impression of this consulting firm. Here's how the staff remedied the situation and learned from their mistake.
Kalvar, Shannon T. TechRepublic (2003). Careers>Consulting>Project Management>Reports
Review: Life in the New Work Order, or What Was I Doing Reading Death March? 
So what is there in this book for the technical writer? There is some obvious advice, such as don't enforce a process that gets in the way of reaching goals; and don't try out radically new tools on this project. There is also good advice that most of us would take years to discover on our own, about the high-level politics that might help the project and some strategies to try during negotiation. If you are managing a group, it also gives some ideas on the different social roles that every team seems to need.
Lizak, Samantha. TECHWR-L (2004). Articles>Reviews>Project Management
Long-Distance Teams: Facing the Challenges 
Offers advice for managers of long-distance teams on working across time zones, accommodating team members' cultural norms, easing the difficulties of language differences, and nurturing team spirit.
Legg, Kathy A. Intercom (2004). Articles>Project Management>Collaboration>Online
Making the Case for Explicit Documentation Requirements 
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.
Das, Pradipto. Usability Interface (2008). Articles>Documentation>Project Management
Making Your Design Real: The Form and Behavior Specification
Let's say your development organization has embraced design as a key to creating successful products. You've devoted time and energy to creating the perfect, goal-directed design for your product. Your programmers are ready and eager to start putting that design into code. So…now what? How do you communicate your design to your development team, accurately and in sufficient detail? One approach is to produce a Form & Behavior Specification.
Olshavsky, Ryan. Cooper Interaction Design (2003). Design>Project Management>User Interface
Manage the Document Life Cycle for the Important Documents on Your Project 
Not all documents require a full lifecycle, but if you understand the nature of building documents, you will be better able to plan for the time required to complete them successfully.
Mochal, Tom. TechRepublic (2005). Articles>Project Management>Documentation
Kaizen is a Japanese phrase that means 'continuous improvement' and has long been used by Japanese managers. Find out how to apply this style to your work as a technical communicator and how kaizen can also be used effectively when working in a team.
Gopalakrishnan, Janani. Intercom (2006). Careers>Management>Project Management
Management Methods to Lower Documentation Costs 
Most people who are in charge of technical documentation have a technical background. No wonder that they look to technology for solving their cost problems: databases, content management or translation memory. But the investment costs are high, of course. And it often takes years for such systems to amortise, if at all they do. A business manager would adopt a different approach to solving the problem: without technology and without investments, by setting priorities and by using optimized processes. There are several tried and tested approaches from the domain of business management that have been succesfully used in other departments to deal with very similar problems. This article explains the most important of these methods and gives examples of how they can be applied to technical documentation.
Achtelig, Marc. indoition engineering (2006). Articles>Project Management>Management>Workflow
Managing a Company-Wide Policies and Procedures Project 
It takes skills in three different areas to manage a company-wide policy and procedures project. First, people must be organized and motivated to participate. Executive support is critical here. And the persons actually performing the tasks must be the ones to document it. Second, the project must be clearly defined and tracked. The document creation and review process must be structured simply, to take full advantage of the documentation team’s limited time. Finally, the information published must be accurate and controlled. Work processes should be analyzed before the procedures are documented, and published procedures must be distributed to specified manual holders.
Creps, William B. STC Proceedings (1996). Articles>Project Management>Documentation>Policies and Procedures
Managing a Large Web Page Project 
Web page projects can be completed in minimal time if you have your team'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!
Ricks, Debra. STC Proceedings (1997). Articles>Web Design>Project Management
Managing a team of employees who are located around the world can be challenging. Discover how to efficiently and effectively work to create the highest level of output.
Damrau, Jackie. Intercom (2006). Careers>Management>Project Management>Offshoring
Managing and Documenting Your Project, XML Style
Here are links to the listings described in Managing and Documenting Your Project XML Style.
Fisher, Timothy. XML Journal (2003). Articles>Documentation>Project Management>XML
Risk management is as much art as science. Being aware of what risks are and how they can affect a project can be the difference between success and failure. Three elements of risk management—regardless of project size or scope—will influence success: understanding what risks are; developing and detailing categories of risk; and building a mitigation plan into the project plan. This approach to risk management benefits the project manager by bringing into focus—as early as possible in the project life cycle—many potential detriments to project success. When folded into a repeatable project management methodology, these processes can translate into dollars as the probability of meeting calendar and budget goals increases.
Bierbower, James G. STC Proceedings (1998). Articles>Project Management>Risk Communication
Managing the Monster, Managing the Zoo 
Every technical communicator, whether controlling a single large project or a dozen small ones, must develop a set of management skills appropriate to the task in order to remain a qualified member of the communication team. This calls for being part diplomat, part technical expert, part salesman, and part rhinoceros.
Wise, Daniel E. and Elizabeth Bailey. STC Proceedings (2005). Articles>Project Management>TC
Managing the Monster, Managing the Zoo 
Every technical communicator, whether controlling a single large project or a dozen small ones, must develop a set of management skills appropriate to the task in order to remain a qualified member of the communication team. This calls for being part diplomat, part technical expert, part salesman, and part rhinoceros.
Wise, Daniel E. and Elizabeth Bailey. STC Proceedings (2004). Careers>TC>Project Management
Managing the Monster; Managing the Zoo 
Every technical communicator, whether controlling a single large project or a dozen small ones, must develop a set of management skills appropriate to the task in order to remain a qualified member of the communication team. This calls for being part diplomat, part technical expert, part salesman, and part rhinoceros.
Wise, Daniel E. and Elizabeth Bailey. STC Proceedings (2002). Careers>Project Management
Managing Your Customers' Expectations 
How many customers do you know who deliberately set out to make your life difficult? Not many, I’m sure. They probably don’t anticipate that adding three new chapters to a manual means that the project deadline needs to change or another writer needs to be hired. They may not realize that another round of reviews requires more (billable) hours of work. In most cases, good two-way communication prevents problems in the first place and provides solutions for the unforeseen issues that arise.
Frick, Elizabeth A. 'Betsy'. Intercom (2003). Careers>Business Communication>Project Management
Managing Your Documentation Monster: Project Management for the 90's 
If you'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.
Glick-Smith, Judith L. and Karen A. Steele. STC Proceedings (1993). Articles>Documentation>Project Management
Review: Managing your Documentation Projects

Documentation projects require a significant amount of coordination and planning, and managers often find themselves faced with the challenge of successfully integrating a range of new elements including international legal requirements, new players, budgets and scheduling demands to make a product successful. Most often they look around for solutions to develop an effective strategy for their documentation projects that places control in their hands.
Kudesia, Saurabh. International Journal for Technical Communication (2006). Articles>Reviews>Documentation>Project Management
Managing--and Surviving--A Design Project 
Describes a process for designing documents that establishes clear goals and minimizes disagreements.
Harvey, Patrick. Intercom (2001). Design>Project Management>Collaboration
Acting without planning can be expensive, and because of the potential cost of poorly thought-out actions, we should not only plan, but plan twice.
Hart, Geoffrey J.S. Geoff-Hart.com (2000). Articles>Project Management>Planning>User Centered Design
We are all against bonded labour and slavery. I ask you: are software professionals (including technical writers), better off than slaves and bonded labourers?
Kamath, Gurudutt R. IT People (2003). Articles>Documentation>Project Management
Mission Statements: Why You Might Want One
I recently started a new job. The group I manage is new and all the people on my team have recently been transferred into this group. Additionally, each person has spent a lot of time in the recent past working on individual, solitary projects, and has not regularly been part of a collaborative team.
Malone, Erin. Boxes and Arrows (2004). Careers>Project Management>Writing
There are 11 readers currently online: 1 registered user and 10 guests. Register.

![]()
![]()


![]()
![]()
![]()