Homework answers / question archive / Southern New Hampshire University IT 261 Final Project Guidelines and Rubric Overview The final project for this course is the analysis of a case study through the lens of a project procurement officer

Southern New Hampshire University IT 261 Final Project Guidelines and Rubric Overview The final project for this course is the analysis of a case study through the lens of a project procurement officer

Management

Share With

Southern New Hampshire University

IT 261 Final Project Guidelines and Rubric

Overview

The final project for this course is the analysis of a case study through the lens of a project procurement officer. You will select one case study from a set of provided cases. You will analyze how the elements of the procurement process address all phases of the expected procurement—conduct, execute, control, and close—and discuss the considerations and analyses that inform the development of a comprehensive procurement management plan.

Every project requires some amount of procurement to support the activities of the project team. The procurement may be purchasing standard products such as computers, software, or furniture used by a website development team. Or the procurement may be more complex, such as the custom development of a new ruggedized, weatherproof, external battery smartphone case. In the former example, the procurement may be highly focused on finding the lowest-cost, compliant supplier. In the latter example, the procurement may focus on finding the most technically competent supplier. As a procurement professional, you must know the preferred methods to satisfy the requirements demanded by both types of projects.

The project is divided into three milestones, which will be submitted at various points throughout the course to scaffold learning and ensure quality final submissions. These milestones will be submitted in Modules Two, Three, and Five. The final project will be submitted in Module Seven.

In this assignment, you will demonstrate your mastery of the following course outcomes:

Select appropriate contract types that align with procurement requirements in maximizing value and minimizing risk for the buyer
Differentiate procurement processes between the United States and international environments in ensuring compliance with local regulations and adherence to best practices
Select appropriate evaluation tools for identifying vendors that best satisfy procurement requirements and provide maximum value
Evaluate contracting decisions for the extent to which they satisfy key procurement principles of value for money, ethics, competition, transparency, and accountability
Assess the components of a procurement management plan for their ability to satisfy the requirements of the project

Prompt

The development of a procurement management plan begins by collecting and analyzing inputs from the project such as, but not limited to, the project scope statement, project schedule, project budget profile, organizational assets (company policies, standard terms and conditions), statement of work, technical specification, and verification requirements. Based on the analysis of project requirements, the type of contract, the bid process, and evaluation process are each defined.

You will analyze and discuss the considerations and choices that inform the development of a procurement management plan that satisfies the procurement scenario described in the selected case study. The analysis should be comprehensive and cover all the considerations of how an effective procurement is executed from initiation to closure.

For this assessment, you will select one Harvard Business Review case study from those presented below, and analyze the case from the perspective of the project’s procurement officer. Ensure the procurement analysis considers all phases of the expected procurement: conduct, execute, control, and close.

Review the description for each of the four choices of case studies available through the links below.

GlaxoSmithKline: Sourcing Complex Professional Services
Harley-Davidson Motor Co.: Enterprise Software Selection
Sher-Wood Hockey Sticks: Global Sourcing
Timberjack Parts: Packaged Software Selection Project

Once you have decided which case to work with, use the links in the Harvard Business Review area of the course to access the case study.

Specifically, the following critical elements must be addressed in your analysis:

I. Overview of Procurement Management Plans

a. Discuss the purpose of a procurement management plan.

b. Define the basic components of a procurement management plan.

c. Explain how each major component of a procurement management plan satisfies the project or organizational requirements in the case study.

II. Contract Types

a. Define each type of contract.

b. Assess contract types for their suitability for different types of projects (construction, design, services, products, etc.).

c. Assess contract types for their ability to maximize value and minimize risk for the buyer.

d. Select the most appropriate contract type(s) for the procurement plan in the case study. Be sure to justify your rationale with research.

III. Procurement Regulations in United States and Abroad

a. Discuss procurement regulations required by local, regional, and federal governments with regard to specific types of procurements executed in the United States (e.g., Manchester, New Hampshire).

b. Discuss procurement regulations required by local, regional, and federal governments with regard to specific types of procurements executed internationally (e.g., Manchester, United Kingdom).

c. Summarize the differences between the domestic and international procurement regulations discussed above.

d. Determine which procurement regulations would apply to the procurement plan in the case study, and explain your reasoning. In other words, will you be required to follow domestic or international regulations, or both? Why?

IV. Source Selection

a. Describe common source selection criteria used to evaluate vendor proposals.

