Project Management: Detailed Analysis of Notebook Purchase Project

This project management assignment presents a detailed analysis of a project aimed at purchasing a notebook for a junior business analyst. The project begins with the creation of a project charter, outlining objectives like comparing notebooks, purchasing the most effective one, and setting up a network connection, all within a budget of $1000 and a two-week timeframe. The project follows a Prince2 approach and includes defined roles and responsibilities. A comprehensive project plan is then developed, featuring a Work Breakdown Structure (WBS) that breaks down the project into phases: project initiation, planning, buying process, monitoring and control, and closure. The plan also includes task durations, a Gantt chart for visualizing the timeline, and detailed cost breakdowns. The document further addresses project monitoring and reporting, including a task log sheet, and a reporting plan. Risk assessments are also included and a status report detailing completed and upcoming tasks. The project's success hinges on effective monitoring and control to ensure adherence to the budget and schedule.

Running head: PROJECT MANAGEMENT
Project Management
Name of the student:
Name of the University

1PROJECT MANAGEMENT
Task 1: Project charter
Date 7/16/2019 Author name <Please fill>
Project release 05/08/2019
Start date 7/16/2019 Finish date 8/02/2019
Project manager Please fill
Project objectives  To compare all the available best notebooks
 To buy the most effective featured notebook
 To setup network connection with the notebook
Approach In order to accomplish this project the project execution approach that
has to be followed by the project associates is Prince2. All the phases of
Prince2 are should be followed respectively to complete the connection
setup within the estimated budget of $1000 and time of 2 weeks. It has
been determined that if this approach is properly followed throughput
the phase then the junior business analyst would be able to carry the
notebook and use those whenever required.
Roles and responsibilities
Name Role Responsibility
Steven Smith The role of a business analyst
is to design the business
strategies in such a way so that
the entire company can reduce
The main responsibility of the
business analyst is to help the
business to implement
effective technical solutions

2PROJECT MANAGEMENT
the overall complexity of the
operations and functions. In
order to develop the most
effective strategy the analyst
collects and interprets data
from different areas within the
organization
after precisely determining the
requirements and project
programs, key stakeholders
and communication strategies.
Comments
It is determined that if all purchase or buying requirements are successfully throughout followed
by company associates then the junior business analyst would be able to spent a lots of time in
the office and also along with the clients. The analyst would be able to keep himself or her-self
updated regarding the product and service requirements. The goal of the project is to get the
correct notebook with accurate setup at a minimum amount of cost and time of 14 days or 2
weeks.
Task 2: Project plan
2.1 Work Breakdown Structure (WBS)
WB
S Task Name
0 Schedule for buying a notebook
1 Project initiation
1.1 Project scope statement development
1.2 Requirement identification and gathering

3PROJECT MANAGEMENT
1.3 Resource identification and gathering
1.4 Checking for best notebook
1.5 Comparison between the different notebooks developing organizations
2 Project planning
2.1 Feasibility analysis
2.2 Risk management plan
2.3 Resource plan
2.4 Software requirement gathering
2.5 Hardware requirements gathering
2.6 Preparing accurate network
2.7 Comparing online for the best featured notebook
3 Buying process to be followed
3.1 Identification of the main problem
3.2 Searching for information
3.3 Alternative evaluation
3.4 Purchase decision
3.5 Purchase
3.6 Post purchase evaluation
4 Project monitoring and control
4.1 Connection setup
4.2 Continuous improvement plan
5 Project closure
5.1 Buying the best notebook
5.2 Post maintenance program implementation
5.3 Final implementation

