Introduction
This essay will talk about the backbone of a project: the business case theme. The business case theme is firmly related to the continued business justification principle. As Turley states (2010), this principle recommends that before and during a project we should evaluate whether the project is desirable, viable and achievable. It signifies that the project needs to be profitable and the use of time and resources should be justified. This essay will analyze the similarities and the differences between two management approaches concerning the business case theme. The first methodology that is going to be described is Prince2, where an overview of its main characteristics will be provided. Then, the essay will explain the same …show more content…
In a recent study, Mckenna (2016) underlined that when we attempt to state the precise level of scope, cost and time on a project we are going to fail because there is no flexibility concerning something that is very dynamic. Instead, with Scrum we recognize that it’s impossible to define everything at the beginning of a project, and therefore we are expecting things to change. Scrum allows for variability and for unexpected problems.
Similarly, Collyer (2010) and Boehm (1996) declared that excessive detail in the early stages of a project with Prince2 may be problematic and ambiguous in a changing environment. Between the various problems that a too-detailed requirements document can have, we can mention the impossibility to change or add functionality because of early specifications of requirements and focus of solutions on a specific time, although they are both likely to change. Unlike Prince2, Agile is planned to use a minimum of documentation to report critical business needs, and to facilitate flexibility and receptiveness to dynamic conditions. In Prince2, producing documentation for the whole project is a long and expensive process, besides it not always correctly expresses the needs of both product owner and team. Suffice it to say that on the one hand the development team needs much time to write documents, and on the other hand, the product owner does not always have the necessary …show more content…
In addition to the Project efficiency, concerning the meeting between cost, time and scope goals, Scrum aspires also to satisfy stakeholders’ expectations of the project. Agile methods usually involve customers from the beginning and during the various steps, both in establishing project’s goals, giving feedbacks and evaluating progressive prototypes (Serrador, Pinto, 2015). Another confirmation is given by Sliger (2012), according to whom Agile projects are planned to deliver early and often a product or product increments, in order to combine customers’ feedback and other new information into the next step. By spending more time on experimenting, executing, and learning, and less time on speculation, the cycle time for delivery is reduced. Agile teams are better able to compete in the market and manage the speed of
This essay will talk about the backbone of a project: the business case theme. The business case theme is firmly related to the continued business justification principle. As Turley states (2010), this principle recommends that before and during a project we should evaluate whether the project is desirable, viable and achievable. It signifies that the project needs to be profitable and the use of time and resources should be justified. This essay will analyze the similarities and the differences between two management approaches concerning the business case theme. The first methodology that is going to be described is Prince2, where an overview of its main characteristics will be provided. Then, the essay will explain the same …show more content…
In a recent study, Mckenna (2016) underlined that when we attempt to state the precise level of scope, cost and time on a project we are going to fail because there is no flexibility concerning something that is very dynamic. Instead, with Scrum we recognize that it’s impossible to define everything at the beginning of a project, and therefore we are expecting things to change. Scrum allows for variability and for unexpected problems.
Similarly, Collyer (2010) and Boehm (1996) declared that excessive detail in the early stages of a project with Prince2 may be problematic and ambiguous in a changing environment. Between the various problems that a too-detailed requirements document can have, we can mention the impossibility to change or add functionality because of early specifications of requirements and focus of solutions on a specific time, although they are both likely to change. Unlike Prince2, Agile is planned to use a minimum of documentation to report critical business needs, and to facilitate flexibility and receptiveness to dynamic conditions. In Prince2, producing documentation for the whole project is a long and expensive process, besides it not always correctly expresses the needs of both product owner and team. Suffice it to say that on the one hand the development team needs much time to write documents, and on the other hand, the product owner does not always have the necessary …show more content…
In addition to the Project efficiency, concerning the meeting between cost, time and scope goals, Scrum aspires also to satisfy stakeholders’ expectations of the project. Agile methods usually involve customers from the beginning and during the various steps, both in establishing project’s goals, giving feedbacks and evaluating progressive prototypes (Serrador, Pinto, 2015). Another confirmation is given by Sliger (2012), according to whom Agile projects are planned to deliver early and often a product or product increments, in order to combine customers’ feedback and other new information into the next step. By spending more time on experimenting, executing, and learning, and less time on speculation, the cycle time for delivery is reduced. Agile teams are better able to compete in the market and manage the speed of