180
Dear All,
Hi,
I am new in this community. Our company is going to implement Dynamics GP 10 and I am leading that project. I dont have any previous experience of GP 10. But I am comfortable with ERP iScala 2.2. We have a kick off mieeting with the partners in this week.
Anyone can please guide me from where to start and what to start.
Hoping to hear soon,
Regards,
Muhammad Imran
*This post is locked for comments
Well, I too agree with your stance over customization but context may be different for all of us. I've seen clients/organizations for going major customisations in GP that really takes time to be a mature one. However, I'm still certainly against any kind of development in GP. Please go through the following link:
I totally agree with the writer's point of view.
I agree with Ian on the training approach. Identify your 'early adopters' in key business areas. These are the people who express a desire to learn the software. Train them as your Super Users. Provide other users with the training they need to process their daily tasks and then once they've gotten their feet wet, so-to-speak, have your Super Users provide recurrent, expanded training specific to each group of users.
Also, recurrent training even after Go Live helps people keep their skills sharp. One thing I've done for clients is hold 'Lunchtime Learning' sessions on a monthly basis. Bring the folks to a conference room, feed them, and offer some tips and tricks to enhance their experience with the software. They eat it up (pun intended).
Good luck!
Hi, I agree with the other advices given by Frank and Mariano. In addition, some other things you might want to consider are 1. A good start point might be your Chart of Accounts. Get this defined and imported as early as possible. 2. Set up a test company and manually process some data so you can test your processess / model your business. Then keep restoring the live company into the test as you go along so that you have up to date data to play around with (say for developing FRx reports etc).
There are two schools of thought on training. - 1. Run formal training days for users upfront before you go live. 2. Train a super user during implementation (probably yourself?)...and then train people on the job - ie train them how to do their daily tasks individually sitting at their PC's...then at a later date when people have got to grips with the system, and have found their way around, you can run formal training.
Personally, I rather the second approach. I find that when it comes to the formal training people have more relevant questions etc. However its hard to do in larger companies, where the sheer number of users make this approach impractical.
Bounce any issues you might have into the forum.
Best of luck.
Sorry, I really have to disagree very strongly with this last post. I have seen another similar post on the forum in the past advising someone not to go near any kind of customisation and my response was the same...If you have not seen stable customisation so far...then the problem is with your developer and not the system. This kind of statement is very unhelpful and gives out the worng message. Saying 'Personally, I prefer to stay from customisation' is one thing - leading a user to believe that all customisations for GP are inherently bad is another.
There is nothing inherently wrong with GP that makes it a bad candidate for customisation. Dexterity is a fine product as are all the other tools available. I have been developing modification / customisations / add-ons etc for GP since version 2. Do not be afraid of tackling a development project for Dynamics GP. As with everything else to do with GP, its down to the quality, experience and ability of your Partner.
And yes, do let us know if there is any query.....
Adding to above stated valuable suggestions, 1) please do include some experienced member (MSGP 10.0) in your internal implementation team (Phase or module wise), 2) Do not skip/miss technical and functional training sessions. 3) Keep close eye on 'Solution Design Document - Suggested flows provided by your GP partner' and atleast do try to apply it on your business processes. 4) Verify the results/outcomes (Reports/Prints) 5) Most importantly, DO NOT GO FOR Customization (If it is necessary - then test all the flows properly coz I've not observed stable customization so far).
Best of Luck.
Muhammad,
You are in the unevnviable position of not knowing the product but yet leading the implementation of it. You will have to rely on your partner heavily for advice and guidance.
However, my advice to you as project manager is threefold - 1. Make absolutely certain that the external implementation team understands your business processes thoroughly prior to configuring the software, 2. prepare your internal team (implementation and end users) for the upcoming changes in the way data is processed, and 3. do not skimp on training!
Number 1 is important because you want to be able to leverage the capabilities of the software and keep customizations to a minimum. Number 2 is important because the way people do things will change. This is true with any ERP implementation. Do not let users try to fit the software to existing business processes because 'that's the way we've always done it'. This also is important to keep customizations to a minimum. Number 3 is important because people need to know ALL the features of the software that are designed to make their jobs more efficient and effective.
As you might imagine, these are the 3 areas I see over and over again that are not adhered to strictly in ERP implementations but which have a major impact on the ultimate success of the project.
Good luck and let us know how it goes. Oh, and welcome to the forum!
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (