QSO 355 Final Project Part 1 PDF

Preview

Summary

Assignments for SNHU course work from 2020-2022 academic year. All work submitted align with BS Business w/concentration on Project Management....

Description

Running head: 6-1 Final Project

1

6-1 Final Project Zachary Miller Southern New Hampshire University

Final Project

2 Table of Contents

I. II.

III.

IV. V. VI.

Introduction Project Overview A. Roles and Responsibilities B. Scope and Schedule Tasks A. Description B. Time C. Dependencies Resources A. Alignment B. Evaluation Risk A. Sources B. Strategies Budget Schedule

Introduction Purpose: Looking at A&D history, they are a very successful company although they started to fall behind competitors when it came to online shopping. According to Jeffery, “In early May 2003 Johnson received an urgent message from the company’s CIO, Matt Webb. Webb asked Johnson to join him for a meeting with A&D’s senior managers to discuss taking over the company’s

Final Project

3

online store project” (page 2, 2019). Therefore, the purpose of this paper is to help A&D come up with a plan and implement it in time for them to sell their products online before the upcoming holidays. Background Information: A&D High Tech initially started in Lincoln, Nebraska where their main target group was small businesses. A&D supplied computer products, accessories, and provided service to customers. Jeffery mentions in his article that “Ted Walter started its first store in 1988. A&D’s made-to-order products were very innovative at the time, and were the first to be introduced in the personal computer industry… In 1999 A&D implemented its first enterprise resource planning (ERP) system, using software from J. D. Edwards. A&D opted to use J. D. Edwards primarily because its software could be customized to handle the thousands of parts that A&D used for production” (page 2, 2019). A few years later, A&D realized how successful it was to implement the ERP, which resulted in more change within the company. Some of the other examples of changes implemented after ERP were improving its systems in handling the supply chain, payment process, customer relationship management (CRM), and order management. Overall, after all of these changes were made, A&D noticed a dramatic change in costs as well as a significant return on investment on its supply chain and data warehousing projects. In the end, after noticing the beneficial aspects of these changes, A&D needs to focus heavily on the next big thing which is having the ability to operate on online store. Project Overview In order for A&D to stay competitive in this market field, they are deciding to offer the ability to purchase their products online. The biggest benefits from this is it will expand their

Final Project

4

business as the premier technology provider from the Midwest to worldwide and will set itself apart from any competitor. The main purpose of this section is to define the key people in this project along with their roles and responsibilities, discover the scope of the project, and finally the completion timeline. Below I described the roles and responsibilities, the scope, and the timeline for the project in an Excel document.

Scope and Schedule

Stakeholder Analysis Project Name: Project Manager:

A&D High Tec Chris Johnson

Project #: unsure I looked in the case study but could not find anything. Sponsor: Ted Walter Updated: unsure I looked in the case study but could not find anything.

Scope: The overall scope of this project is to implement a functional online system that will allow customers to shop. By doing this it will have a direct result in the influx of a customer base along with growth in sales. The project will kick off on May 2003, and the deadline for the project will be November 2003. To accomplish the timeline, A&D needs to stay up to date on their “building system requirements, software requirements, a detailed design, test planning, technical infrastructure, development and unit test, testing, and deployment” (Jeffrey, 2019). The final step in the scope will be tasking an engineer to put everything together to ensure the orders and the fulfillment of them will be completed and function properly. Schedule: When it comes to the timeline and completion of each step within the allotted time, it is extremely important that it be followed as strictly as possible. They do not want anything that

Final Project

5

could interfere with it due to the strict deadline of being up and running by the holidays. They need to do whatever possible to avoid any kind of scope creep. A good way to make sure this is being accomplished is having steps that are similar within the project being worked at the same time, that way they can save that time where possible. An example of this would be having all the system and software individuals working together that way they all can be on the same page. Looking at the WBS of the project in the case study, it seems like this deadline will be meet within the given timeframe. According to the PMBOK WBS can be defined as “deliverable oriented hierarchical decomposition of the work to be executed by the project team. The work breakdown structure visually defines the scope into manageable chunks that a project team can understand, as each level of the work breakdown structure provides further definition and detail” (2017). Overall, the PM in this case did a great job by dividing the project up into sub-categories with descriptions of whatever resources they will need to complete the project clearly shown. Task As mentioned previously, WBS can be defined according to the PMBOK as “deliverable oriented hierarchical decomposition of the work to be executed by the project team. The work breakdown structure visually defines the scope into manageable chunks that a project team can understand, as each level of the work breakdown structure provides further definition and detail” (2017). Looking at the A&D project, it has been broken down into nine sections that need to be completed with several sub categories under those nine as well. Below is a chart that will describe each of the nine task that needs to be completed along with the timeframe of each and the dependencies. “Dependencies are the relationships among tasks which determine the order in which activities need to be performed. There are four (4) types of dependency relationships, finish to start, start to start, finish to finish, and start to finish” (Project Insight, n.d).

Final Project

6 Alignment

Task ID 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21

WBS Code 1 1.1 1.1.1 1.2 1.2.1 1.2.2 1.2.3 1.2.4 1.2.5 1.3 1.3.1 1.3.1.1 1.3.1.2 1.3.1.3 1.3.1.4 1.3.1.5 1.3.1.6 1.3.2 1.3.3 1.3.4 1.4 1.4.1

22 1.4.2 23 1.4.3 24 1.4.4 25 26 27 28 29 30 31 32 33 34

1.4.5 1.4.6 1.4.7 1.4.8 1.5 1.5.1 1.5.2 1.5.3 1.6

