To test SAP effectively requires the involvement of the end users of the systems, Without this, testing the synthesis of the organisations business processes and the SAP business modules (such as FI, HR, MM and PP) can become either overburdened with documentation or unrepresentative of how the SAP system will really be used.
Yet these users have two handicaps: they are very rarely trained testers and they often have a business as usual job to run while they do the testing as well. These mean they have little time to spare for testing and what time they have is not spent as effectively as they would like. A double whammy that often limits the value of acceptance testing SAP implementations.
This course on SAP acceptance testing is designed to address that very problem. It is also suitable for many of the other participants in SAP UAT such as business analysts, SAP implementors and managers of acceptance test.
Monday, March 23, 2009
Saturday, March 21, 2009
The culture of acceptance
This is an extract from an article in Newswireless about changing the culture of acceptance for IT project failure.
All businesses would wish to implement strategic IT projects more quickly, economically and surely. Above all, they need to eliminate the risk either of failure or of the project taking so long that the business needs no longer match the aims of the project. There are two important trends which will help: Agile methodology and ‘Software as a Service’ (SaaS).
The Agile approach to IT implementation offers companies a quicker and surer means of delivery. Agile delivers business benefits earlier and unlike Prince2 or Waterfall, allows feedback from the end users without having to wait for user acceptance testing.
Prioritised requirements can be bundled into short “Sprints” of work during which analysis, design/build and software testing are executed in rapid succession. In this way Agile provides a platform for projects to be tested frequently against business aims and for new system functionality to be demonstrated to end users along the way. This enables the business and IT provider to work closely together, with stakeholders involved throughout the project.
All businesses would wish to implement strategic IT projects more quickly, economically and surely. Above all, they need to eliminate the risk either of failure or of the project taking so long that the business needs no longer match the aims of the project. There are two important trends which will help: Agile methodology and ‘Software as a Service’ (SaaS).
The Agile approach to IT implementation offers companies a quicker and surer means of delivery. Agile delivers business benefits earlier and unlike Prince2 or Waterfall, allows feedback from the end users without having to wait for user acceptance testing.
Prioritised requirements can be bundled into short “Sprints” of work during which analysis, design/build and software testing are executed in rapid succession. In this way Agile provides a platform for projects to be tested frequently against business aims and for new system functionality to be demonstrated to end users along the way. This enables the business and IT provider to work closely together, with stakeholders involved throughout the project.
Subscribe to:
Posts (Atom)