A project team depends on the type of project. When we implemented the Canadian government and DOD, I'd bet there were over 100 on the team. On the other hand, when we built the initial archiving system for SAPPI Paper, there were 3 of us. Each company starts with a team that is more sized to what they can afford, than to what they need. The project is then tailored to those limits. Now, for the CEO advisor, that really has no real SAP component to it. Because you are an experienced and successful business man, you are selling your experienced advice to CEO's who have businesses that are in trouble. The SD component comes in because there are never enough hands around. So you start "helping out" by working their SAP SD issues for them. I suggest SD, because that module is much more forgiving than FICO. You try helping out with FICO when you don't have the appropriate (and massive) required expertise, and you'll find your self handing from the nearest yard arm. Neal
| | | ---------------Original Message--------------- From: Anee saini Sent: Tuesday, August 23, 2011 9:27 AM Subject: Returning to SAP (FI/C0) with knowledge from 10 years ago Thank you for your valuable feedback, greatly appreciated. What are the most challenging issues in an SD role or CEO advisor for someone like myself, I assume it would be understanding the module itself? Just curious to know what is a typical size of a team on a project? Many thanks | | __.____._ Copyright © 2011 Toolbox.com and message author. Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251 | | R. N. Wilhite SAP Career Helper
Posted helpful replies on 5 threads in a group to earn a Bronze Achievement Popular White Papers In the Spotlight View the "Managing the Application Life Cycle" webinar and learn how organizations optimize their SAP applications. _.____.__ |
Aucun commentaire:
Enregistrer un commentaire