Task Name Overall Project Project Management Manage Project System Requirements Gather Business Requirements Design Business Process Flows Finalize Technical Requirements Create Operational Requirements Identify Technical Infrastructure Needs Software Requirements Create Functional Requirements Capture Customer Profile View and Search Product Catalog Updating and Calculating Shopping Cart Taking Payments Submit Order Check Order History & Order Status Create Data Requirements Create ERP Interface Requirements Create User Interface Requirements Detailed Design Design Capture Customer Profile Page & Components Design View and Search Product Catalog Page & Components Design Updating and Calculating Shopping Cart Design Taking Payments Page & Components Design Submit Order Page & Components Design Check Order History & Order Status Page & Components Design Logical and Physical Data Model Design ERP Interface Test Planning Gather Testing Requirements Create System Test Plan & Test Cases Write System Test Scripts Technical Infrastructure

Time (Days )

Dependencies

127 8 4 6 15 2

5 5, 6 7, 8 5, 6 ,8

4 6 3 6 4 3 3 7 4

13 12, 13, 14, 15 16 12,13

10 13.5 13.5 6

23

6 16

22, 23, 24, 25

4 18 20

26

14 20 22

11 31, 21 32

22, 23, 24, 25

Final Project 35 36 37

7 1.6.1 1.6.2 1.6.3 1.6.4

38 39 40

1.6.5 1.7

41

1.7.1

42

1.7.2

43

1.7.3

44 45

1.7.4 1.7.5

46 47 48 49 50 51 52

1.7.6 1.7.7 1.7.8 1.7.9 1.8 1.8.1 1.8.1.1

Create Development Environment Create Testing Environment Support Development Environment Support Testing Environment & Deployment Support Database Development & Unit Test Build Capture Customer Profile Page & Components Build View and Search Product Catalog Page & Components Build Updating and Calculating Shopping Cart Build Taking Payments Page & Components Build Submit Order Page & Components Build Check Order History & Order Status Page & Components Build Logical and Physical Data Model Build ERP Interface Support Development & Assembly Test Testing Perform Assembly Testing Perform Phase 1 Testing

53 54 55 56 57 58 59

1.8.1.2 1.8.2 1.8.3 1.9 1.9.1 1.9.2 1.9.3

Perform Phase 2 Testing Perform System Testing Perform Validation Testing Deployment Implement System Deploy to Production Project Wrap-up

20 34.2 3.8

9 35 35

46 4.6

36 47 35

13

22

12

23

7

24, 42

6 24

25 26, 41, 42

6 15.5 18 46

43, 44 28 29 21

20 160 80

12

80 8 90

31 41, 42, 42 44, 45, 46, 52, 47, 48 51, 32, 33 54 50 57 58

Evaluation Looking at the information given to us in the case study on A&D, there are a substantial amount of resources in order to complete the project within the given timeframe. Another benefit I see in the WBS is the numerous task that can be completed at the simultaneously. Due to the number of people in that field, it may result in a speedier finish for the project. The only issue

Final Project

8

residing within the project is the few unknown contributors. The reason for this is because it is unknown who they are along with the skill set they offer to the project. However, this may result in their benefit because some projects that will take longer will be able to be handed off to them if their skill set fulfills the requirements. Risk

A risk can be anything that can cause a harmful impact when it comes to your projects timeline, the performance of the project, or the budget of the project. According to Ray, “Project risk management is the process of identifying, analyzing and then responding to any risk that arises over the life cycle of a project to help the project remain on track and meet its goal. Risk management isn’t reactive only; it should be part of the planning process to figure out risk that might happen in the project and how to control that risk if it in fact occurs… risks are potentialities, and in a project management context, if they become realities, they then become classified as “issues” that must be addressed. So risk management, then, is the process of identifying, categorizing, prioritizing and planning for risks before they become issues.” (2017). In order for risks to be eliminated, PM’s need to clearly identify the risk managers in the opening explanation of each individual project. However, their responsibilities will start in that phase and will continue to resurface throughout the entirety of the project until it is finalized. By doing this, the risk managers will be able to document any risk factors that surface during the process, brief them accordingly, and evaluate them in order to make sure they do not occur again during future projects. The risk in projects can differ depending whether or not it is a large scale project or a small scale project. According to Ray, “On large-scale projects, risk management strategies might include extensive detailed planning for each risk to ensure mitigation strategies are in

Final Project place if issues arise. For smaller projects, risk management might mean a simple, prioritized list of high, medium and low priority risks” (2017). In the end, no matter the size of the project, risk managers have one goal and that is to eliminate any issues or risks that may surface during the project. Below is a risk chart for the risk/strategy for A&D High Tech Online Store.

9

Final Project

10

Final Project

11 Budget Se

QSO 355 Budget Sheet.xlsx

e link above to full Excel Document as shown to the right.

Final Project

12 Schedule

Final Portion of Final Project .xlsx

Figure 1: Final Portion of Final Project Please refer to attached XLS file above as it is sub-located for reference via above linked object.

Final Project

13

References: Jeffery, M. (2019). A&D High Tech (A): Managing Projects for Success. Kellogg School of Management. Project Insight. (n.d.). Retrieved March 19, 2019, from https://www.projectinsight.net/projectmanagement-basics/task-dependencies Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide)–Sixth Edition (Vol. Sixth edition). Newtown Square, PA: Project Management Institute. Retrieved March 19, 2019, from http://ezproxy.snhu.edu/login?url=https://search.ebscohost.com/login.aspx?direct=true&d b=nlebk&AN=1595320&site=eds-live&scope=site Ray, S. (2019, March 18). The Risk Management Process in Project Management. Retrieved March 26, 2019, from https://www.projectmanager.com/blog/risk- management-processsteps

Final Project

14...