b. Select an appropriate vendor evaluation tool suitable for identifying vendors for the procurement plan in the case study. The tool you select should employ appropriate selection criteria and be capable of producing a summary evaluation score.

c. Assess the vendor evaluation tool produced for its effectiveness in satisfying the project requirements and providing maximum value to the buyer in the case study.

V. Procurement in Practice

a. Summarize the key principles of value for money, ethics, competition, transparency, and accountability.

b. Discuss the importance of the key principles in effective procurement.

c. Evaluate the contracting decisions described in the case study for the extent to which they satisfy key procurement principles of value for money, ethics, competition, transparency, and accountability (i.e., the field situations, situational decision making, etc.).

Milestones

Milestone One: Analysis Overview and Contract Selection

In Module Two, you will submit a document that identifies the case study you selected for analysis from the provided options and begins the first parts of your analysis. Your document should provide an overview meeting all critical elements in Section I of the final project, discussing why and how a procurement management plan would be useful in the procurement scenario selected. Then, considering all critical elements in Section II of the final project, discuss the contract types that could be used to execute the scenario. Select an appropriate contract type for your case study and justify your selection of the chosen contract type. This milestone will be graded with the Milestone One Rubric.

Milestone Two: Procurement Regulations & Source Selection

In Module Three, you will submit a document with more of your analysis for the case study that you selected. First, consider the critical elements in Section III of the final project. Then discuss the impact of government regulations on procurement, the regulatory differences for procurements between the United States and another country, and potential regulatory effects for your selected procurement scenario. Second, consider the critical elements in Section IV of the final project, analyze and choose a set of parameters that you feel are useful for evaluating vendor proposals, develop a vendor evaluation tool, and assess its usefulness for proposal evaluation and selection in your scenario. This milestone will be graded with the Milestone Two Rubric.

Milestone Three: Summary of Procurement Principles

In Module Five, you will submit a document with a summary of the key principles of value for money, ethics, competition, transparency, and accountability, and discuss how a professional procurement process satisfies those principles. You will then apply this knowledge to evaluate the contracting decisions made in the selected case study, following the critical elements in Section V of the final project. This milestone will be graded with the Milestone Three Rubric.

Final Submission: Procurement Analysis

In Module Seven, you will submit a comprehensive analysis of the case study from the perspective of the project’s procurement officer. It should be a complete, polished artifact analyzing all of the critical elements of a procurement management plan as outlined above. It should reflect the incorporation of feedback gained throughout the course. This submission will be graded with the Final Project Rubric.

Final Project Rubric

Guidelines for Submission: Your procurement analysis must be 10-12 pages in length (plus a cover page, table of contents, and references) and must be written in APA format. Use double spacing, 12-point Times New Roman font, and one-inch margins.

Overview

Imagine that you are a help desk service delivery supervisor (HDSDS) for TechWare, a national software company specializing in integrated financial systems. TechWare’s main product is an integrated financial systems software for medium- to large-size enterprises called FinWork. Its software package allows organizations to perform payroll, budgeting, accounting, accounts payable, accounts receivable, cashiering, and other bookkeeping and accounting functions.

The company has over 2,000 clients nationwide and provides fully hosted solutions for approximately 40% of its client base. As part of TechWare’s software support agreement with its clients, each organization is entitled to technical support for their financial software package (FinWorks). Recently, TechWare has received an increasing number of complaints from its clients regarding the level of support received from the help desk on technical issues. Hold times to speak to a technician are longer than before, and help desk requests are also taking longer in general to resolve.

The project is divided into four milestones and a final product, which will be submitted at various points throughout the course to scaffold the learning process leading to a final product. The milestones will be submitted in Modules Three, Four, Five, and Six. The final product will be submitted in Module Seven.

This project will address the following course outcomes:

Establish key performance indicators and acceptable levels of service for given information technology services
Prevent the degradation of service by establishing performance baselines and monitoring service levels
Recommend opportunities for information technology service improvement that ensure alignment to service-level agreements based on measurement of current service levels
Develop plans that will facilitate continuous improvement of information technology service and information technology professional communication
Communicate key information technology concepts and solutions effectively to audiences with various levels of information technology experience

Please utilize your text, course learning resources, the Shapiro Library databases, and other reputable sites on the internet as sources of information.

Preparation

Be sure to read this entire document as well as a more detailed description of the milestones in each respective module.
Review the individual rubrics for specific requirements and expectations.
Review the TechWare Service-Level Agreement document and the TechWare Service Metrics document.
After reviewing the assignment requirements, be sure to consider all of the concepts learned throughout the course when preparing your work. Incorporate these concepts within your project.

Prompt

Your key tasks as supervisor are to evaluate, baseline, and streamline the help desk service currently being provided to clients. You will be responsible for recommending opportunities for service-level improvement that balance the needs of the client with the realities of successfully addressing information technology (IT) issues. Ultimately, you will prepare a detailed presentation to communicate your recommendations to help desk staff, team leads, and management.

Your presentation should address the following prompt: What recommendations would you make to improve the service level and decrease customer complaints? How did you come to these conclusions, and why is it important to address these issues? Remember, you are presenting to your fellow IT team members, and as a supervisor, it is important to inspire your team members to follow your lead. Please note that the course project intent is to introduce students to the ITSM process. For the intended learning and exposure to the course project topics, assumptions can be made and any such assumptions should be documented.

The completed presentation must include all of the critical elements, in order, listed below.

Specifically, the following critical elements must be addressed:

Introduction to your team:
1. Given the client complaints, determine the specific issues that the help desk is facing, and explain how you came to these conclusions.
2. What are some goals and objectives for a successful IT help desk? In other words, what service-level agreement standards or overall service goals need to be attained in order for the help desk to be considered successful?

Describe what key performance indicators (KPI) will be used to measure and track help desk performance.

Describe the importance of client satisfaction as a measure of IT help desk success, specifically for TechWare.

Explain how current help desk service-level baselines will be established. Specifically, how will you determine the current level of service and designate it as acceptable or not acceptable?
1. What stakeholders and user needs should be taken into account?
2. What is considered an acceptable level of service, and should this be static or dynamic?
3. Explain the process you designed for measuring improvement of service. What methods could be used to measure improvements (surveys, call logs, etc.)? Why is measuring performance improvement useful? What is the reasoning behind your process? D. Explain how you plan on monitoring service levels to identify improvements or patterns.

Recommend methods to improve IT service levels to comply with service-level agreements (SLA) provided to clients.
1. Summarize the performance requirements as outlined by the clients’ service-level agreements. Why are these important for determining areas for improvement?
2. Analyze the performance deficiencies and describe their underlying causes. Perform a comparison between current service levels and those described in the service-level agreement.
3. What recommendations can you provide to improve and resolve the help desk service performance concerns?
4. To what extent would the recommendations you had for improving and resolving help desk service performance concerns be enduring? In other words, would your recommendations ensure continuous improvement or static improvement, and why? What could you do to instill the concept of continuous improvement in the work environment?
5. What recommendations can you propose to instill continuous communication improvement within the IT team? For example, how can you monitor or provide in-house training for your team members on ways to communicate with customers?

Communication:
1. Use illustrations, analogies, and other didactic tools to express the technology terms used in your presentation to ensure comprehension by non-technical management staff. Be sure to use the appropriate level of information technology jargon/language to ensure that audiences of varying levels of IT experience can comprehend your proposal to improve service.

Milestones

Milestone One: Introduction

In Module Three, using PowerPoint (or another tool such as Prezi), create the slides and speaker notes for the first section (critical element I) of the final project.

Below are links that offer helpful tips and examples for developing your presentations:

This milestone is graded separately with the Milestone One Rubric.

Milestone Two: Metrics

In Module Four, using the PowerPoint file from Milestone One, create new slides and speaker notes for the second and third sections (critical elements II and III) of the final project. This milestone is graded separately with the Milestone Two Rubric.

Milestone Three: Current Level of Service

In Module Five, using the PowerPoint file from Milestone Two, create new slides and speaker notes for the fourth section (critical element IV) of the final project. This milestone is graded separately with the Milestone Three Rubric.

Milestone Four: Service-Level Agreement

In Module Six, using the PowerPoint file from Milestone Three, create new slides and speaker notes for the fifth section (critical element V) of the course project. This milestone is graded separately with the Milestone Four Rubric.

Final Submission: ITSM PowerPoint Presentation

In Module Seven, using feedback from prior milestones, consolidate and finalize your final project. Be sure to consider the communication requirements (critical element VI) and make appropriate updates to meet these requirements. This submission is graded with the Final Project Rubric.

Deliverables

Milestone	Deliverables	Module Due	Grading
One	Introduction	Three	Graded separately; Milestone One Rubric
Two	Metrics	Four	Graded separately; Milestone Two Rubric
Three	Current Level of Service	Five	Graded separately; Milestone Three Rubric
Four	Service-Level Agreement	Six	Graded separately; Milestone Four Rubric
	Final Submission: ITSM PowerPoint Presentation	Seven	Graded separately; Final Project Rubric

