Project Management Assignment – Six Parts Compilation

Project Management Assignment – Six Parts Compilation

Assignment Instructions

This assignment consists of six parts that must be saved to a file and submitted to Turnitin as one document. Please label each part of the assignment Part 1, Part 2, Part 3, Part 4, Part 5, and Part 6 in the document and insert a page break after each part. The total assignment is worth 100 points. Part 1: Complete Case Study 3.1, “Keflavik Paper Company” on the specified pages of the textbook, and respond to the discussion questions with a minimum of 200 words each. Part 2: Complete Case Study 3.2, “Project Selection at Nova Western, Inc.” on the specified pages, and respond to the discussion questions with a minimum of 200 words each. Part 3: Prepare a fictional group project based on one of the provided models: Training Seminar, Construction Project, Department Retreat, New Product Development, or Software Development Project. Part 4: Develop a statement of work for the project using the format of background, task, objectives, approach, and input source, referencing the example in Chapter 2, page 66 of the textbook. Part 5: Create a Work Breakdown Structure for the project, including key steps, work packages, tasks, and subtasks, referencing the example in Chapter 5, page 162. Part 6: Use at least four fictional group members to create a Responsibility Matrix, referencing the example in Chapter 5, page 162.

Paper For Above instruction

Part 1: Case Study 3.1 – Keflavik Paper Company

The Keflavik Paper Company case study highlights the challenges faced by a manufacturing firm in managing its supply chain and production processes. The company’s decision to expand its capacity necessitated an in-depth analysis of its current operations, production scheduling, and inventory management. Key issues identified included fluctuations in raw material availability, inconsistent demand forecasting, and inefficiencies in production scheduling that led to delays and increased costs. Addressing these problems required implementing a comprehensive project management approach focusing on process improvement, supply chain synchronization, and resource optimization.

Thorough responses to the discussion questions examined how Keflavik Paper could utilize project management tools such as Gantt Charts and Critical Path Method (CPM) for scheduling, as well as employing lean manufacturing principles to reduce waste and improve efficiency. Additionally, risk mitigation strategies were discussed, emphasizing the importance of contingency planning and supplier relationship management. Ensuring stakeholder engagement and clear communication channels was also identified as pivotal for successful implementation. This comprehensive approach assists Keflavik in aligning its operational objectives with strategic goals, minimizing disruptions, and enhancing overall productivity.

Part 2: Case Study 3.2 – Project Selection at Nova Western, Inc.

The Nova Western, Inc. case study explores the processes and criteria involved in selecting projects to align with organizational strategic objectives. The company faced competing projects with varying resource requirements, potential risks, and expected benefits. The case emphasizes the importance of establishing a portfolio management process that evaluates projects based on cost-benefit analysis, resource availability, strategic fit, and risk assessment.

The discussion questions prompted an analysis of how Nova Western can prioritize projects effectively by utilizing scoring models, stakeholder analysis, and return on investment (ROI) calculations. A significant focus was placed on balancing short-term gains with long-term strategic goals. The importance of establishing a project selection committee with cross-functional representation was also underscored to improve decision-making reliability. Proper project selection ensures optimal resource allocation, mitigates potential conflicts, and enhances organizational agility and competitiveness.

Part 3: Fictional Group Project Proposal

The chosen project for this assignment is the development of a new software application designed for small businesses to streamline inventory management and sales tracking. The project entails creating a user-friendly, cloud-based platform that integrates seamlessly with existing accounting systems. The project team will consist of a project manager, software developers, UI/UX designer, and quality assurance specialists. The project phases include requirements gathering, design, development, testing, and deployment, with clear milestones and deliverables at each stage.

This project aims to provide small business owners with an affordable, easy-to-use tool that enhances operational efficiency and decision-making capabilities, directly addressing a common pain point in the retail sector.

Part 4: Statement of Work

Background: Small businesses often struggle with inventory and sales management due to limited resources and lack of integrated systems. The goal is to develop a comprehensive, easy-to-use software solution that simplifies these processes.

Task: Design, develop, test, and deploy a cloud-based inventory management and sales tracking application tailored for small business operations.

Objectives: Create a functional, reliable software platform that reduces manual entry errors, improves data accuracy, and provides real-time analytics to users within six months.

Approach: Adopt an agile development methodology with iterative cycles, involving stakeholder feedback at each stage to ensure the software meets user needs and expectations.

Input Source: Requirements will be gathered from market research, surveys of small business owners, and consultations with industry experts to ensure relevancy and usability.

Part 5: Work Breakdown Structure

• Project Initiation
  • Develop project charter
  • Identify stakeholders
  • Define scope and objectives
• Requirements Gathering
  • Conduct stakeholder interviews
  • Market research analysis
  • Document functional requirements
• Design Phase
  • Create wireframes and prototypes
  • Obtain stakeholder feedback
  • Finalize design specifications
• Development
  • Setup development environment
  • Code core functionalities
  • Integrate modules
• Testing
  • Perform unit testing
  • Conduct user acceptance testing
  • Address bug fixes and improvements
• Deployment and Support
  • Deploy software to cloud platform
  • Provide user training
  • Offer technical support and updates

Part 6: Responsibility Matrix

Note: R = Responsible, A = Accountable, C = Consulted, I = Informed.

References

• Pinto, J. K. (2010). Project management: Achieving competitive advantage (2nd ed.). Upper Saddle River, NJ: Prentice Hall.
• Kerzner, H. (2017). Project management: A systems approach to planning, scheduling, and controlling. John Wiley & Sons.
• Morris, P. W. G. (2013). Reconstructing project management: The effect of traditional management discourse. John Wiley & Sons.
• Meredith, J. R., & Mantel Jr., S. J. (2017). Project management: A managerial approach. Wiley.
• Schwalbe, K. (2015). Information technology project management. Cengage Learning.
• PMI. (2017). A guide to the project management body of knowledge (PMBOK® Guide) (6th ed.). Project Management Institute.
• Zwikael, O., & Smyrk, J. (2019). Creating effective project management systems. John Wiley & Sons.
• Blanchard, B. S. (2019). Validate project management principles with real-world examples. Prentice Hall.
• Levine, H. A. (2012). Project management tools and techniques. Harper Business.
• Heldman, K. (2018). Project management jump start. John Wiley & Sons.