SWOT analysis (SWOT matrix) is an acronym for strengths, weaknesses, opportunities, and threats. This tool is used for a product or a business to specify its internal or external factors which are favorable or unfavorable to achieve its objective. While using this strategic planning tool, keep in mind that Strengths and weakness are the internal factors whereas, threats and opportunities are the external factors.(to the business or product).
SWOT Analysis of Agile Model
Agile software development model is an incremental model consist of short iterative cycles. A truly agile method must be iterative (take several cycles to complete), incremental (not deliver the entire product at once), self-organizing (teams determine the best way handle work), and emergent (processes, principles, and work structures are recognized during the project rather than predetermined). (Boehm & Turner, 2005)
M.Scott Peck explained the need of agile software development as,
“If a predictive method like Waterfall is to avoid pain of problems, then we can say that Agile was developed to solve the pain of problems” -M.Scott Peck, The Road Less Traveled.
While carrying out the SWOT analysis, Agile Manifesto and Agile principals can be used as useful pointers.
Strengths:
1. Welcome changing requirements, even late in development
Agile methods are flexible to change. In any iteration, change is welcomed and can be implemented. Agile is perfect for the tasks where is high changeability. Boehm & Turner said that “changes are an ally rather than an enemy. Change allows for more creativity and quicker value to the customer”. (Boehm & Turner, 2005)
2. Early benefits to the customer
Agile methodologies can give an early look of the product(how it might look like) to the user, which helps them to meet the customer need and satisfaction.
3. High visibility of the process
As mentioned in principals behind Agile Manifesto “Business people and developers must work together daily throughout the project” (Principles behind the Agile Manifesto, 2017). So the stakeholder involves in every step of the process and it provides clear visibility of it.
4. Simplicity
Striving for simplicity is also included in Agile principals. The simplicity could be in three different aspects i.e design, process or code. Simplicity can be considered as an advantage or disadvantage. In small projects, design simplicity is an advantage as it reduced the time whereas it can be a disadvantage for large projects where more rigorous processes are required. (Shahir, Daneshpajouh & Ramsin, 2008)
5. Prioritizing Requirements:
Prioritizing the requirements according to customer needs and risks involved are the common practice in Agile methodologies. It helps mitigates projects risks and help focus on stakeholder satisfaction. (Shahir, Daneshpajouh & Ramsin, 2008)
6. Cost control
Budget, Time, and scope are three fundamentals of project management. In agile methods, time and budget are fixed while scopes are variable. “Agile uses time-boxing to control schedule and is encouraging the customer to prioritize all product functionalities that will be delivered. Using such a fixed timescale enables a fixed budget”.( Welcome to Fisnik’s blog – 2017).” All the errors can be fixed in time in agile processes without affecting the predetermined budget.
7. Teamwork and Collaborative Decision Making
In the Agile process, team members are working closely and the decision of each member is worthy and will affect the result. So it’s really important to take right decisions and stay away from destructive conflicts which can really effect the end result, especially in form of cost and time.
Weaknesses:
1. Agile practice
The true agile is rarely practiced, which is the biggest problem. Most of the time software developers assume that Agile is all about flexibility and absence of process, which is not true. Agile has its own unique development structure which is different than traditional other development approaches. Agile is iterative, it is adaptive and it is supported by some outstanding tools and techniques. (Ghandhi & Shubh, 2013) So understanding the true Agile is really important.
2. Heavy customer interaction
As stated in the Principal Agile manifesto that Face-to-face conversation is the efficient and effective method of conveying information (Principles behind the Agile Manifesto, 2017).So the heavy interaction is required from the customer side in order to meet his expectations and provide a quality product.
3. Not suitable for Large projects/organizations
As Agile models emphasis on face to face interaction, verbal communication, over-written documentation and requirement flexibility, it’s really hard to integrate into large organizations.
4. Lack of documentation:
Agile processes didn’t rely on heavy documentation. So the lack of documentation and modeling cannot help for future projects guidance.
5. Agile thrives with co-located teams.
The agile model works for co-located teams, Where customer feedback is mandatory in the real time. All team members are required to work close to each other. So because of this geographic bound, it’s really hard for in-line business to manage all team members under one roof in practical.
Opportunities
1. Team Empowerment
As mentioned in Agile principals that “Build projects around motivated individuals, Give them the environment and support they need, and trust them to get the job done.”
So empowered teams working on agile processes have full support and voice of every team member is valuable. The intellectual and experienced members have the authority to make decisions alone which is beneficial for the project.
2. Iterative and incremental methodology
Because of iterative nature of Agile methods, Team has always chance to change its direction and implement new designs and ideas, in any stage of the project, if required. So the agile model allows adopting latest technology at any stage.
3. Expert advice
Excelling the agile projects, expert opinions in different contexts are a great opportunity which can not be overlooked. Development experts are involved greatly throughout the software development process, as well as domain technology, and methodology experts. (Shahir, Daneshpajouh & Ramsin, 2008)
Threats
1. Lack of documentation
As agile methods are simple and people oriented. So mostly during face to face communication, all the important issues were discussed and decisions were taken. So because of lack of proper documentation structure in agile processes, it’s always threatening to overlook of keeping the important points.
2. Lack of Agile practices in traditional organizations
Traditional organizations are not integrating the agile process very warmly, lack of this interest in the adaptability of Agile methodologies are amply mentioned by Boehm & Turner in Journal “Management Challenges to Implementing Agile Processes in Traditional Development Organizations”. The problem in implementing agile models can be the difficulty of coordinating agile and waterfall processes or can be human resources.
3. Security problems:
In an Agile model, we cannot found several new world IT problems, especially the Security related issues. As no proper security structure is present, so the Agile team have to face several security related issues. The problems can arise because of lack of security knowledge and awareness among team members.
SWOT Analysis Of Waterfall Model
Waterfall is the most common old technique used for software development. It’s also known as linear-sequential life cycle model. As the name indicates, all steps in waterfall model are systematic, means need to complete one phase before jumping into the other. Waterfall model is really old and used for the construction & manufacturing projects. As it’s created in a time when no software development projects existed, so later on software projects using this hardware-oriented technology as it is, which creates the problem. (“Waterfall model”, 2017)
Strengths:
1. Easy to understand
Waterfall models provide a structured approach which is easy to understand. It provides clear milestones in development processes which are easy for developers to understand and reach.
2. Easy to manage:
It’s easy to manage as each phase is properly structured and deliverables are fixed.
3. Proper documentation
In Waterfall model, documentation holds great importance. All the design specification, requirements, processes and even source codes are documented carefully. It not makes only the easy communication but also helped in the future projects to learn from mistakes.
4. No geographic boundaries
Waterfall model didn’t have geographic restrictions and it can use easily among geographically scattered teams.
Weaknesses
1. Scope adjustment
It’s not possible to adjust the scope during development cycle in Waterfall models.
2. Risk & Uncertainty
Risk and uncertainty are high in waterfall models. Designers may not be aware in advance regarding future difficulties while designing a product or feature (“Waterfall model”, 2017). So if the product is not well thought in the start, it’s very hard to revise and make changings.
3. Customer satisfaction
As the process is proceeding step by step and after the testing phase, the customer is able to view its product.so it’s not so satisfactory for the customer to wait up to the end, to see how its product looks like.
Opportunities
Helpful in betterment of future projects
Due to proper documentation in waterfall models, it may help to design similar or even more enhanced projects in the future
Threats
Hardware-oriented model
As its mainly used for hardware projects and introduced as a flawed model, so it has many short comes.
References:
Boehm, B., & Turner, R. (2005). Management Challenges to Implementing Agile Processes in Traditional Development Organizations. IEEE Software, 22(5), 30-39. http://dx.doi.org/10.1109/ms.2005.129
Dalipi, F., & profile, V. (2017). SWOT Analysis On Agile Methods. Fisnikd.blogspot.se. Retrieved 15 June 2017, from http://fisnikd.blogspot.se/2009/11/swot-analysis-on-agile-methods.html
Gandhi, S. P. (2013 ) SWOT Analysis of Agile Methodologies.
Principles behind the Agile Manifesto. (2017). Agilemanifesto.org. Retrieved 15 June 2017, from http://agilemanifesto.org/principles.html
Shahir, H. Y., Daneshpajouh, S., & Ramsin, R. (2008, August). Improvement strategies for agile processes: a SWOT analysis approach. In Software Engineering Research, Management and Applications, 2008. SERA’08. Sixth International Conference on (pp. 221-228). IEEE.
Welcome to Sidra's Blog 
Nice work.