Agile in Project Management
(→Abstract) |
(Agile in Project Management) |
||
| Line 1: | Line 1: | ||
| − | == | + | == Introduction == |
| − | + | === What is Agile? === | |
| − | Agile | + | The traditional approach into solving problems were based on a waterfall project management. This process is about setting an action plan that consists in a series of steps. In order to move forward with the plan, all the steps with their respective goals had to be completed. This approach did not allowed teams to move fast and to have possible solutions with minimum expenses. This is why Agile approach changed project management. With iteration and prototyping, teams are allowed to make mistakes and receive constant feedback to improve during the development process, instead of waiting until the end to know if the customer’s needs are being satisfied. |
| − | + | Agile is the result of a discussion held in 2001 by a group of software developers and project managers. During the meeting, they talk about the aspects and characteristics of the projects they have been involved where final outcomes were a success. This team created a new statement of values for software development that is called ‘The Agile Manifesto’. Agile is an interactive practice where cross functional teams work together to find solutions and proposals to reach a specific outcome throughout a continuous iteration process. Agile is composed by several steps where each one of them allows the team to adapt, improve and adjust what is needed to reach the expected outcome based on the objective of the project. [1] | |
| − | + | == Agile’s Values == | |
| + | These four values are the core of this practice [1][2][3]: | ||
| + | * '''Individuals and interactions over processes and tools''' | ||
| + | Agile aims to be humancentric and participatory [1]. Processes and tools provide guidance, best practices, and improve productivity [2]. However, Agile states that people need to be involved in the development process. Users, customers, and the development team need to work together, have an open and effective communication to create a viable solution that will comply with the objective of the project. The iteration process will start with the feedback provided by costumers and users when the proposed solutions are tested and validated. | ||
| + | The challenge of this value is how the communication is held within the team. People need to listen and be open to different proposals that will arise in the discussion. Effectiveness in important to avoid the communication being ambiguous and time-consuming. | ||
| + | * '''Working software over comprehensive documentation ''' | ||
| + | When using the Agile approach, the proposed solutions in each iteration does not need to be fully developed. Agile explains that those possible solutions should be developed with what is just enough to achieve the goal and not invest time in frivolous tasks and features that are not vital to test them. The objective of this value is to provide users and customers a tangible solution to review, test and give feedback to continue with the improvement process of it. | ||
| + | The challenge of this value is to deliver a working product or prototype so users and customers can have a real interaction with it in comparison to deliver documentation and KPI’s of the results. | ||
| + | * '''Customer collaboration over contract negotiation''' | ||
| + | Customers need to be involved in the process. At the beginning of the relationship between the project managers and the customers, the details of the projects tend to be incomplete and any decision set in stone in the initial discussion can become an issue in the future when it changes. In this matter, Agile suggests negotiating flexibility for change with the customers in the project’ scope, resources, prices and outcomes to be allowed to make adjustments as progress is made in the project. | ||
| + | The challenge in this value is to have proper and complete preparation of the teams as well as setting from the beginning which are the expectations of the outcome. | ||
| + | * '''Respond to change over following a plan ''' | ||
| + | The uncertainty of a project outcome depends on the needs of the customers and users. In contrast with the usual procedure to follow a step-by-step plan without allowing change to take part, Agile suggests that it should always be open the possibility of change and adjustments to the project in development. This is how the iteration process takes place giving the option to make changes and adjustments to obtain a well design solution or product in the end. This value is also relevant when there is consideration to changes in the environment itself since the business world tends to have continuous change. Project managers must be diligent to change that will surely occur during the development of the project | ||
Revision as of 20:35, 19 February 2022
Introduction
What is Agile?
The traditional approach into solving problems were based on a waterfall project management. This process is about setting an action plan that consists in a series of steps. In order to move forward with the plan, all the steps with their respective goals had to be completed. This approach did not allowed teams to move fast and to have possible solutions with minimum expenses. This is why Agile approach changed project management. With iteration and prototyping, teams are allowed to make mistakes and receive constant feedback to improve during the development process, instead of waiting until the end to know if the customer’s needs are being satisfied. Agile is the result of a discussion held in 2001 by a group of software developers and project managers. During the meeting, they talk about the aspects and characteristics of the projects they have been involved where final outcomes were a success. This team created a new statement of values for software development that is called ‘The Agile Manifesto’. Agile is an interactive practice where cross functional teams work together to find solutions and proposals to reach a specific outcome throughout a continuous iteration process. Agile is composed by several steps where each one of them allows the team to adapt, improve and adjust what is needed to reach the expected outcome based on the objective of the project. [1]
Agile’s Values
These four values are the core of this practice [1][2][3]:
- Individuals and interactions over processes and tools
Agile aims to be humancentric and participatory [1]. Processes and tools provide guidance, best practices, and improve productivity [2]. However, Agile states that people need to be involved in the development process. Users, customers, and the development team need to work together, have an open and effective communication to create a viable solution that will comply with the objective of the project. The iteration process will start with the feedback provided by costumers and users when the proposed solutions are tested and validated. The challenge of this value is how the communication is held within the team. People need to listen and be open to different proposals that will arise in the discussion. Effectiveness in important to avoid the communication being ambiguous and time-consuming.
- Working software over comprehensive documentation
When using the Agile approach, the proposed solutions in each iteration does not need to be fully developed. Agile explains that those possible solutions should be developed with what is just enough to achieve the goal and not invest time in frivolous tasks and features that are not vital to test them. The objective of this value is to provide users and customers a tangible solution to review, test and give feedback to continue with the improvement process of it. The challenge of this value is to deliver a working product or prototype so users and customers can have a real interaction with it in comparison to deliver documentation and KPI’s of the results.
- Customer collaboration over contract negotiation
Customers need to be involved in the process. At the beginning of the relationship between the project managers and the customers, the details of the projects tend to be incomplete and any decision set in stone in the initial discussion can become an issue in the future when it changes. In this matter, Agile suggests negotiating flexibility for change with the customers in the project’ scope, resources, prices and outcomes to be allowed to make adjustments as progress is made in the project. The challenge in this value is to have proper and complete preparation of the teams as well as setting from the beginning which are the expectations of the outcome.
- Respond to change over following a plan
The uncertainty of a project outcome depends on the needs of the customers and users. In contrast with the usual procedure to follow a step-by-step plan without allowing change to take part, Agile suggests that it should always be open the possibility of change and adjustments to the project in development. This is how the iteration process takes place giving the option to make changes and adjustments to obtain a well design solution or product in the end. This value is also relevant when there is consideration to changes in the environment itself since the business world tends to have continuous change. Project managers must be diligent to change that will surely occur during the development of the project
