- What are Accenture’s Papers like Historically?
- What is the Primary Motivation of White Paper or Technical Document Writing?
- Why is this Paper an Exception?
The History of Accenture Documentation
Technical documentation is only very rarely published by Accenture. That is why their research can’t be considered as such, as they will alter it to increase sales. This is a problem because there is a lot of this type of commercial material on the web, that does not do much more than serve as a calling card for the company which I described in Writing Marketing Driven White Papers to Getting Business. They leave out a lot of the complexities of the topic, and simply propose that you contact them.
I have to say this is a good paper on the steps of how to setup DP and SNP should be lauded, and it is so strange for a document of value to be produced by Accenture, I thought I would bring up its anomalous nature here.
Accenture’s Technical Documentation
The paper is how technical documentation should be written. Clear, step by step and jargon-free directions of how to do things. This documentation fairly well dominates the SAP Help documentation on these topics which is close to indecipherable, which is one of the reasons this blog is popular. However, with the Accenture documentation, it is not listed who wrote the document, which I always think that is wrong. The company’s name can be on the work, but the paper was written by a person, not a computer, and they deserve attribution. So if you are interested in basic setup of the DP and SNP-environment, you will want to read this paper.
Advice on Enjoying the Multimedia Presentation
To see the full screen just select the lower right-hand corner and expand. Trust us, expanding makes the experience a whole lot more fun.
This presentation illustrates the problems with SAP support and how Brightwork SAP Support addresses these shortcomings.
What Kind of Support is This?
If this does not sound like standard support, you are right. And that is the point.
We designed our support to help our customers get the most out of SAP, not to maximize our margin or to try to protect previous sales inaccuracies. We know how to get your SAP applications working better.
To see the broader information about our SAP support see our main SAP Support Page.
Taking advice from companies like Accenture puts any project at risk of using poor fitting applications and overspending. This book covers these risks in detail.
Enterprise Software Risk Book
Better Managing Software Risk
The software implementation is risky business and success is not a certainty. But you can reduce risk with the strategies in this book. Undertaking software selection and implementation without approximating the project’s risk is a poor way to make decisions about either projects or software. But that’s the way many companies do business, even though 50 percent of IT implementations are deemed failures.
Finding What Works and What Doesn’t
In this book, you will review the strategies commonly used by most companies for mitigating software project risk–and learn why these plans don’t work–and then acquire practical and realistic strategies that will help you to maximize success on your software implementation.
Chapter 1: Introduction
Chapter 2: Enterprise Software Risk Management
Chapter 3: The Basics of Enterprise Software Risk Management
Chapter 4: Understanding the Enterprise Software Market
Chapter 5: Software Sell-ability versus Implementability
Chapter 6: Selecting the Right IT Consultant
Chapter 7: How to Use the Reports of Analysts Like Gartner
Chapter 8: How to Interpret Vendor-Provided Information to Reduce Project Risk
Chapter 9: Evaluating Implementation Preparedness
Chapter 10: Using TCO for Decision Making
Chapter 11: The Software Decisions’ Risk Component Model