Agile is an iterative and collaborative process of applying processes and controls to achieve an objective. This methodology is highly popular in product development scenarios. Let's look at the following diagram for an end-to-end view of the agile methodology:

Let's look at all of the moving parts:

• While agile is focused on relatively quicker achievements than the other methodologies, the important aspect for its success is knowing the big picture well in advance.
• Using the big picture, a list of features/requirements/cases are elaborated and carved out into multiple plans.
• Each plan is then taken into execution, which is known as a sprint.
• A plan can have multiple sprints/sprint cycles.
• While executing sprints, feedback is taken and used in the backlog validation/updates.

Let's now learn salient activities in the agile methodology:

1. Use case scenarios preparation: This should be comprised of the solution core preparation, solution roll-out, support/sustenance, presales, and so on.
2. Initial requirements analysis: This is characterized by the following:

• • This is typically achieved initially in each sprint, led by an advisor/partner consultant, with sponsors, stakeholders, and key users.
  • A list of requirements and use cases needs to be prepared per sprint volume.
  • An ideal start would be to first prepare the requirements outline, covering everything at a high level.
  • In between sessions, you must document findings and solutions to make alignment upfront to ensure a smooth envisioning of the bigger solution.

3. Solution-envisioning workshops: This is one of the most critical phases where solution options using the Strength, Weakness, Opportunities, and Threats (SWOT) technique are discussed.
4. Prototyping workshops: This stage is characterized by the following:

• • These are workshop sessions with sponsors and users, demonstrating the proposed solution (fits, workarounds, and gaps).
  • This is used to validate the solution approach and its buy-in by stakeholders.
  • This phase is conducted in iterations/sprints so that the requirements and key decisions taken are well documented and are kept up to date with each prototype.

5. Final system build: This phase includes the following:

• • After ensuring sufficient confidence in the proposed solution, the final system can be taken for building.
  • This is iterative in nature and involves leveraging sprint cycles to deliver functionality incrementally.
  • After this stage, the following are some key activities to be undertaken:

• • • System Integration Testing (SIT): Refer to Chapter 11, Testing and Training, for more details.
    • The user acceptance testing (UAT): Refer to Chapter 11, Testing and Training, for more details.
    • Training: Refer to Chapter 11, Testing and Training, for more details.
    • Cut over/transition: Refer to Chapter 11, Testing and Training, for more details.
    • Go-live: Refer to Chapter 12, Managing Go Live and Post Go Live, for more details.
    • Support: Refer to Chapter 13, One Version Service Updates, for more details.

After understanding the CRP and agile methodologies, let's now learn about the traditional waterfall methodology.