4PROJECT MANAGEMENT
Schedule for buying a
notebook
Project initiation
Project scope
statement
development
Requirement
identification and
gathering
Resource
identification and
gathering
Checking for best
notebook
Comparison between
the different
notebooks
developing
organizations
Milestone 1:
Completion of
proect initiation
Project planning
Feasibility analysis
Risk management
plan
Resource plan
Software
requirement
gathering
Hardware
requirements
gathering
Preparing accurate
network
Comparing online for
the best featured
notebook
Milestone 2:
Completion of
project planning
Buying process to be
followed
Identification of the
main problem
Searching for
information
Alternative
evaluation
Purchase decision
Purchase
Post purchase
evaluation
Milestone 3:
Completion of
buying process
Project monitoring and
control
Connection setup
Continuous
improvement plan
Milestone 4:
Completion of
monitoring and
control phase
Project closure
Buying the best
notebook
Post maintenance
program
implementation
Final implementation
Milestone 5: Project
close
Figure 1: Work Breakdown Structure of the project
(Source: Created by author)
Task identification
The entire notebook purchasing project is subdivided into four phases and all the four
phases are interconnected to each other. It has been determined that the outcome of previous task
is used as the input to the very next task. The four different phases those are considered in this
project are project initiation, planning, buying process, project monitoring and control and
project closure. The net time that has been estimated for the completion of this project is 14 days.
Thus, there will be no time to waste.

5PROJECT MANAGEMENT
After buying and network setup it has been identified that no unit testing, integrated
testing, black box and white box testing will be conducted in this project. However, in order to
check that all the process are meeting project requirements and objectives properly appropriate
control and monitoring phases should be followed. The five monitoring phases that needs to be
followed are as follows:
 Design of appropriate and effective project monitoring plan
 Proper repot management mechanism
 Recommendations on continuous improvement plan
 Ensuring the project guidelines
The total time that has been estimated for the successful purchase of the notebook is
$1000 and the net time estimated is 14 days or 2 weeks. Within this time phase, the business
analyst should purchase this product and establish all the setup as well. Te duration for each task
is also mentioned in the below table:
WB
S Task Name Duration
0 Schedule for buying a notebook 14 days
1 Project initiation 2.5 days
1.1 Project scope statement development 0.5 days
1.2 Requirement identification and gathering 0.5 days
1.3 Resource identification and gathering 0.5 days
1.4 Checking for best notebook 1 day
1.5 Comparison between the different notebooks developing organizations 0.5 days
1.6 Milestone 1: Completion of project initiation 0 days
2 Project planning 6 days
2.1 Feasibility analysis 0.5 days
2.2 Risk management plan 0.5 days
2.3 Resource plan 0.5 days
2.4 Software requirement gathering 0.5 days
2.5 Hardware requirements gathering 0.5 days

6PROJECT MANAGEMENT
2.6 Preparing accurate network 0.5 days
2.7 Comparing online for the best featured notebook 0.5 days
2.8 Milestone 2: Completion of project planning 0 days
3 Buying process to be followed 11.5 days
3.1 Identification of the main problem 0.5 days
3.2 Searching for information 1 day
3.3 Alternative evaluation 1 day
3.4 Purchase decision 1 day
3.5 Purchase 1 day
3.6 Post purchase evaluation 1 day
3.7 Milestone 3: Completion of buying process 0 days
4 Project monitoring and control 12.5 days
4.1 Connection setup 0.5 days
4.2 Continuous improvement plan 0.5 days
4.3 Milestone 4: Completion of monitoring and control phase 0 days
5 Project closure 14 days
5.1 Buying the best notebook 0.5 days
5.2 Post maintenance program implementation 0.5 days
5.3 Final implementation 0.5 days
5.4 Milestone 5: Project close 0 days

7PROJECT MANAGEMENT
Gantt chart for the project
Figure 2: Gantt chart for the project
(Source: created by author)

