ERP PeopleSoft Consulting

As we move through the discussion on Day 2 and looking at the project scope, constraints will be identified.  Be sure to provide your client and consulting team with examples of what might be a constraint.  A constraint is something that limits your degree of freedom.  Limited development resources might be a constraint.  Constraints might be economic, political, functional, technical and even environmental.  Be sure to document the constraints and work with the project team to ensure they are identified.

Second to constraints would be assumptions.  You make assumptions regarding many aspects of the project.  Assumptions represent opinions that have not or cannot be readily or easily proven; yet they are expected to be true.  An assumption that is often made in organizations is that the executive team is on board and giving total support to the project.  Sometimes an assumption is made that the organization has a specific requirement, only to find out in the fit/gap that the system cannot support the requirement.

So far we have covered many discussion topics in Day 2 and it is important to facilitate interaction and participation by the team.  The one week workshop packs a great deal into the first week that not only sets the stage for the project but also ensures the success of the project.  Think about the deliverables that will be produced as a result of the workshop.

This entry was posted on Tuesday, June 9th, 2009 at 8:23 pm and is filed under Consultants, Deltas, Implementation, PeopleSoft Finance, PeopleSoft HCM, Project Management, Project Planning, Questions, Training, Training and Development, Upgrade.You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.