Agile systems development provides organizations with an iterative model, allowing for quicker, more incremental results. However, an Agile SDLC is also more flexible in terms of the comprehensive project results, meaning stakeholders may have a set of requirements going in that are reshaped throughout the life of the project.
When might an organization opt for an Agile SDLC, and why? How would you describe the flexible nature of an Agile SDLC, to set stakeholders expectations upfront?
Respond to at least three of your peers. In your response, consider providing other benefits of using an Agile SDLC.
When might an organization opt for an Agile SDLC, and why?
An organization might opt for Agile SDLC when their requirement list has several vital task needed. The reason is to reduce the number of priority requirements within a timely manner. Then refocus attention on the least importance requirement.
How would you describe the flexible nature of an Agile SDLC, to set stakeholders expectations upfront?
The approach to provide a stakeholder is divide up their expectation into maybe 3 section (red, yellow, orange). It’s a color code system that might give a visual perspective for a client. The red list are those aspect that require rapid turnaround time or to be consider priority requirements. The yellow list are those aspect that require least quick turnaround time or to be consider urgency requirements. The orange list are those aspect that require not soon turnaround time or to be consider least significance requirements. A draw out conversation with the stakeholder to figure out what requirement of their project are truly necessity.
I think that an organization might opt for an Agile SDLC when they have a large project that can be implemented in phases and they want a least some of the working product now, or when they have a project where all the requirements are not known, and changes will need to be made as they discover new requirements. The great thing about agile is that the “pieces” or sprints can be developed and implemented very quickly. I would describe it to a stakeholder as this:
Separate your requirements into needs, wants, and like to have. We can implement your needs right away while working on your wants and like to have. This gets your company working on the product and giving feedback which can be addressed and implemented in another sprint. Other expectations that need to be set up front is the understanding that changes and additional requirements while they can be added or changed at any point, it will add a delay and cost to the final delivery.
I believe that an organization should opt for the Agile approach in the very beginning. Obviously this is dependent on the size and scope of the project. Especially when it comes to software development, the Agile SDLC would be a big win for all parties involved. The customers or clients who will use the product would be at a great advantage since they’re seeing the iterations of the product as it’s moving down the assembly line; literally from start to finish.
The stakeholders do come in with grand expectations, but as time passes their expectations will be reshaped as the product would be lower or higher than they expected. Although, their expectations are dependent on the how detailed and organized the phases of Concept, Inception, and Release were while moving down the Agile path.