Final Project Rubric

Guidelines for Submission: You have two options for submission of this project:

Submit a PowerPoint presentation (or use another tool such as Prezi): If you choose to submit a presentation, you must include speaker notes. These notes should be written as you would speak to your audience, and they will be used to assess your attention to each of the critical elements listed in the prompt. There are several links provided that will help you create an audience-appropriate presentation and notes.

Presentation Recording: Your second option is to record yourself giving your presentation. You must make sure that each slide of your presentation is visible so that your instructor can view the presentation for evaluation. With this option, you must ensure that the instructor can hear you verbally present your project as well. You may record yourself standing in front of a room (it can even be an empty room) as you work your way through your project (requiring a webcam and recording software, as in this video example ), or you can use tools such as Jing or Camtasia so that you can click through your presentation directly on your computer while capturing your verbal explanations. Using Jing or Camtasia will probably be the easier option for recording your presentation, as it will require less in terms of technology and resources.

Critical Elements	Exemplary (100%)	Proficient (85%)	Needs Improvement (55%)	Not Evident (0%)	Value
Key Issues	Meets “Proficient” criteria and provides specific detail and support regarding the source of the issues	Accurately determines the specific issues that the help desk is facing according to the scenario	Determines the specific issues that the help desk is facing, but with gaps in accuracy or lack of necessary detail around what the scenario indicates	Does not determine the specific issues that the help desk is facing	4
Goals and Objectives	Meets “Proficient” criteria, and established goals show keen insight into the needs of the scenario or provides particularly strong support for the established goals	Establishes and supports reasonable service goals for a successful IT help desk	Establishes goals, but not all goals are reasonable for a successful help desk, or does not provide relevant support for the importance of the established goals	Does not describe what key performance indicators will be used to measure and track help desk performance with adequate detail	6
Key Performance Indicators (KPI)	Meets “Proficient” criteria, and KPIs are particularly relevant given the scenario and can provide the basis for a full plan for improving IT service	Establishes KPIs based on the scenario and identified issues that could be logically used as the basis for improvement of service levels	Establishes KPIs, but not all KPIs are based on the scenario and identified issues, or not all KPIs could be logically used as the basis for service level improvement	Does not establish KPIs	6
Importance	Meets “Proficient” criteria, and support includes exceptional examples with scenariospecific context and professional or scholarly sources that highlight the organizational “big-picture” importance	Describes the importance of client satisfaction as a measure of IT help desk success with relevant support from scenario and external sources	Describes the importance of client satisfaction as a measure of IT help desk success, but lacks relevant support from scenario and external sources	Does not describe the importance of client satisfaction as a measure of IT help desk success	7
Stakeholders and User Needs	Meets “Proficient” criteria, and explanations show keen insight into the end users and stakeholders that must be considered, with specific examples from the scenario	Explains in detail the stakeholders and user needs that should be considered when determining acceptable levels of service	Explains the stakeholders and user needs that should be considered when determining acceptable levels of service, but lacks detail	Does not explain the stakeholders and user needs that should be considered when determining acceptable levels of service	6
Acceptable Level of Service	Meets “Proficient” criteria, and reasoning is driven by the scenario, so all conclusions fall within the appropriate context	Accurately identifies and explains the level and nature (static or dynamic) of acceptable service monitoring with logical reasoning	Identifies and explains the level and nature of acceptable service monitoring, but with gaps in accuracy or logic	Does not identify and explain the level and nature of acceptable service monitoring with logical explanation	6
Measuring Improvement	Meets “Proficient” criteria, and defense of process includes relevant and reliable resources and examples	Establishes and defends the process designed for improving service and the methods that could be used to measure improvements in accordance with established KPIs and acceptable service levels	Establishes and defends the process designed for improving service and the methods that could be used to measure improvements; however, process is not always in accordance with established KPIs and acceptable service levels	Does not establish and defend the process designed for improving service and the methods that could be used to measure improvements	4
Monitoring Service Levels	Meets “Proficient” criteria, and defense includes relevant and reliable resources and examples on how the process would prevent degradation	Establishes and defends a process for monitoring service levels that could prevent the degradation of service	Establishes and defends a process for monitoring service levels, but the process may not prevent the degradation of service	Does not establish and defend a process for monitoring service levels	7
Performance Requirements	Meets “Proficient” criteria and provides specific examples and support from SLA and the scenario	Accurately summarizes the performance requirements as outlined by the clients’ servicelevel agreements (SLAs) and the importance of those requirements for identifying areas for improvement	Summarizes the performance requirements as outlined by the clients’ service-level agreements (SLAs) and the importance of those requirements for identifying areas for improvement, but with gaps in accuracy	Does not summarize the performance requirements as outlined by the clients’ servicelevel agreements (SLAs) and the importance of those requirements for identifying areas for improvement	4
Performance Deficiencies	Meets “Proficient” criteria, and determined deficiencies are supported with information from the scenario	Logically compares current service levels and those described in the service-level agreement to accurately determine areas of performance deficiency	Compares current service levels and those described in the service-level agreement to determine areas of performance deficiency, but with gaps in logic or accuracy	Does not compare current service levels and those described in the service-level agreement to determine areas of performance deficiency	6
Recommendations	Meets “Proficient” criteria and provides specific detail that links the recommendations to the scenario, current service levels, and supporting evidence to formulate logical conclusions	Provides recommendations to address identified deficiencies that could logically improve and resolve the help desk service performance concerns based on current service levels	Provides recommendations to address identified deficiencies based on current service levels, but does not address all of the deficiencies identified, or not all recommendations would logically improve and resolve the help desk service performance concerns	Does not provide recommendations to address identified deficiencies based on current service levels	8
Continuity of Recommendations	Meets “Proficient” criteria, and the accompanying support evidences how and why the recommendations are appropriate for the given scenario	Assesses the extent to which the previous recommendations would be enduring and alters recommendations to ensure continuous improvement of IT service within the scenario environment with support	Assesses the extent to which the previous recommendations would be enduring and alters recommendations, but alterations may not ensure continuous improvement, or there is insufficient support for the assessment of recommendation endurance	Does not assess the extent to which the previous recommendations would be enduring and does not alter the recommendations	8
Continuous Communication Improvement	Meets “Proficient” criteria and provides real-world evidence such as scholarly resources and common management strategies with specific examples	Recommends methods for continuous communication improvement within the IT team based on evidence of prior success and proven strategies	Recommends methods for continuous communication improvement within the IT team, but those methods are not based on prior success or proven strategies	Does not recommend methods for continuous communication improvement within the IT team	8
Illustrations, Analogies, and Jargon	Meets “Proficient” criteria, and communication acts as an example of proper communication within the IT service industry	Uses logical illustrations, analogies, and jargon appropriately to express the technology terms used in the presentation to ensure comprehension by nontechnical management staff	Uses logical illustrations, analogies, and jargon to express the technology terms used in the presentation, but not always appropriately given the non-technical staff needs	Does not use logical illustrations, analogies, and jargon to express the technology terms used in the presentation	10
Articulation of Response	Submission is free of errors related to citations, grammar, spelling, syntax, and organization and is presented in a professional and easy-toread format	Submission has no major errors related to citations, grammar, spelling, syntax, or organization	Submission has major errors related to citations, grammar, spelling, syntax, or organization that negatively impact readability and articulation of main ideas	Submission has critical errors related to citations, grammar, spelling, syntax, or organization that prevent understanding of ideas	10
				Total	100%

Rubric Annotations

Term	Definition/Additional Context
Provides specific detail and support	Such as specifying the result of customer complaints, what is related to communication issues, and how students came to the conclusion based on the scenario information
Particularly strong support	Support evidences both direct relevance to the scenario and insight into the deficiencies/areas of improvement of IT service industry, for example.
Particularly relevant KPIs	KPIs are strong enough to be used as the basis for the plan for improvement and the guidelines for measuring progress and align to the organizational mission and standards.
“Big-picture” importance	Not only are the description and support relevant for the particular scenario and IT service, but they also highlight the importance of service levels for the overall organization. Basically, students are able to view from the “management” perspective of IT service.

Option 1

Low Cost Option

Download this past answer in few clicks

27.99 USD

PURCHASE SOLUTION

Already member? Sign In

Option 2

Custom new solution created by our subject matter experts

GET A QUOTE

GLAXOSMITH.pdf

QSO_349_Project_Guidelines_and_Rubric.pdf

rated 5 stars

Purchased 3 times

Completion Status 100%

Google (5.0)

Southern New Hampshire University IT 261 Final Project Guidelines and Rubric Overview The final project for this course is the analysis of a case study through the lens of a project procurement officer

Management

Overview

Preparation

Prompt

Milestones

Deliverables