8PROJECT MANAGEMENT
The Gantt chart presented in above section has shown the critical task and the project
milestones as well. Not only this but also it shows the connection between the project activities
and the total time that is required to complete each of the project activity within assigned time of
14 days or 2 weeks and budget of $1000.
Project costing
The total cost that has been estimated for the project is $1000 that includes hardware cost,
software cost, network setup cost and wages of network engineer and wi fi modem set up cost
and price of the notebook. The cost assigned for the project is detailed in the below section:
WBS Task Name Resource Names Cost
0 Schedule for buying a notebook $1,000.00
1 Project initiation $0.00
1.1 Project scope statement development $0.00
1.2 Requirement identification and gathering $0.00
1.3 Resource identification and gathering $0.00
1.4 Checking for best notebook $0.00
1.5 Comparison between the different
notebooks developing organizations $0.00
1.6 Milestone 1: Completion of project
initiation $0.00
2 Project planning $495.00
2.1 Feasibility analysis $0.00
2.2 Risk management plan $0.00
2.3 Resource plan $0.00
2.4 Software requirement gathering Cost for software [1] $50.00
2.5 Hardware requirements gathering notebook cost[1] $385.00
2.6 Preparing accurate network network connection setup
cost[1],network engineer $60.00
2.7 Comparing online for the best featured
notebook $0.00
2.8 Milestone 2: Completion of project
planning $0.00
3 Buying process to be followed $40.00
3.1 Identification of the main problem $0.00
3.2 Searching for information $0.00

9PROJECT MANAGEMENT
3.3 Alternative evaluation network engineer $40.00
3.4 Purchase decision $0.00
3.5 Purchase $0.00
3.6 Post purchase evaluation $0.00
3.7 Milestone 3: Completion of buying
process $0.00
4 Project monitoring and control $80.00
4.1 Connection setup network connection setup
cost[1],network engineer $60.00
4.2 Continuous improvement plan network engineer $20.00
4.3 Milestone 4: Completion of monitoring
and control phase $0.00
5 Project closure $385.00
5.1 Buying the best notebook notebook cost[1] $385.00
5.2 Post maintenance program
implementation $0.00
5.3 Final implementation $0.00
5.4 Milestone 5: Project close $0.00
Task 3: Monitor and report of project progress
Whether the project is progressing or governing towards the expected direction or not is
checked followed by appropriate project control and monitoring. Project monitoring is referred
to as an important component in the project development life cycle. It is responsibility of the
project supervisor and project team associates to make sure that all the project activities are
followed and maintained to meet the project objectives. The details of the steps are as follows:
 Design of effective project monitoring plan
 Design of accurate report management mechanism
 Project improvement plan
 Post project maintenance plan
The task log sheet for this particular notebook purchase project is as follows:
WBS Task Name Duration Start Finish Resource Names Cost

10PROJECT MANAGEMENT
0 Schedule for buying a
notebook 14 days Tue
7/16/19
Fri
8/2/19 $1,000.00
1 Project initiation 2.5 days Tue
7/16/19
Thu
7/18/19 $0.00
1.1 Project scope statement
development 0.5 days Tue
7/16/19
Tue
7/16/19 $0.00
1.2 Requirement
identification and gathering 0.5 days Tue
7/16/19
Tue
7/16/19 $0.00
1.3 Resource identification
and gathering 0.5 days Wed
7/17/19
Wed
7/17/19 $0.00
1.4 Checking for best
notebook 1 day Wed
7/17/19
Wed
7/17/19 $0.00
1.5
Comparison between the
different notebooks
developing organizations
0.5 days Thu
7/18/19
Thu
7/18/19 $0.00
1.6 Milestone 1: Completion
of proect initiation 0 days Thu
7/18/19
Thu
7/18/19 $0.00
2 Project planning 3.5 days Thu
7/18/19
Tue
7/23/19 $495.00
2.1 Feasibility analysis 0.5 days Thu
7/18/19
Thu
7/18/19 $0.00
2.2 Risk management plan 0.5 days Fri
7/19/19
Fri
7/19/19 $0.00
2.3 Resource plan 0.5 days Fri
7/19/19
Fri
7/19/19 $0.00
2.4 Software requirement
gathering 0.5 days Mon
7/22/19
Mon
7/22/19 Cost for software [1] $50.00
2.5 Hardware requirements
gathering 0.5 days Mon
7/22/19
Mon
7/22/19 notebook cost[1] $385.00
2.6 Preparing accurate
network 0.5 days Tue
7/23/19
Tue
7/23/19
network connection
setup cost[1],network
engineer
$60.00
2.7 Comparing online for
the best featured notebook 0.5 days Tue
7/23/19
Tue
7/23/19 $0.00
2.8 Milestone 2: Completion
of project planning 0 days Tue
7/23/19
Tue
7/23/19 $0.00
3 Buying process to be
followed 5.5 days Wed
7/24/19
Wed
7/31/19 $40.00
3.1 Identification of the
main problem 0.5 days Wed
7/24/19
Wed
7/24/19 $0.00
3.2 Searching for
information 1 day Wed
7/24/19
Thu
7/25/19 $0.00
3.3 Alternative evaluation 1 day Thu Fri network engineer $40.00

