Agile Manifesto (Agile Alliance)
Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan Agile emphasizes simplicity, instead of using complex, lengthy documentation to define requirements, the process is streamlined to avoid unnecessary bureaucracy. Requirements are usually captured in a minimalistic format, such as user stories. This light weight approach reduces the time spent on documentation, allowing more focus on delivering value quickly.
Agile encourages face-to-face communication or close collaboration through tools like video calls, which helps quickly address any questions or concerns. This is preferred over lengthy email chains or official meetings, as it fosters quicker decision-making and reduces misunderstandings.
Requirements are not set in stone upfront. Business analysts focus on defining the most immediate needs and then iterating over time. Along with user stories, acceptance criteria are defined to clarify the conditions that must be met for the user story to be considered complete. These criteria are often discussed and refined in conversations between the business analyst, stakeholders, and the development team.
12 Principles
Customer satisfaction through early and continuous delivery of valuable software.
>> Agile focuses on incremental releases. Welcome changing requirements, even late in development.
>> Requirements are seen as evolving and not set in stone. Deliver working software frequently.
>> Team releases parts of the software regularly, keeping the customer engaged and reducing the chance for misaligned expectations. Business people and developers must work together daily.
>> This keeps communication open and ensures that everyone understands the project’s goals and can adapt to shifting requirements. Build projects around motivated individuals.
>> Trust is critical. Motivated and well-supported individuals are key to a successful project. The most efficient way to convey information is face-to-face conversation.
>> While documentation is still important, the most effective way to communicate within a development team is through regular meetings, discussions, and interactions. Working software is the primary measure of progress.
>> Agile shifts the focus from documentation or planning to actual functionality. If the software works as expected and adds value, then progress is being made. Agile processes promote sustainable development.
>> The team should work at a pace that is maintainable over the long term. This avoids burnout and ensures consistent, high-quality delivery. Continuous attention to technical excellence and good design enhance agility.
>> Regular attention to the technical details and keeping the design clean and maintainable helps prevent technical debt and keeps the software adaptable to future changes. Simplicity - maximizing the amount of work done - is essential.
>> The goal is to simplify processes and features. Rather than building overly complex systems, Agile emphasizes doing only the necessary work, which helps to reduce waste and keep the team focused on delivering core value. The best architectures, requirements, and designs emerge from self-organizing teams.
>> The team itself is responsible for coming up with the best solutions, including the architecture, design, and implementation of requirements. At regular intervals, the team reflects on how to become more effective.
>> Agile promotes regular retrospectives, where the team evaluates what went well and what could be improved. 
Agile Business Analysis
