Project kickoff Library management system

timer Asked: Feb 4th, 2019
account_balance_wallet $10

Question Description

Create an 10 slide project kickoff presentation in Microsoft® PowerPoint® similar to this Project Kickoff (SAMPLE TEMPLATE ATTACHED BELOW). PLEASE USE REFERENCES ATTACHED BELOW TO GATHER INFORMATION FOR THIS ASSIGNMENT. ***include short speaker notes

The kickoff presentation you create should include details pertaining to the project you defined in the Project Plan Draft assignment below, including budget details as appropriate. Specifically, your presentation should include: ***A high-level project definition ***Business case (a description of the business problem/opportunity the plan is designed to solve/exploit) ***Project approach ***Description of team members and roles ***Project scope ***Out of scope ***Timeline ***Budget and budget reporting ***Risks, cautions, and disclaimers

Unformatted Attachment Preview

Project Kickoff Customer Service Phone App Goals and Objectives ▪ Provide convenient/on-the-go customer service ▪ Phone app will allow customer to: ▪ Schedule service call ▪ Online chat with service agent ▪ Leave text message ▪ Get customer status Project Scope ▪ ▪ In Scope: ▪ Support for Android and iOS ▪ Features: ▪ Chat ▪ Text ▪ Customer status Out of Scope: ▪ Support for Windows and Blackberry ▪ Features: ▪ Integration with website (future) Budget / Sponsor ▪ Approximate Cost – $200,000 ▪ Sponsor – Customer Service Area Implementation Timeline ▪ Design – week of 5/7/18 ▪ Features ▪ ▪ User Stories ▪ Scenarios ▪ Acceptance Criteria/Conditions of Satisfaction Sprints – 6 weeks (5/14 – 6/22) ▪ UX ▪ Back end ▪ Reporting ▪ UAT – User Acceptance – 2 weeks ( 6/25 – 7/13) ▪ Release – 2 weeks (7/16 -7/27) Risk Factors ▪ ▪ Availability of resources: ▪ PM assigned to multiple projects ▪ Product owner availability (still has “day job”) ▪ Developers still have to support existing apps New technology ▪ Chat feature ▪ Text interface Project Team Roles and Responsibilities [Full Name] Project Manager [Full Name] Product Owner [Full Name] Developer UX [Full Name] Developer DB/API [Full Name] Developer Reporting [Full Name] Tester QA/UAT Team/Stakeholder Communications ▪ Team meetings ▪ Status reports ▪ E-mail updates ▪ Shared project folder Running head: WORK BREAKDOWN STRUCTURE METHODOLOGY 1 Work Breakdown Structure Methodology WORK BREAKDOWN STRUCTURE METHODOLOGY 2 Work Breakdown Structure Methodology (WBS) I chose WBS methodology since it simplifies tasks since the workload is assigned independently to the team and worked on simultaneously. As a result, challenging tasks are completed successfully. The project manager can also effectively supervise individual tasks rather a collection of activities. The outcomes are measurable, and the team can are prevented from performing additional duties that are not stipulated in the WBS framework (Scheid, n. d). Besides, since the tasks can be quantified; the project manager can determine the budgetary requirements of each function and allocate the required financial resources to each of them. In this regard, the delegation of jobs is so efficient that it minimizes wastage. The workload is divided into scheduled units that enable the project manager to track their progress. Using the knowledge, the manager can establish the completion period for the project. Moreover, the scope of the project is clearly defined, and the team can accurately determine what items within the framework has not been completed. The work is; therefore, completed after they meet the partial requirements to create a functional project. Besides, the project manager can assign responsibilities to specific individuals. The persons are obliged to ensure that their teams work within the limits of the projects (budget and deadlines). Most important, the productivity of the group is enhanced since the project managers can determine the strengths and weaknesses of each and delegate work according to their competencies. Also, the tasks are comprehensively delineated; thus, they work to achieve the common goal of the project (Scheid, n. d). In this regard, the team can determine the correlation between the deliverables WORK BREAKDOWN STRUCTURE METHODOLOGY 3 consequently promoting accountability and transparency. In conclusion, it provides an interactive environment where the members communicate to solve critical issues. Project Plan My project involves a software development of a library system that uses a computerbased system to manage its operations on a day-to-day basis. The project will incorporate many features that will puts e-library on another level. I will create a simplified project using the waterfall model that will encompass the determination of the system requirements, software requirements, analysis, program design, coding, operability, testing, and maintenance. The program design will incorporate deliverables that control, analyze, monitor, and test the software phases (O' Reagan, 2017). The initial capital and other budgetary conditions of each deliverable will be determined. Besides, the feasibility of the project is determined to establish whether it satisfies the market niches. Furthermore, the project deliverables will be identified and allocated specific completion timelines. The size of each deliverable will be measured, and the labor requirements needed to accomplish them. Also, the complexity of the phases will be determined, and an appropriate approach used that optimizes the strengths of each team member. Communication within the development period will be carried out through meetings and feedbacks on emails and memos. Every task within the development framework will be marked against a checklist upon completion to enhance efficiency, and all the deliverables are completed. Potential risks within each phase will be identified to prevent the occurrence of undesirable outcomes. The threats are analyzed and controlled using countermeasures to eliminate or reduce their effect on the WORK BREAKDOWN STRUCTURE METHODOLOGY 4 system’s lifecycle O' Reagan, 2017). Importantly, the project will have quality control stages to ascertain that the deliverables meet the expected standards set at the initial stages. Any challenges encountered will be resolved amicably under the guidance of the team managers. WORK BREAKDOWN STRUCTURE METHODOLOGY 5 References O’ Reagan. (2017). Software project management: Concise guide to software engineering. Springer. 27-46. doi: 10.1007/978-3-319-57750-0_2 Scheid, J. (n. d). How to implement the WBS methodology. Bright Hub PM. Retrieved from ...
Purchase answer to see full attachment

Tutor Answer

School: UIUC



Project kickoff.
Library management system.

Goals and objectives.

To provide easy access of books.


To enable a 24 hours access of books.


Increase the number of people with access to the library


Reduce manual work and the risk loosing books.


Project scope.
In scope.
Support windows and android.

Student portal.


Student registration.


Student log...

flag Report DMCA

Tutor went the extra mile to help me with this essay. Citations were a bit shaky but I appreciated how well he handled APA styles and how ok he was to change them even though I didnt specify. Got a B+ which is believable and acceptable.

Similar Questions
Hot Questions
Related Tags
Study Guides

Brown University

1271 Tutors

California Institute of Technology

2131 Tutors

Carnegie Mellon University

982 Tutors

Columbia University

1256 Tutors

Dartmouth University

2113 Tutors

Emory University

2279 Tutors

Harvard University

599 Tutors

Massachusetts Institute of Technology

2319 Tutors

New York University

1645 Tutors

Notre Dam University

1911 Tutors

Oklahoma University

2122 Tutors

Pennsylvania State University

932 Tutors

Princeton University

1211 Tutors

Stanford University

983 Tutors

University of California

1282 Tutors

Oxford University

123 Tutors

Yale University

2325 Tutors