Microsoft knows that selecting a partner who adopts a structured methodology is crucial for project success. This is why deep expertise with Sure Step is now mandatory for Microsoft Gold Certified Partners such as TVision Technology. We had been using the SureStep methodology for many more years before it became mandatory; firstly because it is important to follow an agreed methodology and secondly because Sure Step was developed specifically for Dynamics projects.
Microsoft Dynamics Sure Step provides a complete methodology—including project management discipline and field-tested best practices—plus user-friendly tools that enable you to more successfully deploy, migrate, configure, and upgrade Microsoft Dynamics solutions.
Sure Step was first developed for NAV projects over 10 years ago and proved so successful it was adopted by Microsoft for use with all Dynamics products. In 2010, when Microsoft revised the Partner Accreditation Criteria, Sure Step expertise became mandatory. At TVision we have the qualified individuals and the track record of using Sure Step.
“In my 25 years in the IT industry, I have never seen a system go in with so few issues.”
Lee Kingshott, IS Director, Brookson
Following the success of Sure Step for implementations, Microsoft introduced a Solution Selling methodology that compliments the post-sales experience. At TVision we think this is great as it helps set expectations from the first contact you have with us all the way through to post-live support.
Fundamentally an implementation methodology is designed to ensure the greatest chance of project success. If the methodology does not suit your organisation then there is conflict with that aim; therefore, we recognise that certain aspects of the approach may need to be flexed to suit each client.
There are three core aspects to any implementation:
Understanding Requirements and Agreeing Scope phase involves documenting requirements, comparing these to standard functionality and agreeing the scope for what shall be delivered. We can discuss and agree the level of detail required in this phase. Typically that will depend on the approach to be taken for the next phase, System Build / Configuration. For example, if you prefer an agile development approach (such as SCRUM or DSDM) then the requirements and scope will need to be analysed in greater detail than if you are happy to adopt an interactive design / test led approach.
System Build / Configuration may involve development; it will include workshops with your project team to test the configuration of the solution. Once your team is happy with the end-to-end solution then it’s ready to replace your live system.
System Migration consists of all the tasks required to take the configured software and make it ready for use; primarily this will be data migration, any document tailoring (branding) and end user training.Back to top Back to All Knowledge