Agile methodology for Microsoft Dynamics 365 Finance and Operations one version D365FO

Agile methodology for Microsoft Dynamics 365 Finance and Operations one version D365FO

Salient feature in Agile methodology:

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

Initial requirements analysis:

Typically achieved in a couple of days in each sprint, led by an advisor/partner consultant, with sponsors, stakeholders, and key users.

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, must document findings and solution to make alignment upfront in order to ensure a smooth envisioning of the bigger solution

Solution envisioning workshops: This is one of the most critical phase where solution options using the SWOT technique are discussed.

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

Final system build:

After ensuring sufficient confidence in the proposed solution, final system can be taken for building up.

This is iterative in nature and involves leveraging sprint cycles to deliver functionality incrementally.

After this stage below are some key activities to be undertaken:

System Integration Testing (SIT)

User Acceptance Testing (UAT)

Training

Cut over/transition

Go live

Support