|
Concept and Selection
Articulate business and customer justifications for the project idea; do quick rough take at approach, scope, time, costs; evaluate the business case, determine whether to proceed, and identify initial team.
Project Proposal and Evaluation
Opportunity Screening Worksheet
New Project Proposal
Project Scope Definition: Mission Statement
Project Scope Definition: Deliverables
Project Business Case
Assign PM and Sponsor
Project Sponsor
Project Team Leader Description - Roles & Responsibilities
Effective Meetings Checklist
Action Item List Formats
Initiation and Planning
Form the initial team, define the requirements in detail, investigate and review major design alternatives for fulfilling the requirements, and plan the rest of the project.
Team Kickoff - Project Goals, Team Roles and Responsibilities
Project Charter
Project Team Organization and Assignments
Software Release Team Member Glossary
Task Responsibility Matrix Formats
Stakeholder Analysis Summary Table
Team meeting agenda
Project Requirements
Agile Technique Brief: Requirements Cards
Business Process Modeling Technique Brief
Software Requirements Specification
Software Requirements Capture Guideline
Requirements Interview Checklist
Requirements Workshop Planning Guide
Use Case Specification
Technique Brief - Context Diagrams
New System Request for Proposal (RFP) Outline
IT Project Request for Proposal
High-Level Design and Reviews
Agenda for Preliminary Design Review Meeting
Review Checklists: Preliminary Design Review
Project Alternatives Tradeoff Table
Guideline for Deciding Whether to Outsource Work on a Project
Vendor assessment checklist
Project Plan Signoff Checklist
Team Communication
Agile Technique Guideline: Standup Meetings
Communications Plan
Project Stakeholder/Influencer Assessment and Communication Plan
Milestone Table with Driver Tasks
Team Meetings Descriptions Sample
Team Meeting Agenda
Team Meeting Minutes
Planning, Scheduling, Estimating, Costs, and Risks
Configuration Management Plan
IT Project Plan Document
Requirements Management Plan
Requirements Measurement Plan
Benefits Realization Plan
Software Project Plan
Software Release Life Cycle Overview
Project Flexibility Matrix
Cost Benefits Analysis
Product and Project Risk Assessment and Mitigation Tables
System Hazard Analysis Method
Project Risk Checklist
Project Budgets and Cost Tracking
Project Overview Test Plan
User Impact Assessment (IT)
IT Process and Staff Impact Assessment
User Documentation Plan
Training Plan - High Level
Guidelines for planning and scheduling:
Example Work Breakdown Structures
|
 |
Execution and Approval
Create the project deliverables, reviewing and testing them along the way for quality and adherence to the project requirements.
Ongoing Planning
Maintenance Planning Guidelines and Plan Outline
Specifications and Development
Business Data Dictionary Template
Software Requirements Specification
Localization Guidelines
Interface Protocol Document
Reviews
Guideline for a Simple Signoff Process
Review Checklists: Detailed Design Review
Review Checklists: Critical Design Review
Review Checklists: Final Design Review
Coding Review Guidelines
Development Testing
Project Test Plan
Software Unit Test Plan and Report Guidelines
Integration Plan
Software Integration Checklist
Software Test Transfer Forms
Tracking and Status
Agile Technique Guideline: Information Radiators
Tracking with Visible Deliverables
Team Member Status Report
Project or Software Release One-Page Summary
Executive Summary of Project Status/Risks
Project Escalation Process Guidelines
Change Control Form
Requirements Traceability Guideline
Requirements Change Management Guideline
Project Status Reports
Project Scorecard
Issue Resolution Status Report
Approval Testing
QA and Beta Test Manager Job Descriptions
Master Test List
Beta Test Plan
User Acceptance Test Plan
Issue Resolution Status Report
Change Control Form
Completion Criteria/Checklists
Release decision process guidelines
Software Quality Release Criteria
Delivery and Closeout
Release and deliver the project's outputs to customers, get initial customer feedback, and close out the project, including taking stock of lessons-learned.
Release to Delivery
Guidelines - Completion Criteria
Close-out Activities
Project Closeout Meeting Agenda
Lessons Learned Survey
Lessons Learned Meeting Report
Related Links
More resources you might find useful to further your knowledge of software projects and managing projects in IT organizations
|