Introduction to project

Introduction
This blog is based on practical experience on software project management and The project management institute’s PMBOK( Project management Body of Knowledge),Providing specific HOW-TO-DO it tips for achieving many of PMBOK’s Recommended best practices.

This Manager’s Blog to project management is designed as a quick reference guide for the busy manager. All the time tested PM worksheets and guidelines will be keep on posting on this Blog very frequently without the extensive theory and background information that will the beauty of this Blog. This quick reverence project manager’s Blog is meant to be a practical reference for each busy software project manager as well as beginners who willing to learn software project management. I hope this Blog will be valuable tools for planning and managing your projects and that you enjoy the experience.

The upcoming practical topics are:

Unique Project Life cycle

The project Charter

Project Scope Statement

Estimating Durations for Required Activities and resources

Project Communications Planner

Risk assessment and response analyzer

Guideline for keeping Things Moving a “TO-DO” list and tools to help you

execute, control, and close out your project

Project Deliverables status analyzer

Variance Analyzer

Guide line for handling scope change

Project Scope Change order

Project Issue Tracker

Project Status Report

Sample project sign off form

When and how to kill the Project

Before going in details of above topics, lets have a quick look on some very important definition related to project management

Project:
A project is a temporary endeavor under taken to create a unique product or service.

Point to ponder:
Since project is temporary (i.e. It will have defined Start and End Date), Project managers Must get their Project completed by expending only the amount of time, money, lobor, and other resources that have been allocated.
Since Project result in unique products and services, so projects are are typically organized into specific phases that most appropriately reflect the evolution of these unique deliverables.

Project Deliverables:
Any meausurable, tangible, verifiable output that must be produced to complete the project. Deliverable takes 2 forms:
Interim output like software E_R diagram or use case Diagram
Final deliverables associated with these interim outputs

Project Phase
A project Phase is a collection of project activities, usually resulting in the creation of a major deliverable

Note:
There are literally hundreds of project activities that must be undertaken in order to create all the deliverables listed. We could jump right I and try to complete all of them at once, but this would likely result in chaos. Instead, we combine the activities into clusters and sequence them so that we can proceed logically and systematically. In short we group the project activity in short; we group the project activity in phases.

Project Life Cycle:
The project life cycle is a collection of project phases whose name and number are determined by the control needs of the organization involved in the project.

Stakeholders:
Those who are affected by project activities.(it might be team member , customer, suppliers , any people who will be effected by this project )

Stakeholders review and approve deliverables at each phase before allowing the next phase to begin. In this way stakeholders try to ensure that deliverables evolve in a steady, controlled fashion and that resources are not wasted.


Next Topic will Be Unique Project Life cycle

Will be available on next friday 4th may 2007