Discussion Assignment: Characteristics Of Agile Project (Coursework Sample)

Agile Approach
Name
Institution
Course
Date of Submission
Agile Approach
Different projects utilize different management approaches. The method applied in a project depends on the type of the project. The essay below describes the characteristics and projects that use an agile and a predictive approach and the differences between the predictive and the scrum methodology.
According to Schwalbe (2016), the projects that require an agile approach and those that need a predictive approach have different characteristics. An agile approach is applicable in a project where the team cannot prompt the scope earlier in the product cycle. The method is also applicable to a project where the team wants to produce potential marketable products in a short time. Besides, the agile approach shall also apply in projects that have less rigid constraints. More so, the agile approach can be used in a project that has experienced and co-located teams. Lastly, the projects that utilize this method have unclear requirements, smaller risks and more flexible scheduling (Schwalbe, 2016, p. 118).
The projects that need a predictive approach have different characteristics with those that need the agile approach. For instance, the predictive approach-projects have substantial constraints, dispersed and inexperienced teams. They also have large risks and clear, straightforward requirements. Lastly, they have a relatively firm accomplishment date. The predictive approach is mainly applicable in projects where the team can express the scope of the project earlier in the project life (Schwalbe, 2016, p. 118).
Schwalbe (2016) has defined and outlined various types of scrum, artifacts, and ceremonies. A scrum refers to a process framework for agile development. In a project, a scrum entails three roles for the participants (Schwalbe, 2016, p.118). The first role is the Product owner, and it refers to the individual who is in charge of ensuring a business value of the project. Besides, the product owner holds the obligation for deciding the work to be done in the project development, and he/she determines the order in which tasks are to be executed by other participants. For instance, in an organization, the CEO or the person who suggests a project is the product owner (pg. 118).
The second role is the ScrumMaster, and it entails the individual who is accountable for guaranteeing a productive team. The ScrumMaster is also in charge of the facilitation of the daily scrum. Besides, he/she ensures that there is collaboration across all functions and roles during the project development. Lastly, the ScrumMaster ensures that there is a total eradication of all barriers that may inhibit the effectiveness of a team (Schwalbe, 2016, p. 118).
The third and the last role is the development team or the scrum team. The role refers to a group of five to nine people who work in an organized manner to yield the desired results for each sprint in a project. In most cases, a sprint takes two to four weeks, and during this time, a particular task must be completed and submitted for review (Schwalbe, 2016, p. 118).
An artifact refers to a precious object fashioned by people in a scrum. It is also known as a deliverable in some project management methods. Three artifacts are essential in a scrum. The first one is the Product backlog, and it can be described as a list of features that the business value puts in priority. In a product backlog, the details of the highest priority items are broken down to estimate the effort that the team will need to develop them. The sprint backlog is the second artifact, and it lists the priority items from the product backlog that are to be accomplished within a sprint. The priority items are divided into smaller tasks that can be completed in 12 to 16 hours. Lastly, the burndown chart artifact indicates the remainder cumulative work in a sprint on a daily basis (Schwalbe, 2016, p. 119).
In a scrum, a ceremony refers to a meeting or activity facilitated by y the ScrumMaster (Schwalbe, 2016, p. 119). While suing a scrum method, the ScrumMaster facilitates four different ceremonies which include the sprint planning session, the Daily Scrum, the sprint reviews and the sprint retrospective. In a sprint planning session, the team together with the ScrumMaster gathers to choose the piece of work that would be done within a sprint, from the product backlog. The duration of the meeting is 4 hours to the whole day. The Daily Scrum is a meeting held by the team on a daily basis to share the progress of the tasks, challenges and plan the work to done that day. The assembly lasts for about fifteen minutes, and it occurs at the same venue and time. The Sprint reviews entail a meeting held by the team and the ScrumMaster to demonstrate the completed tasks in a sprint. Lastly, the sprint retrospective is a convention in which the group gathers to look for the ways of improving the product and the development depending on review given by the development team (pg. 119).
Schwalbe (2016) outlines that Scrum activities are different with the predictive methodology activities. For instance, during the project initiation in a predictive method, the main activities include the i...