Project Management is the discipline of planning, organizing, and managing resources to bring about the successful completion of specific project goals and objectives.
#25446
This form shows a generic, fill-in-the-blank evaluation form for small- and medium-sized projects.
Barker, Thomas. Texas Tech University (2004). Academic>Course Materials>Project Management
#29526
Project Management and the Technical Communicator
Describes how project management can help technical communication professionals better plan and manage their technical documentation projects.
McCormick, Greg. SlideShare (2007). Presentations>Project Management>Documentation>Collaboration
#31853
Project Management for Creative Teams: Art and Science
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.
Adaptive Path (2008). Articles>Project Management
#18473
Project Management for Professional Publications 
Managing technical publications—whether they be paper-based, web-based, or any of many electronic forms—requires skills in scheduling, budgeting, managing people, and the like. To that end, the core of the course will prepare the students to assume management roles in various businesses, industries, or governmental agencies.
Warren, Thomas L. Oklahoma State University (2002). Academic>Courses>Management>Project Management
#26065
Project Management for the Technical Communicator
Tasks need to be managed to be completed on time, with available resources to achieve the required result.
Bhatt, Sita Chandrakant. Indus (2005). Articles>Project Management>TC
#30546
Project Management for Writers 
Project management skills are part of every writer'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 "customer" 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.
Yeo, Sarah C. STC Proceedings (1993). Articles>Project Management>Writing
#19519
Project Management in a Home-Based Environment
Acxiom Corporation provides a wide spectrum of data products, data integration services, and mailing list services, as well as data warehousing and decision support services to major firms in the United States and United Kingdom. Effectively supporting the company¡¯s documentation needs requires a project process that keeps work flowing. The Documentation team developed a process consisting of four phases: planning, design, validation, and delivery. This triedand- true process contributes to the success of our home-based team.
McKee, Kimberly and Deborah Lovell. STC Proceedings (1998). Articles>Project Management>TC
#25032
Project Management Professional Certification Handbook
A guide to help people prepare for the project management certification exam administered by PMI.
#20353
Humorous aphorisms about project management.
#28598
A Project Manager's Survival Guide to Going Agile 
When software development project teams move to Agile methodologies, they often leave project managers behind. Traditionally trained project managers are confused as to what their new roles and responsibilities should be in an environment that no longer needs them to make stand-alone decisions. This paper focuses on re-defining the job of project manager to better fit the self-managed team environment, one of the core Agile principles. Special emphasis is placed on the shift to servant leadership, with its focus on facilitation and collaboration. Mapping of PMBOK knowledge areas to Agile practices is discussed at length. After reading this paper, project managers should have a better understanding of what changes they need to make professionally, and how to make these changes in order to survive the transition to an Agile software development approach.
Sliger, Michele. Rally Software Development (2007). Articles>Project Management>Agile
#28609
A Project Manager's Survival Guide to Going Agile
When software development project teams move to Agile methodologies, they often leave project managers behind. Traditionally trained project managers are confused as to what their new roles and responsibilities should be in an environment that no longer needs them to make stand-alone decisions. This presentation focuses on re-defining the job of project manager to better fit the self-managed team environment, one of the core Agile principles. Special emphasis is placed on the shift to servant leadership, with its focus on facilitation and collaboration. Mapping of PMBOK knowledge areas to Agile practices is discussed at length. After reading this paper, project managers should have a better understanding of what changes they need to make professionally, and how to make these changes in order to survive the transition to an Agile software development approach.
Sliger, Michele. Rally Software Development (2006). Presentations>Project Management>Agile
#27562
A Project Manager's Survival Guide to Going Agile
This paper focuses on re-defining the job of project manager to better fit the self-managed team environment, one of the core agile principles. Special emphasis is placed on the shift to servant leadership, with its focus on facilitation and collaboration. Mapping of PMBOK knowledge areas to agile practices is discussed at length. After reading this paper, project managers should have a better understanding of what changes they need to make professionally, and how to make these changes in order to survive the transition to an agile software development approach.
Sliger, Michele. Rally Software Development (2005). Careers>Project Management>Agile>Collaboration
#21773
A template to be completed by the experience design team lead in preparation of or as an attached document to Product Requirements documents. Information should be filled in to give an overview to project team who may be new to the project.
Malone, Erin. AIfIA (2003). Resources>Project Management>Workflow
#10872
A Project Plan for Creating Training Courses 
This link formerly referenced a free Microsoft Project 98 project plan for designing and developing technical courseware. This has been expanded into a 78-page ebook on how to write a successful software training course.
Rice, William H. IV. WilliamRice.com (2004). Books>Education>Project Management>Technical Writing
#24329
Have you ever been involved in a project that was a disaster from beginning to end? What went wrong? What did you learn from those problems? How did you either salvage the project or decide that it couldn’t be saved? These projects are horrible experiences at the time, but they offer many valuable lessons that can help each of us better manage our information development projects in the future.
Hansen, Lauren Y., Ruth T. Glaser, George F. Hayhoe and Sheila C. Jones. STC Proceedings (1998). Careers>Project Management>Workflow
#21260
Proposal Production: Creating Calm Amid the Chaos
The production of a winning business proposal can be a tough and trying time for all involved. But with the use of some simple tools, strategic up-front planning, and effective management techniques during actual production, the proposal task can run smoother and more eflciently. And by following these guidelines you can lead a highly efficient proposal stafs through the toughest proposal efforts and produce a proposal document that wins new business and moves your company forward.
Wilson, Richard P. STC Proceedings (1997). Articles>Grants>Proposals>Project Management
#30549
Publications Project Management A Toolkit for Overcoming Common Pitfalls
Traditional project management 'science' 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.
Anton, Kathy, Teresa J. Tarwater and Andrea Heugatter. STC Proceedings (1993). Articles>Project Management>Publishing
#25479
Running a project Weblog is a great way to collect, organize, and publish the documents and discussions that are the lifeblood of the project and to shape these raw materials into a coherent narrative. The serial nature of the Weblog helps you make it the project's newspaper of record. This kind of storytelling can become a powerful way to focus the attention of a group. The desire to listen to a compelling story and find out what happens next is a deep human instinct.
Udell, Jon. InfoWorld (2003). Articles>Project Management>Community Building>Blogging
#14243
PubsTrac: A Project Management Simulator
The PubsTrac simulator is a new tool for teaching project management in a technical publishing context. It takes the form of a board game in which one or more people each manage one or more projects. Each project must progress through the many steps that make up a typical technical publication development project, and must deal with such problems as bad reviews, product redesigns, sick employees, and resource overloads. In this workshop, participants will actually experience PubsTrac in small groups.
Caernarven-Smith, Patricia and Anthony H. Firman. STC Proceedings (1995). Presentations>Education>Project Management
#24338
Quality Management in Software Development Projects
How do you ensure that business software systems will be good quality, i.e. they will meet the business need and have few bugs? How might 'testing' be perforned at the requiremenst and design stages?
Roberts, Mike Harding. HRA Consulting (2004). Articles>Project Management>Quality
#26837
In rapid prototyping interactive prototypes are developed which can be quickly replaced or changed in line with design feedback. This feedback may be derived from colleagues or users as they work with the prototype to accomplish set tasks. This method is concerned with developing different proposed concepts through software or hardware prototypes, and evaluating them. In general the process is termed ‘rapid’ prototyping. The development of a simulation or prototype of the future system can be very helpful, allowing users to visualise the system and provide feedback on it. Thus it can be used to clarify user requirements options. Later on in the lifecycle, it can also be used to specify details of the user interface to be included in the future system.
#27462
Real Costs Of Technical Publications
This workshop shows a technical publication manager or rising professional how to work in the following technical publishing/financial areas: project management, operating budget preparation and management, and quality control.
Caernarven-Smith, Patricia. STC Proceedings (1994). Articles>Publishing>Technical Writing>Project Management
#24458
The Real Costs of Technical Publications
This workshop shows you how to balance the relationships among time, money, and output. Time is defined as your time and the machines’ time. Money is what this all costs. Therefore, your manuals, screens, and moving media cost money - money we can account for. In this workshop, we will tackle some timehonored questions.
Caernarven-Smith, Patricia. STC Proceedings (1995). Articles>Project Management
#27253
Relating PMBOK Practices to Agile Practices
Michele Sliger understands the turmoil traditional project management practitioners go through as they make the transition from plan-driven approaches to the newer agile methodologies. This week, she offers more insight as she continues her four-part series on relating Project Management Institute (PMI) best practices--as identified in the Project Management Body of Knowledge (PMBOK)--to agile practices. In this column, Michele discusses scope management and time management.
Sliger, Michele. StickyMinds (2006). Careers>Project Management>Agile
#26833
User and usability requirements should be well-defined and integrated into relevant product requirements specification. The purposes of usability methods at this stage are to collect information about the user interface, users, tasks and environments, and to agree what aspects should be formalised as requirements.
UsabilityNet. Resources>Usability>Planning>Project Management
