Developing a SmartWatch System: Professional Practice in IT Project

This project assignment focuses on the practical application of IT professional practice through the development of a SmartWatch system. The project encompasses various stages, including the creation of a scope statement outlining project justification, major deliverables, success criteria, and constraints. The assignment further details project planning with a Gantt chart illustrating task durations and dependencies, alongside a work breakdown structure. Stakeholder analysis is also included, identifying stakeholders, their likely issues, and the positive impacts of the project on them. The project also addresses project management aspects, such as change management, risk management, communication, and quality assurance, culminating in a comprehensive project plan. The assignment also includes brainstorming sessions and vendor selection process. The project aims to develop leadership and management skills and promotes the use of technology for health and fitness.

Running head: PROFESSIONAL PRACTICE IN IT
Professional Practice in IT
Name of Student-
Name of University-
Author’s Note-

1PROFESSIONAL PRACTICE IN IT
1. Tutorial 2 Activity 4: Scope Statement
Project Title: Developing a SmartWatch System
Date: Prepared by:
Project Justification:
The project described in this project is to develop an application system of SmartWatch
system that will have a camera and a GPS to track the intake of food of the user who is
wearing the watch.
This project is important as with the development of this project, the users will get to
know the amount of food that is taken by the user. This project is trying to develop
leadership and management skills in the project developer and with the development of
the system, the users can keep themselves fit.
Major Deliverables:
This project will state the phases included for developing the system of SmartWatch
system. There are many activities included for completing the development process of the
application, all those development will be schedule in this project. This project also helps
to schedule the time included in the project and aims to manage all the tasks. The
developer also helps to develop the project resources included in the system.
Project Success Criteria:

2PROFESSIONAL PRACTICE IN IT
With the allocated time and proper schedule, the project gets successful. The project of
developing the SmartWatch is dividing the project in to many small sections so that the
team members are able to achieve the target within specified time and the schedule given.
The success rate of the project is high as the scheduled budget and time is decided in the
project.
Constraints and Assumptions:
The project time frame included in the project is two years and developers are expecting
the project fund from the grant scheme of the University. The budget of the project that is
$411,280 as developed in the project.
The project plan that is done in this project done using the MS Project software.
For completing this project, many other project management books and articles will be
reviewed so that the concept of managing the project gets clear.

3PROFESSIONAL PRACTICE IN IT
2. Tutorial 3 Activity 3: Gantt chart of developing a SmartWatch System

Running head: PROFESSIONAL PRACTICE IN IT
3. Tutorial 4 Activity 4: Gantt chart of Literature Review assignment
Work Breakdown Structure

Running head: PROFESSIONAL PRACTICE IN IT
Task Durations
Task Name Duration Start Finish
Project Management Work plan 80 days Tue 12/04/16 Mon 1/08/16
Initiation Phase 13 days Tue 12/04/16 Thu 28/04/16
Requirements Gathering & Analysis 4 days Tue 12/04/16 Fri 15/04/16
Define process for gathering
requirements
1 day Tue 12/04/16 Tue 12/04/16
Document project-stakeholder
interviews
1 day Wed 13/04/16 Wed 13/04/16
Analyze requirements 1 day Thu 14/04/16 Thu 14/04/16
Create requirements document 1 day Fri 15/04/16 Fri 15/04/16
Project Charter Development 10 days Fri 15/04/16 Thu 28/04/16
Business Case 2 days Fri 15/04/16 Mon 18/04/16
Document summary of business
purpose justification
2 days Fri 15/04/16 Mon 18/04/16
Define expected benefits 2 days Fri 15/04/16 Mon 18/04/16

1PROFESSIONAL PRACTICE IN IT
Project Scope Definition (High Level) 8 days Tue 19/04/16 Thu 28/04/16
Define primary market research
objectives
3 days Tue 19/04/16 Thu 21/04/16
Define primary market research
deliverables
2 days Fri 22/04/16 Mon 25/04/16
Identify specific exclusions to scope 2 days Fri 22/04/16 Mon 25/04/16
Establish high-level time, cost, and
resource estimates
2 days Tue 26/04/16 Wed 27/04/16
Establish list of key stakeholders 2 days Tue 26/04/16 Wed 27/04/16
Document project charter 1 day Thu 28/04/16 Thu 28/04/16
Project Charter Approval 0 days Thu 28/04/16 Thu 28/04/16
Initiation Phase Approval 0 days Thu 28/04/16 Thu 28/04/16
Planning Phase 32.5 days Fri 29/04/16 Tue 14/06/16
Project Plan Development 32.5 days Fri 29/04/16 Tue 14/06/16
Scope Statement 4 days Fri 29/04/16 Wed 4/05/16
Create scope description (based on
business objectives)
2 days Fri 29/04/16 Mon 2/05/16

