によって Sophea OU 5年前.
265
Sale problems
The document outlines various operational challenges within a sales team, emphasizing problems like duplicate customer entries, repeated calls to the same number, and multiple promotions to the same client.
によって Sophea OU 5年前.
265
もっと見る
Enter your project name
Begin by typing your project name into the Central Topic below, then press the Enter key or click the right-arrow button.
Project activities and schedule
Although we are not planning a detailed schedule here, this map should include the major work elements so that they can be broken down into tasks later.
Add a project activity
Type in a project activity. Examples include:
Add the timescale for this activity
When will this activity take place? Type an approximate date or a project stage.
Communications plan
Communications are vital to your project, so that all stakeholders know what they need to know to play their part. A communications plan helps you to keep everyone informed.
Key communications events
Your communications plan should include a number of key events, with specific purposes and outcomes. You can choose from the suggestion that follow or add your own.
Add another event
Add other project communications events not listed above, or press Enter to skip.
Include a project review?
The project review meeting takes place once the project has been closed, and examines the processes that led to both success and failure in the project. The goal of the review meeting is to improve processes and techniques for the next time.
Click the icon to include a project review meeting:
Communication and collaboration tools
What communication and collaboration tools will you use? How will you issue bulletins, share documents and work collaboratively? Which tools will be suitable for your stakeholders?
Add a communication tool
Add a communication / collaboration tool. Examples include:
Requirements Management
Requirements often make or break projects. If the requirements are not well known in advance, the way that you handle this situation will have a significant impact.
Knowing the requirements is important, but it is more important to be in control of the requirements, and to know what is excluded as well.
Exclusions
For clarity, you should state any known exclusions that are definitely not part of the project, especially if there is a chance that someone might reasonably assume they are included.
Add an exclusion
Specify an exclusion from your project. Examples are
Known requirements
List the major known requirements for your project. If there are a lot, then you might choose to put these in a separate map. You can always come back and add more later. The important thing is that the requirements are gathered in one place and are roughly classified. Requirements can include:
Add a requirement
Add a requirement in the topic text. Requirements should be specific enough to be tested. Prioritise it with MoSCoW grades by clicking on an icon:
Project Stakeholders
A 'Stakeholder' is anyone who might be affected by the project or its outcomes. Some stakeholders are clear, for example the customer and users. But sometimes there are hidden stakeholders, such as people who share the resources that the project will also use. You will need a list of stakeholders for your communication plans.
Users
The users of the outcome of your project may not be the same as the customers who pay the bill. Who are the users, and who represents their interests on the project?
Add a user
Add a user or user representative, such as:
Customers
Who are the people in the customer's organisation who are important to the project?
Add a customer representative
Add a customer representative. These might include people who:
Project sponsors
Project sponsors are the senior members of your organisation who are backing (or will need to be persuaded to back) your project. They provide the authority for the project.
The Business Case
The Business Case justifies the investment in the project. If your project is already approved, then you can skip over this section and delete it later. But if you need buy-in for your project, then you may need to make a simple business case.
Strategic 'fit'
How well does this project fit your strategy?
Is it 'strategic'?
Does it help you along the road towards strategic goals, either for your team, department or company?
Add a strategic reason
Add a strategic reason for this project.
Key benefits
What are the key benefits to your organisation in taking this project forward?
Add a key benefit
Type in a key benefit from this project. Examples include:
Estimated costs
Estimated costs will help to determine the level of authorisation required, the cost/benefit ratio, and the opportunity costs of the project.
Add an estimated cost
Type in the name of a cost and the estimated amount. Typical costs include:
The Statement of Work
The first thing to write is the Statement of Work. This gives a high-level overview of the major items that the project should deliver.
Project resources
What are the key resources that this project will need?
Milestones
A project milestone is an event that shows progress along the path towards completion. Milestones usually have deadline dates.
Add a project milestone
Type in the name of a milestone for your project. Examples include:
Deliverables
A project deliverable is evidence of real progress. It is something that can be handed to your customers or users.
Add a project deliverable
Type a project deliverable into the topic text below, and press Enter. When you are finished, press Enter again. Examples of project deliverables include:
