Essentials of Supply Chain Management, 2nd Edition:- This is written by Michael H. Hugos and contains valuable tips, techniques, illustrative real-world examples, exhibits, and best practices in the are of SCM. This handy and concise paperback helps to stay up to date on the newest thinking, strategies, developments, and technologies in supply chain management. A quite useful possession indeed. This can be bought at most economical price here
Modern ERP: Select, Implement & Use Today’s Advanced Business Systems:- This book is written by Marianne Bradford and what is unique about this book is that it contains contributions from organizations like NetSuite, Microsoft, SAS, GlaxoSmithKline and Deloitte Consulting. This makes this book a much practical document to read and implement in rela life. Incidentally, this is one of the best selling books on ERP these days on Amazon
Learning new tools and technologies has become part of daily chores of any IT professional. There is no way out. Or there is no good reason of why one should not learn new things. I personally am a tech savvy guy and always in lookout of learning new things. The interest is not just to learn things pertaining to data warehouse and BI but everything, which comes on way. The only thing that the new tools/technology I learn should have some fundamentals or concepts to take home.
During this last 6-7 years of being into IT, I have learned numerous theories, technologies, programming languages, tools etc. Most of them were through self-learning. But this self-learning was dependent on all my previous learnings, which I inculcated in the past and without which all this self learning would not have been possible. Today I just picked one more tool/technology to build some understanding on it. I don’t have the access to the software but just the documentation. This is one among few tools/technology I am trying to learn for which I don’t have the access of the software. Though I have hands on extensive hands-on experience on a similar kind of technology by another vendor.
This whole thing lead me to think of how can one approach taking up new tool/technology. Possibly three ways which came into my mind:
1. First hit the document.. get some background. and then come to the tool/hands-on and then again go back to the manuals/references. .. an then back to hands on.. May be over the period doing both things simultaneously.
2. First hit the tool ..let your intuition take over the wheel first.. play around stretch your understanding/intuition… and then come back to references/manual/docs/some text and then back to the tool. Over the period both doing both things simultaneously.
3. First attend some seminar ,some talk, some discussion ( as good as 1 but instead of text you are get into more live things) and then hit the tool may be then back to the manuals tools.. come back to tool/hands-on then go back to discussion and so forth. May be I call it Spaghetti approach. In this approach it could be that you start with Books first and then tools an then talks or any combination.
Which to choose?? Time and availability of resources can give the right call for this.. I keep trying all this approaches. Most of the times approach 2 is a good deal for me. Approach 1 is something we have been trying since the college days. First read about the “c” language, listen some lectures… and then get to the labs for some hands-on. And that was good since one didn’t had so many fundamentals/concepts built up, not so much of exposure to the tools/languages of similar kind. Again like all my postings, there is no need to reach to conclusion of which is better and which not. Depends like everything else. My idea here is just to bring out some points.
The best project is well thought out and fully researched. It is not limited to a budget and time line, but focuses on tasks, owners, goals, and milestones. It begins at the time of software selection and goes well beyond go-live. And although most projects will stumble along the way, successful implementations that actually end on time and on budget are quite possible if managed properly.
we preach the importance of a solid selection and implementation plan. So much so, that we will voluntarily chose not to participate in the evaluation project if we feel the prospect’s selection process lacks structure. Why would we ever do that? Because the company will never be happy. If they do not know how to evaluate their own requirements or communicate those needs to others, they’ll never be able to successfully evaluate if a vendor’s ERP solution is a good fit for their unique requirements. And unfortunately if we can’t review their requirements with them, we cannot help evaluate if our package is a good fit either.
A solid evaluation project for new ERP software is broken out into some fairly set project goals and milestones. Regardless of the company, a proper project plan should include:
– A Review of Key Business Objects & Long-term Goals
– A Formation of a Selection Team & Project Leader
– An Ongoing Project Plan
– Research & Budget Preparation
– Clearly Defined Requirements & Project Goals
– Vendor Demonstrations & an RFP
– Reference Checks
– Data Migration
– Testing, Testing, & More Testing
– Training, Training, & More Training
In reality, you can easily execute on time, on task, and on budget by controlling the entire project through conception and go live. Led by in house or through an outside professional, flawless executions of software implementations are possible. They do not happen by chance, on their own, or without effort. But they are certainly a reality if given the right team and project plan.
I almost forgot about it. One of my friends reminded of it, and so i decided to write something. Enthusiasm is infectious. No matter regarding what – good or bad – if you are enthusiastic about it, you will get people involved. You will infect others.
Enthusiasm is a communicable disease. It has no cure. It has no medicine. It is a sweet poison which will make you feel better when you are sick with it.
But some people will find a way to get away from any kind of disease. And i have seen such people who have a shield around them, which will not let them get infected. They have a shield of NEGATIVE THINKING and ATTITUDE that will not let them think good and be enthusiastic. Enthusiasm can not go thru that shield, and people do not get infected.
That is one of the reasons i forgot about my infectious enthusiasm, because i have a few people around me who are shielded. They are vaccinated. And if i stay around them for long, I will loose my powers of infection. They will become penicilling for me. God does not want that, and so he sent me a doctors advice. Thanks to my friend for being a Hanuman for me and remind me of the powers i have.
My enthusiasm has helped me a lot. In achieving things, in reaching places, in creating success. Even making new friends. I wish i can stay the same, and be more enthusiastic in future. I wish to infect more and more people every day, so that they can go and infect others. After all enthusiasm and energy are the things that make this world moving.
Go ahead, Spread it. Enjoy it. Enthusiasm is the key to success.
courtesy – Ashish Jain — http://indore360.com/portal
10 Tips for Career Success in Office, especially applicable in information technology and service industries
1. Find ways to learn continuously.
2. Find ways to improve whatever you do. Be willing to incorporate the new ideas that you learn in #1.
3. Do your work completely and with pride.
4. Be true to your own values.
5. Clear up those irritations (energy drains) so that you can devote your energy to your work.
6. Practice self-care so that you feel good about yourself.
7. Keep work in perspective so that you hav! e time for other parts of your life (family, friends, hobbies, volunteer work).
8. Listen carefully to everyone. Managers need to walk around and talk to employees and customers.
9. Network within your company and outside.
10. Delegate tasks when appropriate and empower those doing the work to do it their own way.