Project Initiation Phase-life cycle

Project Initiation Phase-life cycle

The Value of Developing a Business Case in Projects

A business case is developed as a justification for a project to solve the identified problem. A business case captures a record of the decisions made by governance regarding how to realize benefits from an investment in a certain project. The business case outlines the opportunities organizations should capitalize on, the risks that need to be suppressed, available threats, the project stages, and the implementation plan summary (Henrie & Sousa-Poza, 2005). In this regard, the business case documents all the options considered and their rationale and evidence to support the decisions made. Therefore, a business case is important because it combines investment appraisal with evidence of how the investment is designed to realize intended benefits (Henrie & Sousa-Poza, 2005).

Types of Requirements

The two basic requirements of a project are functional and non-functional requirements. Functional requirements are the features or functions of a product that project managers must implement for the product or service to accomplish their respective tasks. On the other hand, non-functional requirements are the qualities the product should possess; but mostly from the aesthetic component (Henrie & Sousa-Poza, 2005). There are also business requirements that inform why the project is happening. The business requirement is often the project’s starting point and offers guidance for the other requirements. The last category of requirement is the stakeholder requirement. A stakeholder is an individual interested in the service or product being produced. The stakeholders may either be internal or external. Internal stakeholders include mostly employees, while external stakeholders include regulators, customers, or suppliers (Henrie & Sousa-Poza, 2005). Every stakeholder has individual requirements that they look forward for them to be fulfilled.

The Significance of Including the User Experience (UX)

User experience refers to an individual’s feelings while interacting with a system. The system, in this case, could be a website, mobile application, or even desktop software. User experience is important in managing information technology because it tries to fulfill users’ needs (Djamasbi et al., 2014). It focuses on providing positive experiences that keep users loyal to the product or brand in question. The UX design process involves the user persona, identification of the problem, outlining the strategy, objectives, and features, and finally, the solution (Djamasbi et al., 2014). Some methods for developing user experience include job interviews, functionality maps, wireframes, or prototyping.

References

Djamasbi, S., McAuliffe, D., Gomez, W., Kardzhaliyski, G., Liu, W., & Oglesby, F. (2014). Designing for success: Creating business value with mobile user experience (UX). In International conference on HCI in Business (pp. 299-306). Springer, Cham.

Henrie, M., & Sousa-Poza, A. (2005). Project management: A cultural literary review. Project Management Journal, 36(2), 5-14.

ORDER A PLAGIARISM-FREE PAPER HERE

We’ll write everything from scratch

---

Project Initiation Phase https://archive.org/details/project-management-101
The project initiation phase is the first phase within the project management life cycle, as it involves starting up a new project. Within the initiation phase, the business problem or opportunity is identified, a solution is defined, a project is formed, and a project team is appointed to build and deliver the solution to the customer. A business case is created to define the problem or opportunity in detail and identify a preferred solution for implementation. The business case includes:

A detailed description of the problem or opportunity
A list of the alternative solutions available
An analysis of the business benefits, costs, risks and issues
A description of the preferred solution
A summarized plan for implementation
About Requirements – More than half of the errors in a project originate with the requirements and analysis activities done prior to product design. Requirements are the heart of any project. They describe what the outcome of a project must be, what it must do, or the qualities it must have. In order to be successful, the project manager and his or her team need to identify and manage the project requirements. However, knowing that one must identify and manage the project requirements and actually doing so are two different things. Most projects fail as a result of incomplete requirements, poorly written requirements or misinterpreted requirements.
Discussion Points:

What is the value of developing a Business Case in project?

Discuss the various types of Requirements.
Address the significance of including the User-Experience (UX) in making project management as it applies to managing information technology.