The IEEE Computer Society team
From the Agile Manifesto Conceived for the first time at a ski lodge in the Utah Snowbird resort, development teams are adopting and changing the approach to meet their needs. They also discussed whether this is really the best solution, which raises an important question: Given the concept of software as a multi-layered technology, what role can Agile play? This even corresponds to the principle of multilayer technology? If so, how and where does it intersect? Read on to refresh the Agile approach and how it can coexist with the principle of software as a multi-layered technology.
Want more technical news? Subscribe to the ComputingEdge newsletter today!
Quick Refresh: What is Agile?
Agile refers to a methodology – not a technology – for the continuous delivery of valuable software. The approach is designed to address several key issues facing developers. For example, how can you maintain a consistent development schedule if customers or decision-makers constantly want change? Also, how can you provide a solution that meets the needs of all stakeholders, including security teams, C-suite, user interface (UI) and user experience (UX) people and end users?
Agile solves these problems in several different ways, but mainly includes the following concepts:
- Quickly create many working iterations of a software solution
- Involve a wide range of stakeholders in all phases of the development process
By producing many functional iterations, you get a product that can be tested, researched and adjusted on an ongoing basis, as opposed to a single climax product that everyone hopes is appropriate.
With the participation of many stakeholders, you can include their input in different phases, ensuring that the end result meets their needs. This is more effective than creating an application and hoping that it meets the needs of stakeholders, just to understand that you need to redesign it first because one or more critical requirements have been ignored.
How does Agile fit into software as a multi-layered technology?
Considering software as a multi-layered technology involves segmenting the development approach according to four elements:
- Focus on quality
- process
- Method
- Tools
For many projects, Agile can fit very well into the Process category. This is because the process is divided into four elements, all of which are included in the Agile framework:
- Communication
- Planning
- Modeling
- Construction
- Deployment
How to include Agile in the process category?
The easiest way to use Agile within the software as a multi-layered solution is to simply place it in the Process category, using it to replace other process methodologies. In other words, you make your process flexible.
This would include using Agile principles to guide your communication, planning, modeling, building and deploying your product.
Whose job is it to make Agile work in a multi-layered frame?
To ensure that your process is flexible, it is best to enlist the leadership of Scrum Master. While Agile is a high-level principle, Scrum is the framework used to actually create solutions. In the Agile methodology, the work of your Scrum Master fits perfectly into the five elements of the process, in particular the Scrum Master:
- Designs communication protocols
- Creates the framework for planning iterations and sprints
- It regulates who and which technologies participate in the modeling of the solution
- Guides individual players and teams through software development
- Develops implementation and maintenance strategy
Thus, incorporating Agile into a multi-layered approach to development is a matter of relatively easy integration and operation: Your process becomes Agile. To keep up with the latest developments in the world of software design and implementation, subscribe to the IEEE Computer Society newsletter today.