11PROJECT MANAGEMENT
7/25/19 7/26/19
3.4 Purchase decision 1 day Fri
7/26/19
Mon
7/29/19 $0.00
3.5 Purchase 1 day Mon
7/29/19
Tue
7/30/19 $0.00
3.6 Post purchase evaluation 1 day Tue
7/30/19
Wed
7/31/19 $0.00
3.7 Milestone 3: Completion
of buying process 0 days Wed
7/31/19
Wed
7/31/19 $0.00
4 Project monitoring and
control 1 day Wed
7/31/19
Thu
8/1/19 $80.00
4.1 Connection setup 0.5 days Wed
7/31/19
Wed
7/31/19
network connection
setup cost[1],network
engineer
$60.00
4.2 Continuous
improvement plan 0.5 days Thu
8/1/19
Thu
8/1/19 network engineer $20.00
4.3
Milestone 4: Completion
of monitoring and control
phase
0 days Thu
8/1/19
Thu
8/1/19 $0.00
5 Project closure 1.5 days Thu
8/1/19
Fri
8/2/19 $385.00
5.1 Buying the best
notebook 0.5 days Thu
8/1/19
Thu
8/1/19 notebook cost[1] $385.00
5.2 Post maintenance
program implementation 0.5 days Fri
8/2/19
Fri
8/2/19 $0.00
5.3 Final implementation 0.5 days Fri
8/2/19
Fri
8/2/19 $0.00
5.4 Milestone 5: Project
close 0 days Fri
8/2/19
Fri
8/2/19 $0.00
Reporting plan for the project
People who will
prepare the plan
Content
format
Frequency of
reporting
Delivery process
Project manager Digital
content
Daily Email and face o face meeting
Network engineer Digital
content
Daily Face to face meeting and
email
Business analyst Digital Daily Face to face meeting,

12PROJECT MANAGEMENT
content conference and meeting
The risks associates to this project are as follows:
 Over allocation of project budget
 Overrunning project timeline
 Lack of business strategies
 Lack of technical knowledge among project supervisor and project team associates
 Insufficient resource allocation
Status report
Date 7/16/2019 Author name <Please fill>
Project release 05/08/2019
Reporting period Daily (11 AM to 2 PM)
Work completed this report period
Most of the phases developed for the project are complete. The notebook purchase is completed
and the overall setup is also being established. In addition to this the network, software and
hardware infrastructure setup is completed and presented successfully.
Work to complete next reporting period
In the next reporting period the internet connection set up will be completed and respectively the
testing of the notebook which is not yet been completed would be conducted. It is identified that
if the next reporting period is done with a delay then the buying a notebook project may fail to
meet the consumer’s expectation.

13PROJECT MANAGEMENT
What’s going well and why
As per the primary delivery plan it has been determined that the project is governing towards
correct direction and all the project activities are also successfully getting completed within the
assigned time and budget.
What’s not going well and why
Before final implementation of the project not all the testing approaches are properly followed
and therefore there might be chances of error occurrences.
Suggestions/issues
 Technical training program for the associates
 Proper feasibility analysis
Project changes
 Implementation of proper improvement planning
 Configuration and testing
 Product training
