Select The Best Answers For The Questions

Select The Best Answers For The Following Questions

Directions: Select the best answers for the following questions. Choose the appropriate options based on the WCMI case study and general project management principles for developing a business case, planning, and understanding potential project failures.

Paper For Above instruction

The process of developing a business case involves multiple sequential steps to justify an investment in an enterprise system. The first step typically involves identifying the core business need that the system aims to address, followed by defining clear business objectives that align with organizational goals. Subsequently, evaluating whether to buy a pre-existing solution or build a custom one (buy vs. build) is crucial, alongside estimating costs associated with the project, such as total cost of ownership (TCO) and infrastructure expenses. Detailing the benefits and potential return on investment (ROI) helps articulate the value proposition, while considering other impacts and implementation issues ensures comprehensive planning. It is also vital to review alternative solutions considered and formulate a proposed solution that best satisfies the organization's needs. In some cases, quick fixes might be considered, though they often do not offer long-term solutions.

From the WCMI case study, it is important to include specific items that support each area of the business case. For the 'business need', items such as adopting RFID technology and consolidating manufacturing and sales capabilities are pertinent, as they directly relate to operational improvements and strategic growth. For defining 'business objectives', focusing on completing accurate management decision-making information and expanding manufacturing capabilities in the U.S. are critical objectives. When estimating costs, infrastructure TCO and data standardization are significant factors, and for the 'proposed solution', selecting an integrated ERP system like SAP is relevant. To detail benefits, the increased value of sales can be highlighted, and addressing additional impacts involves considering other implementation and impact issues.

Developing the original project plan requires a structured approach, including tasks such as defining scope and requirements, planning resource allocation, and initiating project activities. Tools like process reengineering (BPR) or closeout procedures may also be used, depending on the project's phase. Task selection must align with project phases, emphasizing comprehensive scope definition, planning, execution, and control. Some tasks like reporting, review, and startup are integral for monitoring progress and ensuring project alignment with goals.

As a CEO interviewing project manager candidates, essential characteristics include strong influence, problem-solving skills, and self-management abilities. While experience and achievement are valued, qualities like leadership, adaptability, communication skills, and the capacity to manage teams and project complexities are particularly vital for successful project execution.

Although detailed project planning helps mitigate risks of failure, it cannot eliminate them. Common issues that contribute to project failure include lack of executive commitment, unrealistic expectations from management or users, premature commitment to budgets and schedules, overly optimistic projections, insufficient resource allocation, ineffective people management, and failure to adapt to changing business environments. Recognizing these risk factors enables better planning and risk mitigation strategies.

References

• Whitten, J. L., & Bentley, L. D. (2008). Systems analysis and design methods. McGraw-Hill Education.
• Schwalbe, K. (2015). Information Technology Project Management. Cengage Learning.
• PMI. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide). Project Management Institute.
• Kerzner, H. (2017). Project Management: A Systems Approach to Planning, Scheduling, and Controlling. Wiley.
• McConnell, S. (1996). Software project survival guide. Microsoft Press.
• Standish Group. (2015). CHAOS Report. The Standish Group International.
• Meredith, J. R., & Mantel, S. J. (2014). Project Management: A Managerial Approach. Wiley.
• Dennis, A., Wixom, B. H., & Roth, R. M. (2018). Systems Analysis and Design. Wiley.
• Davis, K. (2014). Managing Business Process Flows. Springer.
• Engwall, M. (2003). No project is an island: linking projects to history and context. Research Policy, 32(5), 789-808.