Project Charter

• Statement of work
• WHY wn project plan—to introduce the team, new people in the project
• To introduce people about the project—to sell the poject
• Project request or SW
• Signed from sponsor and get approval for the project planning
• A good charter not more then 5- pages otherwise no one read them
• Every one who get involved in the project will see it different
• Y the poject is a good idea---back ground information
• Wt to do no and wt is not to do to avoid confusion
• Draw a boundary line---build the product but not market
• List the objective that should be measure able
• Sponsor, PM and team lead
• Key dates and mile stone
• Contraints, assumptions and risks, dependencies
• Risk---might get in your way
• Sponsor and the team should create charter
Project Charter

• In project management, a project charter, project definition,

or project statement is a statement of the scope, objectives, and
participants in a project. It provides a preliminary description of roles
and responsibilities, outlines the project's key goals, identifies the
main stakeholders, and defines the authority of the project manager.
• Work as a primary sales document. Serves as a focal point throughout
the project. For example, it is a baseline that can be used in team
meetings and in change control meetings to assist with scope
management.