Agile (adaptive) model

Revision as of 23:38, 21 March 2022

Written by Marco Lombardo s210384

Abstract

Agile model is a new way of riding the development approach and life cycle performance domain of a Project, Program and Portfolio Management. The focus of the model is on process adaptability and customer satisfaction. The model is based in iterative and incremental processes combined to achieve a rapid delivery of working software product. ^[1]

Although there are some adaptive methods dating back to before 2000’s, it is possible to date the concept of agile in 2001, when it was signed the “Agile Manifesto”. ^[2] The Agile Manifesto outlines four Core Values (individuals and interactions; working software; customer collaboration; and responding to change) and twelve Guiding Principles which are of key importance for any team aiming at using an agile model.

The agile model is an adaptive model that use iteration or sprints to divide the project life cycle to work with a short-term planning. It is possible to define each sprint as the sum of 5 phases: gathering, design, construction, testing, close, and after each iteration the teams receive feedback, whereas the traditional models are based on a predictive approach (e.g., waterfall model). Both typologies of modelling have their pros and cons and the best approach to follow depends on the project/product.

Its goal is to assist companies provide value more frequently to their clients, react quicker to changes, and eventually improve the business. ^[3] It is utilized when it is necessary to divide a large project into more reasonable tasks and complete them in short iterations throughout the project life cycle, defined as the set of phases from the start to the end of a project.

The model can be applied to almost any project, but for high complexity of design and scale of projects, companies prefer to use the predictive models. It is also important that the companies adopting the agile model make sure that their employees are aware of the rules and methodologies to successfully work with such a model.

Keywords: development approach, agile model, adaptive, sprint, PPPM

