Delivery methods are the different ways you can provide business process, system task and quick reference documentation to an end user. These methods include: Hard Copy User Guides - Provide detailed information about business and system tasks in a paper format. Typically include copies of the screens and menu paths to enhance usability. Eagle does not recommend production of hard copy user guides unless the client culture and/or technology environment does not allow for a

The responsibility of Business Readiness, then, is to integrate with the project during development, learn and validate the processes, methodologies, and quirks of the system, and then identify the components, actions, actors, and milestones that will assure Business Readiness for the end user. And in doing so, those additional orphan tasks are identified and tracked to assure success. In that vein, think of Business Readiness as QA for the user acceptance portion of the proj

What is documentation? Documentation records information about tasks, procedures or specifications. It can be written on paper, or viewed online. People who need to know the recorded information read the documentation to learn the tasks, procedures, or specifications. These “people” are typically referred to as users. What needs to be documented for system users? On enterprise system projects, we always recommend that you document: Business Processes - A particular busines

There is always a significant amount of interaction between the OCM group and the project management/core team in a project implementation. With the integration of the Business Readiness concept, an additional component includes the understanding that many of the “required” tasks (from a project and business success point of view) which must be done, don’t always have an identified “home” or “owner”. From a Project Management perspective, when that happens, the group/functio

I recently attended SAPPHIRE where there was quite a bit of discussion around SAP Enable Now (Formally WPB). I must say I was surprised by the number of people I spoke with who did realize the true value of the tool they had purchased. That is not say they were not happy with the tool they were. But they were also using only a small portion of the tools capabilities, mostly around developing and deploying simulations for their SAP system. What the people I talked with di

We have designed our Talon methodology based on our philosophy surrounding documentation and training. Our underlying philosophy is: Get the users ready. Eagle ensures that end users know how to perform their system processes, and that they take ownership of these new processes. We do this through the right combination of documentation, training and change communication. Customize the solutions. Eagle creates documentation and training that conforms to your business proce

The target audience for the methodology is: Eagle Consultants. The primary audience of the Eagle Talon methodology. Consultants will use the methodology as an overall framework within which they will develop an end user support program for a client. Client Partners. Many clients choose to partner with Eagle in the development of the user support program by adding their own internal resources to the training and documentation development team. These resources can use the m