Agile is an iterative and collaborative process of applying process and controls to achieve the objective. This methodology is popularly embraced by product development enterprises and can be used for implementing Dynamics 365 solutions.

The following is an end-to-end visual of what needs to happen in the agile methodology:

Let's look at all the moving parts:

• While agile is focused on relatively quicker achievement than the other methodologies, the important aspect for its success is knowing the big picture
• 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 popularly known as a sprint
• A plan tends to have multiple sprint cycles
• While executing these sprints, the feedback is taken and used in the backlog validation/updates

After knowing how an agile methodology functions, let's look at some salient steps in this methodology:

1. Use case scenarios preparation: This should comprise of the solution core preparation, solution roll out, support/sustenance, presales, and so on.
2. Initial requirements analysis:

• • Typically achieved in a couple of days in each sprint, led by an advisor/consultant, with sponsors and key users
  • This is important, as the list of requirements and use cases are to be prepared per sprint volume

• • This is not to be focused on a project basis, as the projects are hardly small when implementing Dynamics 365
  • An ideal start would be to first prepare the requirements outline, covering everything at a high level
  • In between the days/sessions, we must document the findings and the solution alignment upfront in order to ensure a smooth envisioning of the bigger solution

3. Solution envisioning workshops:This is one of the most critical phases, where the solution options using the SWOT technique are discussed.
4. Prototyping workshops:

• • 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/sprint so that the requirements and key decisions taken are well-documented and are kept up to date with each prototype

5. Final system build:

• • After ensuring sufficient confidence in the proposed solution, the final system can be taken for building up
  • This is also iterative in nature and involves leveraging sprint cycles to deliver functionality gradually
  • Following this stage, the classical stages can be undertaken:

• • • System Integration Testing (SIT)
    • User Acceptance Testing (UAT)
    • Training
    • Cut over/transition
    • Go live
    • Support

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