How agile (adaptive) model works; elements of an agile model.Source:[https://scrummate.com/agile-guide/agile-model/

Big idea

The development approaches are tools that allow people to correctly follow the steps to create software that meets a business need; it is possible to divide the development approaches in two big areas, adaptive and predictive approach; the agile model is a tool based on the adaptive approach. This model is used for its elasticity and adaptability and based on an iterative approach. ^[4] It is possible to define the agile model as a lightweight method compared with all the other development models.

History

The Agile Manifesto was written in 2001, when 17 developers in Wasatch Mountains (Utah) had a meeting focused on the technological development of the future. Everyone agreed to the fact that most companies were drowning in documentation and were focusing too much on planning, with the consequence that they were losing what was the most important thing for their business: their clients.

For this reason, that weekend they wrote a short document (with only 68 words) that changed completely the development of software and the way of working for big companies. The idea of the Agile Manifesto was to find a common area among the most used frameworks conceptually close to the agile method (for example: Scrum, Extreme Programming, Kanban and other frameworks).

“The Agile Manifesto has four Core Values:

1. Individuals and interactions over processes and tools
2. Working software over comprehensive documentation
3. Customer collaboration over contract negotiation
4. Responding to change over following a plan

And the twelve principles are:

1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
4. Businesspeople and developers must work together daily throughout the project.
5. Build projects around motivated individuals. Give them the environment and support they need and trust them to get the job done.
6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
9. Continuous attention to technical excellence and good design enhances agility.
10. Simplicity--the art of maximizing the amount of work not done--is essential.
11. The best architectures, requirements, and designs emerge from self-organizing teams.
12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly”. ^[2]

Sprints of the agile model

The model is well defined using the word adaptive and it is used in companies to break projects in small pieces. The approach used is that there is no detailed planning of long-term work; it is possible to have a clear idea of future tasks only when these tasks will be necessary to develop. Using this method, the teams need to be elastic and able to easily adapt when the product requirement is changing. The particularity of the version is that a product is examined regularly the use of release iterations, minimizing on this manner the hazard of any looming disasters in future. The iterations involve different teams that simultaneously work on various area. ^[1] The work done in every working session is also known as sprints. They have variable durations that can range from few days to few weeks. The idea is to have a rotating release schedule from the teams to demonstrate that these segments are working well and, if not, to quickly fix any flaws.

Main phases of agile model Source:https://www.slideteam.net/business_powerpoint_diagrams/catalog/product/view/_ignore_category/1/id/437360/s/five-phases-agile-project-management-model-agile-proposal-effective-project-management-it/

The agile model consists of 5 main phases:

1. Gathering: this is the starter point for each company. The first phase is important because there is the need to make a plan in order to conceptualize the product and the needs of the end customer, and also understand who the stakeholders and the teams will be interested in the project.
2. Design: this phase is important to create the initial requirements for the product. The idea is to encourage each team involved in the project to have a holistic view and explore different ideas for the project. It is the phase that expand the collaboration of the team members. It is important because teams need to have a good overview of the product and also of the timeline for the deliveries.
3. Construction: this phase is focusing on deliveries and particularly on the requirements and the constraints that the teams should follow. It is important to have a good collaboration between teams and a good interaction with customers and stakeholders.
4. Testing: in this phase teams analyse the results with what was planning. Teams can adapt or make changes in order to have a better product. The most important work is to receive and elaborate feedback.
5. Close: the iteration is finished; each team should share the results and receive feedback from the customer in order to start the new iteration. The most important thing to do in this phase is to analyse all the keys of the project and save all the knowledge gathered.

Agile is everything about adaptive planning, how to get delivers earlier, every sprint an improvement, development that evolve over time. it encourages rapid response, adoption, and adaptation to change. ^[5]

Applications

Adaptive (agile model) vs. predictive (waterfall model)

To explain where an agile model can be applied, it is important to understand the differences between adaptive (agile model) and predictive (waterfall model) methodologies.

A development approach is the method utilized to design and develop product, service, or the resource involved in the life cycle of a project. Each project is different compared to another, and the approach used can change considering the complexity and volatility of it. In fact, companies with projects with a high complexity are the ones which prefer working using a predictive model, while the ones with projects with a high volatility prefer the adaptive model.

The adaptive strategies change exactly as fast as the real constraints and idea might change; for this reason, this approach is very useful when the requirements to develop a product have a high level of uncertainty and there can be changes during the project. The model defines a clear vision of the full project in the early phase. The development of the project is based on the user feedback, and all changes are done in accordance with the stakeholders. Usually, the method utilizes iterative and incremental approaches with a duration from one to two weeks and where each team involved in the project should deliver and share with the other teams the work done.

Predictive approaches, in contrast, are utilized when it is possible to identify, gather and analyse the requirements before the starting point of project life cycle to reduce as much as possible the changes and replanning the phases of a project. This method, in fact, is useful because it reduces the uncertainty related with the risks management of the project and for this reason it is used when the investment is important.

The predictive models, in particular the Waterfall Model, are still the most used to manage projects. It is defined also as linear sequential model. Often, it is possible to consider the waterfall model as the traditional approach of project management. It is organized in a strict way of planning and executing the plan step-by-step, and each step is dependent to the previous. This type of linear approach often cannot be useful if the product needs dynamic and fast changing environment, as nowadays. In a Waterfall project, if there is a need to fix a failure it will require lots of extra time and cost, that are not planned with the clients. For this reason, many companies are strict to ensure that projects satisfy the constraints before continuing to the next phase, otherwise it will have to be rebuilt from the starter point.

Considering that, it is possible to make a clear line in between the two methodologies and to try to understand when it is better one and when the other.

The waterfall model is suitable for projects with well-defined requirements, where almost no changes are expected. Instead, agile works smoothly when there is a higher chance of frequent requirement changes. Agile is a flexible model able to adapt to the change of requirements, also if it will happen daily. Instead, in the waterfall model the constraints are defined with the business analyst only once at the starter point of the project. ^[5]

Companies which adopted the agile model

The agile model is a not common method and sometimes a challenge for big companies, because it requires strong ability of the teams, flexibility, and fast response to changes. Something that does not seem to be compatible with the rigid’s structures of large companies. But there are some big companies like CISCO (IT), Lego (IT), Barclays (Finance), Panera Bread (IT), Ericsson (Mobile network), PlayStation (Gaming), John Deere (IT), Fitbit (technology), OpenLink (Finance), Royal Philips (medical technology company) which had adopted the agile model and they got positive results from it. ^[6]

Examples of agile software

Some examples of the most popular agile methods are:

1. Scrum: The first agile framework is Scrum, which uses sprints and daily meetings (also known as Scrum ceremonies) at intervals to address different portions or a set amount of work within a project during its life cycle. The method offers benefits such as security, quality, and reliability to the agile method thanks to the combination of iterative and incremental approach called sprints. The first step is to set the goals of each sprint; according to this framework, it is not possible to modify the focus of the sprint, but it is possible to increase the number of sprints and/or modify the scope of one of the future ones. There are three important roles in Scrum: the leader of a project is usually the Scrum master, the client is often the product owner, while the people developing the product are the scrum team members. ^[7]
2. Kanban: The Kanban method is one of the most used frameworks which consists of the visual display of present, future and completed tasks. Each task is displayed in a kanban board where the team members can see the state of every piece of work at any time. The applications for this method are the agile implementation and the development of DevOps software. The reason why the Kanban board is widely used is that having a visual representation of the tasks helps the agile team members to have an overview on all tasks, both their own and the ones related to the project. To achieve this visual display, it is important to have quick and continuous communication of available resources and being completely transparent on the work progress. The core of Kanban means is visualizing the workflow, limit WIP (work in progress) and measure the lead time. ^{[7] [8]}
3. Extreme programming (XP): The last model is the Extreme programming, an agile software development framework with the idea of producing a higher quality software and quality of work for the development team. The model is considered the most specific among all agile frameworks for what concerns good engineering practices for developing software. The values of the extreme programming are five: communication, simplicity, feedback, courage, and respect, and are described in more detail on the website. ^[9]

Limitations

Agile model - Pros and Cons

In the last decades, agile methods are becoming more and more accepted in the software world. However, there are some cases in which this method may not be suitable. As shown below, the agile model presents many advantages, but has also a number of disadvantages to be taken into consideration.

The pros of agile model are many. First, the model is based on transparency and great collaboration between teams and not only, in fact, it a creates a strong relationship between clients and the developing team. This is done thanks to the continuous delivery of a workable product which increases the customer satisfaction. Secondly, the functionality of the model is meant to be developed quickly by cutting overall development time (the delivers of software are reduced at 1-2 weeks) and to be demonstrated; its adaptability makes it suitable both for fixed or changing requirements and the resource requirements are minimum. With regards to the types of teams it can be applied to, the model suits in a good team environment and improves the teamwork and cross training. Moreover, the agile model provides early partial working solutions, minimal rules, easily employed documentation. It is a good model for environments that are continuously changing and evolving, as it improves flexibility to developers, and it is easy to manage. Lastly, it requires very little planning, enables concurrent development and delivery within an overall planned context. ^{[1] [10]}

However, the Agile method is not optimal for all cases. Even though the principles of the model are meant to resolve some of the drawbacks that could arise from using the Waterfall approach, it is not uncommon that companies and/or organizations do not achieve the expected advantages. This is due to one of the following reasons. ^[11]

In the first place, it is not suitable for handling complex dependencies, as it might pose more risk of sustainability, maintainability, and extensibility of the product, if this is too complex and it is hard and difficult to measure how much effort will be needed to start the life cycle of a larger project. Moreover, the model cannot be used by all companies because it requires a certain structure and guidelines to be in place: an overall plan, an agile leader and an agile project manager are a must, without which it will not work. For the successful implementation of the model, it is fundamental that all deliveries and deadlines are strictly managed, as they dictate the scope and guarantee the correct sequence of functionalities to be delivered. Additionally, it can be some misunderstanding among groups due to the fact the documentation is not explained well or because of a lack of emphasis and it is able to result in hard transitions among phases. Moreover, the model depends heavily on customer interaction, so if the customer is not clear or does not have well-defined goals, the team can be driven in the wrong direction or if the client and the team are in different pages the project will derail. For large companies, it could be a disadvantage to use the agile model due to the fact that it entails a very high individual dependency, since it generates minimum documentation. Due to this lack of documentation, the transfer of technology to new team members may be quite challenging; this means that an agile model requires senior developers and there is no space for people without good knowledge of programming skills. ^{[1] [10]} Sometimes, the fact that there is not any kind of system design or just because the team is not ready to work with this model that the structure becomes too complex forcing the companies to follow the waterfall model. ^[11]

To conclude, the agile model represents a good method when it is more important the speed of creating a product compared to its eminence. It is also proven to be useful in the cases where clients are often changing the scope of the project and when the idea to be achieved is not fully defined. From the point of view of the human resources of the companies, good skilled, independent, and adaptable developers are key. Lastly, it is recommended to use the agile model if the industry has to fulfil the continuously varying standards. ^[4]

Annotated bibliography

Agile New Solution Development in Manufacturing Companies,Tuomas Huikkola, Marko Kohtamäki, Technology Innovation Management Review, volume 10, Issue 3 2020

• This conceptual paper proposes a new agile solution development model for technology and manufacturing companies

COMPARATIVE STUDY: WATERFALL V/S AGILE MODEL, A. Dubey, A. Jain, A. Mantri, Acropolis Institute of Technology and Research, Indore (M.P), India, March, 2015

• This journal report is written by A. Dubey, A. Jain, A. Mantri. This report describes the differences between Agile and Waterfall methods.It explains when it is better to use one of the other model in a very organized way.

A Guide to the Project Management Body of Knowledge (PMBOK ® Guide) – 7th Edition and The Standard for Project Management, Project Management Institute, Inc., 14 Campus Boulevard, Newtown Square, Pennsylvania 19073-3299 USA, 2021 ISBN: 978-1-62825-664-2

• This modern guide enables project team members to be proactive,innovative, and nimble in delivering project outcomes. The section studied is the chapter 2, Project Performance Domains, in particular the section explain the differences between adaptive and predictive methods and when is better to use one of another.

References

1. ↑ ^{1.0 1.1 1.2 1.3} https://www.tutorialspoint.com/sdlc/sdlc_agile_model.htm SDLC - Agile Model
2. ↑ ^{2.0 2.1} http://agilemanifesto.org Manifesto for Agile Software Development, 2001
3. ↑ https://kanbanize.com/agile Agile Body of Knowledge
4. ↑ ^{4.0 4.1} http://citeseerx.ist.psu.edu/viewdoc/download;jsessionid=F2BCA87C0B147D28CC78CED89B3802CC?doi=10.1.1.695.9278&rep=rep1&type=pdf] COMPARATIVE STUDY: WATERFALL V/S AGILE MODEL, A. Dubey, A. Jain, A. Mantri, Acropolis Institute of Technology and Research, Indore (M.P), India, March, 2015
5. ↑ ^{5.0 5.1} https://www.blueoceanworkshops.com/agile-adaptive-vs-waterfall-predictive-project-management/ Introduction to agile and waterfall
6. ↑ https://techbeacon.com/app-dev-testing/10-companies-killing-it-scaling-agile Big companies associated with agile model
7. ↑ ^{7.0 7.1} https://thedigitalprojectmanager.com/agile-project-management/, Scrum and Kanban explanations
8. ↑ https://www.atlassian.com/agile/kanban Kanban explanation, atlassian
9. ↑ https://www.agilealliance.org/glossary/xp Extreme programming explanation
10. ↑ ^{10.0 10.1} https://www.simplilearn.com/agile-modelling-article Pros and Cons about agile model
11. ↑ ^{11.0 11.1} http://www.bmc.com/blogs/agile-vs-waterfall/ Usage of the agile model