2PROFESSIONAL PRACTICE IN IT
Define scope boundaries (both in and
out of scope)
2 days Fri 29/04/16 Mon 2/05/16
Define key project deliverables
(including user-acceptable criteria)
2 days Tue 3/05/16 Wed 4/05/16
Work Breakdown Structure (WBS) 4 days Thu 5/05/16 Tue 10/05/16
Create WBS to work-level execution 2 days Thu 5/05/16 Fri 6/05/16
Define task dependencies (including
predecessors/successors)
2 days Mon 9/05/16 Tue 10/05/16
Performance Baseline Measurement 2 days Wed 11/05/16 Thu 12/05/16
Create schedule baseline (with
expected resource effort)
1 day Wed 11/05/16 Wed 11/05/16
Define budget baseline (with schedule
and cost assumptions)
1 day Thu 12/05/16 Thu 12/05/16
Establish baseline tolerance
thresholds (trigger change control)
1 day Thu 12/05/16 Thu 12/05/16
Procurement Planning (Research
Vendor Selection)
8 days Thu 5/05/16 Mon 16/05/16
Analyze market conditions 1 day Thu 5/05/16 Thu 5/05/16
Analyze make-or-buy findings 2 days Fri 6/05/16 Mon 9/05/16

3PROFESSIONAL PRACTICE IN IT
Select contract type 1 day Tue 10/05/16 Tue 10/05/16
Develop procurement management
plan
2 days Wed 11/05/16 Thu 12/05/16
Develop statement of work 2 days Fri 13/05/16 Mon 16/05/16
Project Schedule Plan 2.5 days Fri 13/05/16 Tue 17/05/16
Project Milestones (PMs) 0.5 days Fri 13/05/16 Fri 13/05/16
Define major milestones (alignment
with deliverables)
0.5 days Fri 13/05/16 Fri 13/05/16
Project Scheduling Work Plan 2 days Fri 13/05/16 Tue 17/05/16
Define standard PM and approval
gates
0.5 days Fri 13/05/16 Fri 13/05/16
Document WBS, milestones, and
deliverables (dates and resourcing)
2 days Fri 13/05/16 Tue 17/05/16
Document schedule baseline 1 day Fri 13/05/16 Mon 16/05/16
Resource Management 2 days Mon 16/05/16 Wed 18/05/16
Name project team members (with
roles and responsibilities)
2 days Mon 16/05/16 Wed 18/05/16

4PROFESSIONAL PRACTICE IN IT
Define all project stakeholders (with
roles and project team liaison)
2 days Mon 16/05/16 Wed 18/05/16
Create org chart: project team,
sponsor, steering committee, stakeholders
2 days Mon 16/05/16 Wed 18/05/16
Supporting PM Process Plans 19 days Wed 18/05/16 Tue 14/06/16
Change Management 4 days Wed 18/05/16 Tue 24/05/16
Document change control procedure
for budget and schedule baselines
2 days Wed 18/05/16 Fri 20/05/16
Document change control for
approved scope baseline
2 days Wed 18/05/16 Fri 20/05/16
Document change control for
systems modifications
2 days Fri 20/05/16 Tue 24/05/16
Risk Management 4 days Tue 24/05/16 Mon 30/05/16
Document risk process:
prioritization, mitigation, and contingency
guidelines
2 days Tue 24/05/16 Thu 26/05/16
Document risk assessment for
scope, budget, and schedule baselines
2 days Thu 26/05/16 Mon 30/05/16
Issues Management 2 days Mon 30/05/16 Wed 1/06/16

5PROFESSIONAL PRACTICE IN IT
Document issues process:
prioritization, resolution, and tracking
guidelines
2 days Mon 30/05/16 Wed 1/06/16
Document formal 3-tiered
escalation: project manager, sponsor, and
executives
2 days Mon 30/05/16 Wed 1/06/16
Communication Plan 4 days Wed 1/06/16 Tue 7/06/16
Document guidelines: project
updates and stakeholder collaboration
2 days Wed 1/06/16 Fri 3/06/16
Document guidelines for document
repository access and controls
2 days Wed 1/06/16 Fri 3/06/16
Document standard project team
and executive status report guidelines
2 days Fri 3/06/16 Tue 7/06/16
Quality Assurance and Control
Plan
5 days Tue 7/06/16 Tue 14/06/16
Define criteria for user-acceptance
testing (with checklist)
2 days Tue 7/06/16 Thu 9/06/16
Define criteria for cost/benefit
analysis
2 days Tue 7/06/16 Thu 9/06/16
Define criteria and process for 2 days Tue 7/06/16 Thu 9/06/16

6PROFESSIONAL PRACTICE IN IT
periodic stakeholder satisfaction survey
Define criteria for "Lessons
Learned" (during closeout)
2 days Tue 7/06/16 Thu 9/06/16
Create Draft Project Plan 3 days Thu 9/06/16 Tue 14/06/16
Project Plan Approval 0 days Tue 14/06/16 Tue 14/06/16
Planning Phase Approval 0 days Tue 14/06/16 Tue 14/06/16
Execution Phase 80 days Tue 12/04/16 Mon 1/08/16
Brainstorming Marketing Idea 80 days Tue 12/04/16 Mon 1/08/16
Prep Work 3.25 days Tue 14/06/16 Fri 17/06/16
Define objectives 1 day Tue 14/06/16 Wed 15/06/16
Identify brainstorming team 0.5 days Wed 15/06/16 Wed 15/06/16
Identify location 0.25 days Thu 16/06/16 Thu 16/06/16
Develop agenda 1 day Thu 16/06/16 Fri 17/06/16
Schedule facility 0.25 days Fri 17/06/16 Fri 17/06/16
Arrange facilitator 0.25 days Fri 17/06/16 Fri 17/06/16
Brainstorming Session 5 days Fri 24/06/16 Fri 1/07/16
Analyze market condition 0.5 days Fri 24/06/16 Mon 27/06/16
Identify risks 1 day Mon 27/06/16 Tue 28/06/16