Document Mayhem
Project Management Software > Document Management Software
Risk Assessment Quality Review Checklist
Make sure your IT projects are bulletproof. This checklist doubles as both a quality review plan and a risk assessment document.
Quality Management Systems Procedures: Design Change Control
This document will help you document the change control process for software products and applications.
Story Cards Tracking Tool
Getting customers to write down requirements is next to impossible. Fortunately, Extreme Programming (XP) understands and even embraces this reality and recommends an alternative approach to voluminous software requirements specifications: Story Cards.
Quality Management Systems Procedures: Software Development
This procedure defines all the activities involved in software development, from design through unit testing.
PMXPO 2012
gantthead is once again excited to be bringing you our annual virtual conference and exhibition on Thursday, May 17, 2012. It's your opportunity to learn, network, earn PDUs and gain valuable knowledge all from the comfort of your home, office-or home office. Registration is FREE, so take a minute now and make sure you don't miss out on what promises to be one of the highest-value conference experiences in project management this year.
gantthead is once again excited to be bringing you our annual virtual conference and exhibition on Thursday, May 17, 2012. It's your opportunity to learn, network, earn PDUs and gain valuable knowledge all from the comfort of your home, office-or home office. Registration is FREE, so take a minute now and make sure you don't miss out on what promises to be one of the highest-value conference experiences in project management this year.
Documentation Summary
The Documentation Summary is aimed at providing a comprehensive collection of documentation materials relevant to the project. This document briefly describes each document in the collection and helps you quickly find the information you want to read.
Requirements Gathering Guidelines and Checklists
Start your requirements gathering with this all-inclusive document outlining the entire process from start to finish.
General Definitions for Siebel Objects
If you're just getting to know Siebel, this is a good place to start. This simple glossary of terms related to Seibel Enterprise Applications will give you a good foundation.
System Requirements Specification
The System Requirements Specification (SRS) document describes all data, functional and behavioral requirements of the software under production or development.
Software Vendor Selection Criteria
How do you weed out the vendors among hundreds of products, philosophies and promises? How can you make the right choice? This template provides you with six criteria to evaluate package software vendor solutions.
An Approach to Quantitative Decision-Making: Analytical Hierarchy Process
The Analytical Hierarchy Process (AHP) is a quantitative decision-making methodology that uses pair-wise comparisons to determine the importance of relative evaluation criteria and the relative strengths of decision alternatives. This document is a crash-course in AHP and is designed to help get you making difficult project decisions (particularly package software-related ones) quickly, confidentally and rationally.
Physical Profile and Architecture Form
Use these forms to track your company's computer and network equipment and to keep current equipment in mind while planning for future hardware and software additions and/or replacements.
Siebel Data Conversion Tips and Techniques
When implementing Siebel, you need to make sure your data conversion goes smoothly. Here is a detailed outline of tips to help you do just that.
Quality Management Systems Procedures: Customer Support
This document describes the processes and activities involved in providing maintenance and continuous support of software products and applications.
DM/CM--The Pricing Imperative
A major drawback to content and document management software systems is their high price.
Product Acceptance Checklist
Is your software product acceptable to your client? Does it meet the user acceptance criteria documented early in the planning process? In the test plans? This checklist will help ensure that you are ready to launch the developed system into production.
Manage the Document
Documents can be a boon or a plague to projects, depending on how they are produced and disseminated. Done right, document management is a huge strategic advantage on projects, fostering visibility, collaboration and shared objectives.
Application Security Assessment Checklist
When undertaking software and hardware deployment, don't forget the importance of application security. Use this checklist to help identify, clarify and document these security issues.
Application of Function Point Analysis
Function points are a measure of the size of a software system. To convert function points into levels of effort, the productivity of the enterprise's development teams must be known or estimated. This three-for-one zipped deliverable includes a document explaining function point analysis, instructions on how to apply a function point analysis and a worksheet set up for an Albrecht function point analysis.
Project Documentation Checklists
This document outlines the major project documentation at each project phase (first section), project management knowledge area (second section) and typical software development life cycle (third part). Feel free to include other documentation sets that are relevant to your industry and project life cycle.
The Importance of Change Control
Why is change control so important? With everything a project manager is responsible for, why so much concern over it? What does it really mean, and how do we perform it?
Converting ACT! Contact Data to Siebel Applications
Getting all of your contact information into a Siebel application can be long and tedious--or it can take about 20 minutes, if you know what you're doing. This document is specific to Siebel Enterprise Applications a CRM software developed by Siebel Systems. It outlines the steps and procedures to be followed while converting contact data from ACT to Siebel Enterprise Application.
Document Delivery
When you’re turning in documents and project deliverables to your customer, you need to consider what they’re seeing and what message you’re sending them with the quality of your output. One slip-up can send a very sloppy message that can hinder the rest of the project--and your relationship.
Facing Reality: A Few Fundamental Truths
It’s time that we face up to a fundamental reality: organizations grapple with making project management work successfully on a consistent basis. Yes, there are exceptions--and some notable ones--but on the whole they simply prove the rule. It's time for a different approach.
Breaking Down the WBS
The work breakdown structure is a critical element of the project plan, yet many project managers have difficulty creating an adequate WBS, or even understanding how it can help them. Here is an overview of what a WBS is, and the work that goes into it — you might call it a WBS of a WBS.
Quality Management Systems Procedures Testing
This procedure describes the process of testing software code or products by the test team. It documents the procedure for the entire testing cycle: generating test plans, scheduling tests, conducting tests and reporting test results. This procedure applies to new development, as well as major and minor releases, including customized solutions delivered to customers.
When PMI is TMI (Part 2)
What is a PM to do when confronted with an organizational culture that places little emphasis on structured project management principles? In Part 2 of this series, we’ll examine a simpler approach for introducing structured PM techniques into an organization with one-page project plans.
Training Design Document
This design document serves as the guide to content development for a training course. After this design document is reviewed and approved, all content should be gathered to support the specified learning objectives. The guidance in this document, once approved, is considered sufficient to move to the next developmental process step.
Setting the Project Stage
We're all actors on a project stage...and a well-written planning document sets us up for a successful project. Here, we explore the key elements of this all-important effort.
RFP: Really Failed Plan?
Some RFPs are bad…really bad. It makes you wonder how clear the purchasing organization is on what they are trying to achieve. Here, we look at the process that an organization goes through in preparing and issuing an Request For Proposal--and identify some best practices.
Agile Myths Debunked
Don't believe everything you hear. The truth behind many agile software development myths will help you identify alternative methods to successfully deliver software.
Change HEADWAY Communications Plan
This document captures the key messages, list the target audiences, align the timing for communication and identify the most effective communication channels in relation to these three elements. For small departmental changes the document can consist of 1-2 pages. For large transformational changes the document may consist of up to 8-10 pages or more and include and internal and external communication plan.
Agile 101: Product Backlog
In an Agile project, you don’t create large documents to hold user requirements; in fact, you don’t need a traditional document at all. The preferred technique is to use a product backlog, which represents a prioritized collection of work remaining on the project at any given time.
The Software Shuffle
Software is built on a variety of assumptions, and we need to understand what those assumptions are--and work around them in defining how we use the software. With so many options in the marketplace, how do you decide what’s good and what’s not? How do you navigate the promises of software vendors to know what you should be looking for, and how do you decide what will actually work for you?
Collaborative Effort
Collaborative technologies have been looming on the horizon for some time, and now with fresh impetus from Web 2.0 and other developments, they are playing a greater role in the planning and execution of various business initiatives. That's because application development requires many entities to coordinate their activities and collaboration--whether virtual or otherwise--and has become a ubiquitous way of software development.
Communication Plan Research Guide
Use this document to improve the research the project manager conducts to complete a communication plan.
Time & Materials Rates Sheet
When it's time to proceed on a "time and material" basis with your subcontractor, you'll need this document to specify exactly how the subcontractor will be reimbursed.
Issue Management Overview
The issue management process is fundamental to the successful delivery of the project. It ensures that each issue identified within the project environment is documented, prioritized and resolved within an appropriate timeframe. Use this document as a framework to identify, document, prioritize and resolve your project's issues.
What Agile Is — And What It Isn’t
There’s going to be a lot more talk about Agile now that the Project Management Institute has introduced a new certification program for Agile Project Practitioners. Let’s clear up some initial confusion and look at what Agile is and is not, and why you should care.
Blurry Vision?
Is a project "vision statement" necessary? Let’s look at some of the perceived advantages of having a documented vision statement in place at the beginning of the project engagement to find out.
Midas and the Business Value of CRM
How do you determine the business value of CRM and perform a benefit scan as part of a value-based management approach? Learn by doing, of course! Use this case study example of Midas, Inc., a fictional enterprise that manufactures and markets investment goods, and play along at home as you work your way through the case study.
Training Scope Document
The purpose of this document is to present a comprehensive summary of the discussions and analyses completed to date for development of training to support your project.
Change HEADWAY Training Plan
This document defines the requirements of the training plan that will support the implementation and adoption of the the change. For small changes the document can consist of 1-2 pages. For large changes the document can be extensive as this plan is imperative to the transformation of the organization.
Change HEADWAY Change Management Plan
This document presents the detailed plan for integrating change in the organization. For small changes consider including relevant elements of the document to the Project HEADWAY Project Plan template. For medium changes consider the relevance of a lite Change Management Plan. For large changes complete the Change Management Plan and consider other elements to be added that add to the likelihood of the adoption of the change.
State of Requirements Management
Results from a survey offer business analysts, project managers, developers and other project stakeholders information to help transform the way they produce and manage software requirements.
DAD Systems Documentation Plan
This Microsoft Project plan reflects the activities for documenting the functionality of a distributed application system in a retail environment, i.e., order processing, pricing, inventory, shipping, customer and distributor administration, marketing, etc.
Evaluation Process Ground Rules
Use this document to help you manage application package vendors during every aspect of the evaluation process.
Security Procedures
What's the password? Do the right and only the right people know how to get into the system? Document the procedures and access priveleges and restrictions for keeping your application package system secure.
TeamPlay Pilot Implementation
Your company has chosen Primavera TeamPlay as its new standard project portfolio management tool. This document will provide a project charter and high-level guide to starting a pilot implementation.
Change Control Plan
The only constant in life (and projects) is change. This plan documents a change control procedure that can handle the messiest and most extensive of changes.
