Ankita Kakalasaria
Mini Research 3
ENMG 650-Project Management
Agile program management deals with managing a project which involves less number of members and has a cross functionality between the teams. It is focused on delivering the products iteratively. Iterative method is used in scenarios were the requirements of the project is not clearly defined by the user i.e. the user is not sure of the end product. This methodology gives the user a freedom to review the product constantly and make changes until the desired result is obtained. Designing of a webpage which involves constant evaluation from the user regarding the layout of the widgets, functionalities, and background color is a very good example to indicate the iterative method. …show more content…
Use cases indicates the necessity of formulating the project. It is used to understand the user’s expectation from the project. Backlogs, involves the initial requirements that are required in order to fulfill the ideas mentioned in the use case1.
Tasks refers to the work that needs to be performed in order to complete the project. The tasks are obtained by analyzing the requirements and the use cases provided by the user. Sprint indicates a time frame that is required to deliver the iterative product based on the requirements collected. In order to deliver the product in a given sprint, a sprint planning needs to be performed. A sprint planning involves a meeting with the users of the project in order to discuss the requirements that needs to be delivered in the sprint1.
Scrum involves people from different cross functional teams to be present in a sprint in order to deliver the desired product. As there are members from different fields, there is a scrum meeting which takes place every day1. The meeting lasts for few minutes and important topics on the project’s status and the tasks that needs to be performed are discussed. This discussion results in delivering a product which is more efficient and …show more content…
This achievement is possible due to delivering the products in an iterative manner. An iterative method allows the user to validate the product and provide feedback immediately.
1 https://blog.taiga.io/agile-terms-you-must-know.html
The feedback is useful in making changes according to the current requirements and user’s understanding of the final result. Whereas, in the traditional approach, which follows the waterfall model, the users are completely involved in the beginning stages of the project and later moved out from the project. This exit results in building an end product with which the customer is not satisfied/happy.
The waterfall model which is used in the traditional management, involves building of the entire project after collecting the necessary requirements from the user. Once the requirements are collected in the initial stage there is no further scope for major changes in the requirements during the process of building the project.
Secondly, the look and feel of the product is experienced from the beginning stage of development in the agile program management whereas in traditional management it is only possible at the end of the project. This results in limited scope for improvements in case the product needs any
Mini Research 3
ENMG 650-Project Management
Agile program management deals with managing a project which involves less number of members and has a cross functionality between the teams. It is focused on delivering the products iteratively. Iterative method is used in scenarios were the requirements of the project is not clearly defined by the user i.e. the user is not sure of the end product. This methodology gives the user a freedom to review the product constantly and make changes until the desired result is obtained. Designing of a webpage which involves constant evaluation from the user regarding the layout of the widgets, functionalities, and background color is a very good example to indicate the iterative method. …show more content…
Use cases indicates the necessity of formulating the project. It is used to understand the user’s expectation from the project. Backlogs, involves the initial requirements that are required in order to fulfill the ideas mentioned in the use case1.
Tasks refers to the work that needs to be performed in order to complete the project. The tasks are obtained by analyzing the requirements and the use cases provided by the user. Sprint indicates a time frame that is required to deliver the iterative product based on the requirements collected. In order to deliver the product in a given sprint, a sprint planning needs to be performed. A sprint planning involves a meeting with the users of the project in order to discuss the requirements that needs to be delivered in the sprint1.
Scrum involves people from different cross functional teams to be present in a sprint in order to deliver the desired product. As there are members from different fields, there is a scrum meeting which takes place every day1. The meeting lasts for few minutes and important topics on the project’s status and the tasks that needs to be performed are discussed. This discussion results in delivering a product which is more efficient and …show more content…
This achievement is possible due to delivering the products in an iterative manner. An iterative method allows the user to validate the product and provide feedback immediately.
1 https://blog.taiga.io/agile-terms-you-must-know.html
The feedback is useful in making changes according to the current requirements and user’s understanding of the final result. Whereas, in the traditional approach, which follows the waterfall model, the users are completely involved in the beginning stages of the project and later moved out from the project. This exit results in building an end product with which the customer is not satisfied/happy.
The waterfall model which is used in the traditional management, involves building of the entire project after collecting the necessary requirements from the user. Once the requirements are collected in the initial stage there is no further scope for major changes in the requirements during the process of building the project.
Secondly, the look and feel of the product is experienced from the beginning stage of development in the agile program management whereas in traditional management it is only possible at the end of the project. This results in limited scope for improvements in case the product needs any