kick off meeting PPT for :
Term Project for PCM210
Term: Summer 2018
Course title: Project Management Communications skills
You have been assigned as a PM of a new development project for Abacus Inc., a software company with headquarters in Toronto, ON. The project is about developing a new e-commerce site of the company so that it can offer its products online. This project is time-sensitive but the budget is not a major issue. You have been asked to find ways to deliver a high-quality product as soon as possible.
The solution will replace the existing e-commerce, which is hard to maintain because it's been around for a few years and hasn't been updated properly and uses old technology, and doesn't really integrate that well with other systems. Karla, is the site owner and is the sponsor of the new e-commerce solution. She and her team members, Ali and Bianca, will provide the requirements. They tell you that most of the requirements are known already and just need to be brushed up.
You meet with George, from PMO, who provides all the information already established about the project, which seems to be not a lot! The e-commerce solution needs to integrate with quite a few systems within and outside of the company to be able to provide end-to-end solution. The systems identified so far include:
1- Accounting system: to provide up to date pricing information, discount, etc. Lily, the accounting manager is assigned to be accounting team representative in the project. They have a system, called Accountint that maintains the product pricing, discounts, customer information and so on. That system has some APIs, but they may need to tweak them to work with the new system. Larry, the dev manager on Accountint can coordinate what's needed with the vendor, ABC Inc.
2- Support System: to provide post-sale support. This is a ticketing system that you need to be able to link to the purchased products. Chris, the support manager running a project in his team to redefine the support levels. At a high level, there will be three level of support for each product, providing different levels of support and priced accordingly.
3- Integration with SoftwareSupply.com. This site is a hub for many potential clients who search there and compare similar products before deciding to purchase a software license. Your company wants a presence there, to be able to attract those potential customers. They have APIs that you can use to integrated software product specifications with them.
Marketing group is another stakeholder of this project. Jim, the marketing manager assigned to work on the project says he needs to be able to implement marketing campaigns though the new e-commerce that can support functionalities such as promotion codes and loyalty programs. He talks about subscription levels. You wonder if there are conflicts between what you are hearing from these different stakeholders.
Karla, wants the project to be kicked off as soon as possible. She also wants to stay close to the project, but not "to step on everyone's toes". She and her team still have to run the existing e-commerce solutions, so you figure out they must be busy and finding time with them to provide project progress report or get the needed information might present a challenge. Karla is asking the project to be completed in the next 6 month, at the latest. She wants a status report on a weekly basis and offers to be available with a short notice when needed. At the same time, she offers Ali and Bianca to be more available and support the project.
PMO has a few templates that you can use but the existing ones for project communication plan and status updates may not be suitable for a project like this that needs to integrate a few systems. Other than that, the project will have a standard Sharepoint site that everyone on the project can access and store/retrieve project artifacts and information.
The core project team consists of development team, led by Hema. She has a designer in her team, called Roy, and 5 developers that you don't have their names yet. Bill is the QA lead. He says he has secured one resource and depending on sizing of the project he can bring more people form QA team into the project.
Write up a presentation for the kick-off meeting.
Project Goals and Objectives
Document the goals and objectives of the project. The customers or owners may provide their specific goals and objectives, as well as adding the project team's goals to this section.
Document the project's scope
Project Out of Scope
Document the projects out-of-scope components. It is important to call out what items the project will not complete so the customers and team members are clear on this at the beginning of the project.
Risks & Issues
Document the project's project risks and issues. At this point, the project may not have many risks and issues, but it is important to track and note any at this time.
Document the project's budget estimate. At the project kick-off process, the estimate provided will be at a tolerance level and an established variance level; having a refined estimate at this stage of the project would be difficult.
Project Schedule (Timelines)
Document the schedule of the project. The schedule will be a milestone level only and will match to the major deliverables of the project. The methodology selected will drive the deliverables.
Document the various methodology deliverables. Depending on the type of project and the methodology chosen, this section will include all the relevant deliverables for this project.
Requirements Deep Dive
Document the detail requirements for the project.
Design Deep Dive
Document the detail design information for the project.
Development Deep Dive
Document the development details for the project.
Test Deep Dive
Document the detail testing information for the project.
User Acceptance Criteria Deep Dive
Document any specific user acceptance type testing for the project.