Five risks
 Over allocation of project budget
 Overrunning project timeline
 Lack of business strategies
 Lack of technical knowledge among project supervisor and project team associates
 Insufficient resource allocation

14PROJECT MANAGEMENT
Task 4: Finalization of the project
Date 7/16/2019 Author name <Please fill>
Project release 05/08/2019
Start date 7/16/2019 Finish date 8/02/2019
Application To store and retrieve data from notebook with internet connection
regardless of location and time
The following chart lists the lessons learned for the buying a notebook project. The
project categories are differentiated based on the different project knowledge area.
Procurement management
During the project progress period once the budget get little higher than the preliminary
expectation but with changing time it has been determined that the project run to budget
Scope management
Making measurement with the key performance indicator it is determined that the project has
meet all primary project objectives
Quality management
The project has been completed within the estimated schedule of 14 days or 2 weeks
The project was delivered or completed within estimated time
Project management
From the exercise of project management I have learnt that, different knowledge areas are
available which requires serious attention throughout the project development life cycle period.
If any of these knowledge areas is avoided or overlooked then the entire project will fail to meet
the primary objectives. It is also learnt that, whether the project is governing towards the

15PROJECT MANAGEMENT
objectives or not is measured with the help of Key Performance Indicator (KPI).
Improvements / Recommendations
In order to improve the process some phases those are to be followed include the below:
 Periodic brainstorming session
 Creation of a project charter
 Developing current state process mapping
 Design and development of data sheet
 Design of future state process
 Development of implementation plan

16PROJECT MANAGEMENT
References
Cooper, R. G. 2016. Agile–Stage-Gate Hybrids: The Next Stage for Product Development
Blending Agile and Stage-Gate methods can provide flexibility, speed, and improved
communication in new-product development. Research-Technology Management, 59(1), 21-29.
Czajkowska, A., and Stasiak-Betlejewska, R. 2015. Quality management tools applying in the
strategy of logistics services quality improvement. Serbian Journal of Management, 10(2), 225-
234.
Delerue, H., and Sicotte, H. 2017. Effective communication within project teams: the role of
social media. IAMDC-Wairco, February.
Güngör, D. Ö., and Gözlü, S. 2017. Investigating the Relationship between Activities of Project
Management Offices and Project Stakeholder Satisfaction. International Journal of Information
Technology Project Management (IJITPM), 8(2), 34-49.
Joseph, N. 2017. Conceptualising a multidimensional model of information communication and
technology project complexity. South African Journal of Information Management, 19(1), 1-14.
Kerzner, H., and Kerzner, H. R. 2017. Project management: a systems approach to planning,
scheduling, and controlling. John Wiley and Sons.
Laudon, K. C., and Laudon, J. P. 2016. Management information system. Pearson Education
India.

17PROJECT MANAGEMENT
Pozin, M. A. A., Nawi, M. N. M., and Romle, A. R. 2016. Effectiveness of virtual team for
improving communication breakdown in IBS project delivery process. International Journal of
Supply Chain Management, 5(4), 121-130.
Song, X. (2018, June). A Study on Management Model of Human Resources in Multinational
Companies Based on Cultural Differences--Taking Walmart as an Example. In 2018
International Conference on Sports, Arts, Education and Management Engineering (SAEME
2018). Atlantis Press.
Todorović, M. L., Petrović, D. Č., Mihić, M. M., Obradović, V. L., and Bushuyev, S. D. 2015.
Project success analysis framework: A knowledge-based approach in project
management. International Journal of Project Management, 33(4), 772-783.
Turkulainen, V., Aaltonen, K., and Lohikoski, P. 2015. Managing project stakeholder
communication: The Qstock festival case. Project Management Journal, 46(6), 74-91.
Wu, G., Liu, C., Zhao, X., and Zuo, J. 2017. Investigating the relationship between
communication-conflict interaction and project success among construction project
teams. International Journal of Project Management, 35(8), 1466-1482.