Let’s discuss about Develop Project Charter Process in detail:
This is the process where we create project document which formally authorizes the existence of project and also formally authorizes the project manager to use organizational resources to achieve project objectives or the organizational strategies. The input, Tools and Techniques and output to this process is as follows:
- Business documents: Business case
- Agreements: Any contract or procurement document
- Enterprise Environmental Factors
- Organization process Assets
Tools and Techniques
- Expert judgment
- Data gatherings using brainstorming, focus groups, interviews.
- Interpersonal Skills using conflict management, facilitation techniques, meeting management.
Expert Judgement is the judgement provided by the experts in the area of discipline, knowledge, industry etc to perform activity. Such experts are from groups or person individual in the area of their skills and knowledge, technical expertise.
Data Gathering can be done by using:
Brainstorming: This techniques is used to generate ideas. This is to be done in groups and led by the facilitators. Brainstorming can be used in data gathering for generating idea, solution etc. by stakeholders or team members while creating project charter.
Focus group: this is used to bring stakeholders, subject matter experts to learn about perceived risk, success criteria and other things in conversational way rather than one to one interview.
Interviews: This is used for data gathering by interviewing stakeholders, team members etc. by one to one meeting.
Interpersonal Skills using conflict management, facilitation techniques, meeting management.
Meetings are held with key stakeholders , team members to get high level information like success criteria, deliverable , project key objectives etc.
If you work in a matrix organization, then your team doesn’t report to you.They report to functional managers, and might have other work to do. But when they’re on your project, you’re effectively their boss. So how do you make that happen? Well, you need some sort of authorization, and that’s what the project charter is for. It says exactly what you’re authorized to do on the project (like assign work to the team members and use the company’s resources), and why you’ve been assigned to it. But the charter isn’t just important for matrix companies. In any kind of company, it’s really important to know who’s in charge, and what resources you have available to you when you manage a project.
When you think about it, a lot of different people’s opinions can help your company come to a good decision about whether or not to start a project. Sometimes project sponsors will call on experts to help them decide which projects to do. At Acme Travel, the CEO called a meeting with the VP of Asia Travel to make sure that the teachers’ trip was worth doing. The VP of Asia Travel had set up trips like this one before and he knew where things could go wrong in planning them. Together, they looked at all of the project documentation to make sure that this project looked like it would make Acme enough money to be worth doing.
Your company might need to talk to subject matter experts from a bunch of different departments to decide if a project will be beneficial to it. It might rely on outside consultants or industry groups to tell it how other companies have solved the same problem. All of those different opinions are called expert judgment.
If the experts agree that the project’s business case, contract, and statement of work all add up to a product that’s going to do good things for your company, they’ll usually give the green light to write the charter.
When you sit down to write your project charter, you’ll need to get your stakeholders on the same page about what your project team will do. You might set up meetings with your stakeholders to brainstorm project goals or work with them to resolve conflicts around how your project will run. All of the approaches you take to get everybody on the same page are called facilitation techniques.
- Project Charter
- Assumption Log
The Assumption log is updated or generated through out the project life cycle which records assumptions and constraints .