Fact Sheet Paper
Agile methodology has become a popular approach to project management in recent
years. Unlike traditional waterfall methodology, which is linear and sequential in nature, Agile is
iterative and flexible, allowing for changes and adaptations to be made as the project progresses.
In this information paper, we will present and defend the use of Agile, particularly in comparison
to the traditional waterfall approach. We will also highlight the impact of Agile on scope, roles,
and responsibilities, with a specific focus on how business requirements are captured.
Agile methodology is built on the principle of incremental and iterative development.
This means that instead of delivering the entire project at once, it is divided into smaller,
manageable pieces called iterations. Each iteration involves planning, design, development,
testing, and review, resulting in a working product at the end of each iteration. This approach
allows for constant feedback and adaptation, ensuring that the final product meets the needs and
expectations of the stakeholders. Whereas, normal and first approach to waterfall method is
sequential and linear to project management. There are different stages for the different phases.
Previous is mandatory to complete to start the next one, making it difficult to make changes or
adaptations once a phase is complete. This can lead to issues with scope, time, and budget, as
changes can cause delays and additional costs.
Agile methodologies allow for more flexibility and adaptation to changing project
requirements, while waterfall methodologies rely on a predefined set of requirements and a fixed
timeline. This means that Agile teams can adjust the project as needed to meet changing
customer needs and project complexities, whereas waterfall teams are limited by the initial scope
and timeline. Agile approaches prioritize identifying and mitigating risks early in the project,
whereas waterfall approaches tend to rely on more traditional risk management strategies such as
contingency planning. This means that Agile teams are better equipped to handle potential issues
as they arise, rather than waiting until the end of the project to address them. Agile
methodologies emphasize collaboration and communication among team members and
stakeholders throughout the project, whereas waterfall methodologies tend to be more
hierarchical and siloed. This means that Agile teams can benefit from more diverse input and
insights, leading to better outcomes and higher customer satisfaction.
The impact of Agile on scope, roles, and responsibilities is significant. In Agile, the scope
of the project is flexible and can change as needed, allowing for adaptations to be made
throughout the project. Roles and responsibilities are also more collaborative in Agile, with the
team working together to deliver each iteration. This approach requires a dedicated product
owner who works closely with the development team to capture and prioritize business
requirements.
Capturing business requirements is a critical aspect of any project, and it is done
differently in traditional project management versus Agile/Scrum project management. In
traditional project management, requirements are often captured in a detailed project plan or a
requirements document. These documents are often lengthy and detailed, leaving little room for
changes or adaptations. Requirements are captured through user stories in Agile/Scrum project
management. A user story is a short, simple statement that describes a requirement from the
perspective of the end-user.
References
Cockburn, A. (2002). Agile software development. Pearson Education.
McConnell, S. (1996). Rapid development: Taming wild software schedules. Microsoft Press.
Kniberg, H. (2015). Agile product ownership in a nutshell. C4Media Inc.
