Blog

  • End of an Exception: Quality Management Integrates SAP

    For testing SAP solutions, we used to depend on experts with specialized ABAP or JAVA know-how. Consistent testing of processes beyond SAP systems was quite a challenge.

    Now SAP offers SAP Quality Center by HP. It enables the customer to integrate SAP testing into a comprehensive Quality Management and testing of his IT organisation. This means that SAP testing is no longer a special discipline within Application Management.

    Through bidirectional integration of SAP Solution Manager and HP Quality Center, the precondition for the HP Quality Center to be used as a central control station for SAP testing – and thus for Test Management – has been created.

    For SAP customers, this provides a simple and intuitive approach to controlled access to HP´s Testing Tools, which HP acquired from Mercury Interactive in 2007. In addition to HP Quality Center, at that time called TestDirector for Quality Center, the tools include HP Quick Test Professional and HP Loadrunner.

    The combination of these tools allows for the test requirements to be directly derived from SAP Business Blueprints and to be used as a basis for creating test cases in HP Quality Center.

    In addition to meeting the requirements for SAP applications, HP Quality Center will make it possible to also include processes, that reach beyond the boundaries of SAP systems, into testing requirements, and to test them comprehensively. Testing teams are enabled to start testing from HP Quality Center, without being dependent on SAP specialists.

    So Requirements Management in IT can be standardized and optimized. A better transparency of testing processes will be achieved. Testing results can be compared and, through this, Compliance risks are minimized. Due to user-friendly Quality Management functions, testing automation and re-usability of the testing cases, time and costs will be saved.

    We may summarize that the integration of SAP “SolMan” and HP Quality Center bridges relevant gaps in Application Management allowing the SAP environment to be embedded into a comprehensive IT-wide Test Management.

    🇩🇪 Diesen Beitrag auf Deutsch lesen

  • Application Management Reduces SAP Costs

    In the context of large commercial software installations, the opportunity to reduce costs in the long run – all through the life cycle of the systems – is tremendous. Four fields of Application Management, pragmatically introduced and applied, are able to substantially contribute to this potential benefit.

    Project Portfolio Management
    A consistent Project Portfolio Management (PPM) which considers, evaluates, and releases all changing activities from a business as well as an IT point of view, will concentrate effort and reduce cost. In many cases, changes are evaluated from either business or technical perspective. To get to a comprehensive assessment of change requests by IT – concerning complexity and effects on other business processes or technical components – suitable tools are often missing. As a result, decisions are often based on wrong assumptions, and effort and cost estimates prove to be false.

    Quality Management
    A pragmatic Quality Management, consistently supporting the development process, and realized as an integrated tool, is often missing or insufficiently implemented. Integration of development and quality methods and tools spanning all phases from definition of requirements up to testing, will ensure completeness of testing and, above all, hold the scope of testing activities at a reasonable level. Often, Quality Management fails because the scope of testing cannot be clearly defined. As a result, complete testing gets too laborious and will be left out in parts or even completely. When attempting to put the changes into effect, then, at the latest, there will be undesirable additional costs.

    Environment Protection
    The presumably most difficult issue with large SAP and other packet software installations can generally be referred to as Environment Protection – and it holds the greatest potential for benefit.
    The number of components in modern systems is dramatically growing. The reutilization of customizing settings, data, processes, functions, program components or services helps in the first place to lower development costs. On the other hand, it increases the risk of changes taking effect on various parts of the system, intentionally or unintentionally.

    So how could be made sure that one or more changes at a time will not interfere with other functions that are, at the same time, running or being edited? There are in fact approaches to address this problem by the help of methods and tools. But most of them are to a large extent restricted to the developers´ perspective. They are inadequate for customizing activities, let alone for a business analyst evaluating the effects of changes, which means inadequate on business level. Environment Protection is getting a more and more exigent issue as the amount of internally and externally created services used in the context of SOA (Service Oriented Architectures) is constantly growing.

    Lifecycle Management
    The lifecycle of large applications is not restricted to three or five years. From a realistic point of view, we should rather talk about ten, twenty or more years. And these applications are permanently in a process of change. A consistent Lifecycle Management for all objects, no matter if they are of rather business-related, technical, organizational or descriptive nature or relate to the technical process of their development and operation, is a pressing requirement. The issue is not only relevant for the results of development – how is a result changed over a longer period of time, and for which reason? – but also for the development process itself: What does its realization look like? And, once it is clearly defined, should it repeatedly be carried out in the same way? Changes must be targeted and documented. Useful and reasonable documentation, digitalization, administration, and automation are in demand. This is a promising approach to avoid redundant and unnecessary activities in the context of system change and development.

    Summary
    Application Management projects around SAP and other large packet software installations in all kinds of industries make it obvious that the targeted investment in Project portfolio Management, Quality Management, Environment Protection and Lifecycle Management is profitable.
    With reasonable effort, they produce high benefit all through the lifecycle of the systems. But there is also a short-term advantage, the reduction of errors. Better defined system environments facilitate parallel work on projects. And it will be possible to benefit from prior projects, with respect to development as well as testing and deployment.

    Project work, in particular, clearly shows the high demand for an optimized support of methods and tools in the context of Application Management. In many cases, there is still a great deal of unnecessary manual work done – an issue bearing a great potential for software vendors and at the same time being a challenge for producers of commercial software. In our new beteo mini guides, we present a survey of Application Management tools – not only for SAP systems.

    🇩🇪 Diesen Beitrag auf Deutsch lesen

  • Happy Birthday beteo

    beteo is celebrating its first birthday! You would not believe it, but on February 21 beteo was one year old. A good reason for all friends of beteo to be happy.

    We are proud to see what has been achieved in this first beteo year:
    beteo has become a real company, headquartered in Sarnen, Switzerland, with offices in the Zurich Area as well as in Berlin. Today we have 15 people working for beteo in Switzerland, in Germany, in Kharkov, Ukraine, and in Hyderabad, India.

    beteo is a consulting and software company which helps clients working on comprehensive software installations, foremost SAP,

    With expertise and tools from partners like SAP, HP and specialized software vendors, we are involved in longterm activities supporting large customers in Germany, Austria and Switzerland. What do a market leader in steel industry, a popular sporting goods manufacturer, a large governmental organization, a top Swiss transportation company, the leading Swiss logistics organization and one of the largest Swiss life insurances have in common? They all improve their Application Lifecycle Management with the support of beteo!

    We plan to offer our first own product by May – in the beginning mainly to support our own activities, as a complementary solution to the products used by our customers: SAP Solution Manager, HP PPM, SAP xRPM, HP Universal CMDB, HP Quality Center and TimeWinner. Later on, our product offering and expertise will be extended by specialized solutions from new beteo software partners

    We are permanently broadening our experience and we love to share it with our customers, our partners and the market. In doing so, we promote best practice Application Management not only for the sake of beteo. Project Portfolio Management, Quality Management, Environment Protection and Lifecycle Management are the main disciplines addressed. Our beteo Blog and Website in English and German as well as our contributions to Wikipedia are well observed, linked and commented by the market, from analysts and our competitors alike. Gradually, our vision is becoming reality, and a global dialog on Application Lifecycle Management is in sight.

    beteo is a success story. Both, our consulting as well as our software activities are highly demanded and we are continuously enlarging our teams – not only in Zurich, but in all places where our clients are in need for our support. beteo has ambitious plans, and I am looking forward to an enthusiastic update e-mail for beteo’s second birthday.

  • SAP xRPM and HP PPM – Complementary Solutions?

    Whether in Gartner’s Magic Quadrant for PPM or in evaluations for project portfolio management tools, HP PPM (HP Project and Portfolio Mangement Center) and SAP xRPM (xAPP Resource and Portfolio Management) are always positioned as competitors. But do the specific features of these very specialized solutions justify this positioning?

    What are HP PPM and SAP xRPM ideally used for?
    HP PPM has more or less been exclusively designed to be used for managing IT project portfolios. When it comes to integration with software development and application lifecycle components like testing, configuration management databases (CMDB), and business process management tools (BPM), HP PPM shows its real strengths. The strong process engine of HP PPM cannot only control and drive organizational process, it can also control the technical execution of other software components and allows the integration of quality assurance measures and impact analysis steps. Traditional workflow tools rarely go beyond automating organizational flows. With HP PPM, it is possible to systematically control and track portfolio authorization and to include decision criteria from integrated application portfolio analysis. The following also need to be understood and fed back into the decision process: the impact of a project to the IT system, whether or not implementation of the existing system increases the complexity of an IT system, and if the complexity makes it impossible to make a change to the system. What is missing in HP PPM, are capabilities to thoroughly analyze a project portfolio financially.

    SAP xRPM has been built to support business project portfolio analysis with financial data – not for only IT projects, but for projects of any kind. Based on information from SAP BI (SAP Business Intelligence) and SAP SEM (SAP Strategic Enterprise Management), this is readily identifiable by its architecture. The tool’s integration with SAP financial business data is SAP xRPM’s greatest advantage. SAP xRPM can access the most recent financial information from the customer’s SAP system anytime. Additionally, SAP SEM allows defining and running ad hoc financial simulations, and a “What-if analysis” can be run as part of a portfolio assessment. As opposed to HP PPM, SAP xRPM shows weaknesses in process control and in the area of specific IT portfolio analysis needs. In this area, the integration with development and application lifecycle technology is missing.

    Conclusion
    The decision for the right portfolio and project management solution normally depends on its integration with the management information and tools of the project resources. Missing integration means additional effort and challenges for the planning and execution. HP PPM and SAP xRPM deliver unique integration but into two very different areas: application portfolio versus financial information. The article “PPM – Alibi without Impact Analysis” provides further information on which functions should be covered by a portfolio and project management solution, and how different vendors with their products differentiate themselves.

    The logical consequence from the above positioning could be a complementary use of both HP PPM and SAP xRPM. This way, portfolio management can profit from the strong process engine of HP PPM and the analytical capabilities of xRPM. From a technological point of view, the two solutions can ideally marry, and HP PPM provides the technological capabilities to do so. It can also integrate a lifecycle product like SAP xRPM Architecture, concepts and target use of the tools are different. For this reason, the key to a successful project portfolio management solution is to combine both tools and precisely define the requirements upfront. Only then can the combined HP PPM and SAP xRPM be designed, and failure can be prevented. HP PPM properly integrated with SAP xRPM can be PPM at its best!

    🇩🇪 Diesen Beitrag auf Deutsch lesen

  • HP PPM and MS Project – Synergy Potential with Challenges

    The upgrade from Mercury ITG 6.0 to HP PPM 7.0 entailed a much improved project management module. Project Management has been separated from the actual PPM workbench and is now available as a “zero client” over the web. The new Project Management Cockpit centrally integrates all project activities from modules like Portfolio Management and Resource Management. At a glance, the most important milestones, project status, project risks, scope changes, resource availability and issues show up. Project health or project controlling indicators like Schedule Performance Index (SPI) or Cost Performance Index (CPI) can be automatically calculated and graphically represented.

    Integration with Microsoft Project – both a blessing and a curse
    The bi-directional integration with MS Project is by far the most important step forward. This integration makes a lot of sense. HP PPM 7.0 promises similar functionality like MS Project for the management of project plans. This target is not really met by the current version though. On one side, important functions are missing, and despite very valuable cockpit views, navigating through project plans is too laborious. In addition, replacing Microsoft Project with HP PPM Project Management is difficult since MS Project, is successfully established in many places as the quasi standard to support project management. Enhancing Microsoft Project with HP PPM Project Management still corresponds to a real market need since users often see deficiencies in MS Project’s handling of resources and interdependencies in multi-project management.

    Conceptual Design – the Key to Success
    In order to optimally support project management, the proper design of the interaction between the use of HP PPM and MS Project is required for all available integration. It is of highest priority to define which function to perform in which tool and to what level activities such as phases, milestones, task groups or even tasks are planned where. With its strength in pulling together project data and in presenting management information, HP PPM lacks support for building and changing project plans. The reverse is true for MS Project. The right questions that need to be asked early on are the following:

    • Which system should have the lead?
    • Where are risks entered and maintained?
    • Where will resources be managed?
    • Where is progress tracked?
    • Which level of granularity tasks exchanged?
    • Which milestones are shown in the cockpit?
    • On which levels are resources allocated (for project phases, milestones, task groups or even tasks)?
    • On which of the above levels are work hours booked?
    • Where is the baseline of the project plan maintained?
    • Where are templates created and maintained?
       

    The same is valid for the actual project data.

    Once the integrated solution is designed, this combined system needs to be correctly customized; it is here where the devil lies in the details. When the exact impact of a setting is unknown, data exchange can easily adulterate reporting, and the integration of the tools produces chaos.

    Conclusion
    Many of HP PPM 7.0’s new Project Management features make sense and can produce great value for the customer. HP PPM’s strength for project management lies primarily in an aggregated management view and in the integration with other modules like Portfolio Management, Resource Management or Time Management, where MS Project is already the established operational project management tool in most of the companies. For this reason, a bi-directional integration corresponds to a market need and promises important benefits. But the building of such a combined project management solution is not trivial. An integrated use needs its own proper conceptual design and good experience for its implementation. Design and implementation need clear decisions on what functions are to be performed in which tool and on which granularity level activities (e.g. phases, milestones, task groups or tasks) are defined where. The impact of each setting and the interaction between the tools needs to be understood in detail. If these challenges are overcome, doors open for program and project management to profit from promising synergies of the combined Portfolio AND Project management solution.

    🇩🇪 Diesen Beitrag auf Deutsch lesen

  • SAP Process Testing – Gaps to be Closed

    Theory says that in order for effective business process testing to be done, testing requirements should already be deduced in the requirement’s phase of the software development lifecycle (SDLC). But do SAP users consistently test all the processes that are impacted by changes? Despite obvious consequences, this is hardly ever done.

    Process models are not up-to-date
    Many SAP users do not take the effort to document their business processes in order to derive quality measures and test definitions. But even when this is done, the focus of the projects is on developing a running system, and the process documentation is not maintained during the projects and are not up-to-date.

    When changes are handed over to IT operations, the routine of consistently testing all of the processes to see what is impacted by a change is extremely difficult and time-consuming. Because the link between change and processes is not currently documented, the only choice would be a complete test of all business processes. Hence, if at all, processes are only partially tested. Process testing gets marked as completed just because of the lack of prerequisites for such quality measures. Consequences are fatal. Working systems using the same programs or customizations, suddenly behave differently. Components of homogeneous, but even more so for heterogeneous SAP systems, report errors or stop working.

    It is just too laborious, too complex, and is not system supported to completely document systems from the technical objects up to the process level. After some time it becomes nearly impossible to understand why a process has changed or is implemented in a specific way. Developers in new projects, as well as maintenance programmers, are priority driven by their immediate project goals. Long-term system goals for maintainability of the overall application lifecycle are secondary at best.

    Business Process Lifecycle Management
    Understanding over time why and how processes have changed in a specific way is too hard. In SAP development methodology, a typical SAP Business Blueprint and SAP process model do not care whether individual processes that need delivered or already exist should be changed or be newly developed.
    Because it is not distinguished in such a way, it is not possible at this point in time to derive which processes were impacted from a change. Because of this, properly defining what the testing requirements should be becomes impossible. The prerequisites for a complete test will be missing later.

    This is not only true for new development. The same drawback exists with support and maintenance programming and disciplines in IT Service Management(ITSM). There is no reference of changes to process objects in their lifecycle.

    Projects need to maintain a sustainable lifecycle management for processes. At any time, it is comprehensible which version of a process was caused by which development project or service request, including what objects were impacted in which way. Consequences for later stage process testing in this way are identified early on so testing can be planned properly.

    The ideal SAP system initializes business processes with the first project. Every new project or service request, roll-ins, roll-outs, enhancements, or bug fix impacting the business process, generates a new version of it, with proper test requirements that are included and comprehensible.

    Conclusion
    In order to not let SAP process testing just be a pretense, it is a must that process documentation is maintained throughout all phases of the development cycle by new projects as well as maintenance activities. It needs to be part of the IT organization’s application lifecycle discipline. It is only in this way that the impact of projects on business processes can be understood and business process test requirements can be defined and used for proper SAP testing.

    🇩🇪 Diesen Beitrag auf Deutsch lesen

  • Global Swiss Start-ups Stand Shoulder To Shoulder – Press Release

    Collanos Software and beteo, two Swiss global start-ups, close ranks to share resources, expertise and partnerships. Collanos Software CEO Peter Helfenstein in addition takes on the COO position of beteo. Hence both Collanos and beteo can profit from the experiences and structures of both companies. Despite the intensive cooperation and the shared resources, beteo and Collanos will remain clearly distinctive companies.

    Dieter Steiger, founder and CEO of beteo as well as Advisory Board Member of Collanos, claims that “Collanos Software is an exemplary Swiss global start-up. With the help of our management team and Peter Helfenstein as our new COO, we’ll position beteo similarly well on the international market. Of course, I’m thrilled at the prospect”.

    The joint forces allow both companies to acquire a certain critical size faster and more easily. Marketing and alliance functions can be created in an earlier phase for both Europe and the U.S. Together, these two firms represent a far more interesting service and software partner for large American and European IT-companies such as HP, SAP, Apple or Sun Microsystems. It also makes them more attractive as a potential client for the near and offshore development partners in Ukraine and India. beteo and Collanos shoulder to shoulder can make joint and better use of their expertise in PR, web presence, product management and investments in infrastructure and back office.

    “We are fully aware that reduced working hours of Peter Helfenstein may be a risk for both companies. However, we believe that the synergies and lower costs obtained, will fully justify this partnership”, says Franco Dal Molin, founder, president and CTO of Collanos. “beteo is an ambitious, fast growing and profitable company with unique expertise and potential. Being able to benefit from this is a privilege and a great opportunity for our team. Even though the targeted customer segments are different, both companies have to tackle basically the same tasks. Now, we can do so in a joint effort”.

    Even with the intensive cooperation and the sharing of resources, beteo and Collanos will remain distinctly separate companies. Peter Helfenstein, CEO of Collanos Software and new COO of beteo, asserts that “despite a very close collaboration, the two global Swiss start-ups want to act autonomously to a large extent. Both are developing independently according to their own strategy. Yet, thanks to the new partner, they will do so more efficiently and effectively. We are open to alliances with additional Swiss start-ups that share global ambitions with us”.

    About Collanos Software

    Collanos is a global start-up that focuses on the collaboration needs of teams who demand a secure, cross-platform, server-less solution, on- and off-line. By leveraging open-source technologies, open standards, the familiarity of existing tools, and a global development model, Collanos delivers a friendly, all inclusive team-based solution that combines the benefits of classic client/server, web, and peer-to-peer architectures.

    Collanos was founded in November 2003 and has offices in San Francisco and Zurich, Switzerland.

    About beteo

    beteo is a visionary Switzerland based global software and consulting start-up. Its application lifecycle management solutions and services focus on keeping Enterprise software system environments flexibly and efficiently adaptable to the changing business needs of the future.

    It was founded in February 2007 as a spin-off of a leading Swiss IT Governance service company and is based in Sarnen, Switzerland, and Berlin, Germany. Among its clients are well-known companies in Austria, Germany and Switzerland.

    🇩🇪 Diesen Beitrag auf Deutsch lesen

  • beteo Miniguides – Project Collaboration

    Thanks for this comprehensive list and clarity on the PPM, PM, P±PM terminology.
    How do companies such as Clarizen fit in this categorization of yours? We consider ourselves more in line with being a Project Collaboration solution by focusing on team adoption and sharing via email integration and built in collaboration tools.
    Shall we introduce a new category ‘PCM’ – Project Collaboration Management?

    Through a comment from Clarizen’s Gil Heiman we came up with the idea of creating a beteo Miniguide with Project Collaboration tools. Every reader is invited to contribute to the quality and completeness of the list through comments or feedback.

    🇩🇪 Diesen Beitrag auf Deutsch lesen

  • beteo Miniguides – P&PM Market Survey

    Today’s PPM market is changing. The term PPM as a software category is used by Project Portfolio Management (PPM) as well as Project Management (PM) software vendors. For the sake of clarity there should be a comprehensive category including both subcategories: Project & Portfolio Management (P&PM).

    For this reason we analyze the P&PM market in detail and qualify the vendors corresponding to their functional range as comprehensive P&PM, pure PPM or PM vendors. We raised an inventory and built beteo miniguides with available solutions for the categories:

    Every reader is invited to contribute to the quality and completeness of the list through comments or feedback. We will update these beteo miniguides regularly.

    🇩🇪 Diesen Beitrag auf Deutsch lesen

  • Project Portfolio Management – Miniguide

    In the articles “PPM – Gartner Causes Confusion” and “Project Portfolio – Hype and More” we covered the issue of the nonspecific use of the term PPM.

    Today the PPM market is changing. On one hand software companies are being acquired (HP / Mercury Interactive / Kintana, Oracle / Peoplesoft, Primavera / Prosight, Serena / Pacific Edge). On the other hand the term PPM as a software category is used Project Portfolio Management (PPM) as well as Project Management (PM) software vendors. For the sake of clarity there should be a comprehensive category including both subcategories: Project & Portfolio Management (P&PM).

    In addition suppliers of Project Management tools are providing additional PPM functionality whereas PPM vendors are forced to support Project Management in their solutions. Demian Entrekin, PPM blogger on PPM Today and ITtoolbox, says that this centralization, normalization and standardization of project data and processes are inevitable. He compares the actual stage the PPM market is in today with the one the CRM market was in 10 years ago.

    For this reason we want to analyze the P&PM market in detail and qualify the vendors corresponding to their functional range as comprehensive P&PM respectively as PPM or PM vendors. We raised an inventory and built a miniguide with available PPM solutions on the market. Every reader is invite to contribute to the quality and completeness of the list through comments. We will update the list regularly.

    The miniguide is arranged alphabetically by product names. In the course of time the list should become a ratable miniguide that will be divided into P&PM, PPM and PM applications.

    Product Vendor Moduls
    Artemis 7 Artemis International Solutions Idea & Initiative Management, Product Portfolio Management, Project Management, Program Management, Process Management, Financial Management, Resource Management, Document Management
    AtTask AtTask Project Tracking, Process Improvement, Project & Capacity Planning, Portfolio Management
    Clarity Computer Associates Demand Manager, Project Portfolio Manager, Project Manager, Resource Manager, IT Portfolio Manager, IT Finance Manager, Process Manager
    Compuware IT Governance Compuware Demand Management, Project Portfolio Management, Application Portfolio Management
    Daptiv PPM Daptiv Project Portfolio Management
    Enterprise Project Management (EPM) Microsoft Project Management
    Enterprise Project Portfolio Management Oracle / PeopleSoft Project Portfolio Management
    HP Project Portfolio Management Center PPM (ex. Mercury ITG) HP Software Demand Management, Project Management, Program Management, Portfolio Mangement, Financial Managment, Time Management, Ressource Management, Deployment, Workflow, Document Management
    Innotas Innotas Request Management, Project Management, Program Management, Resource Management, Time Management, Financial Management, Portfolio Mangement
    OPX2 Le Bihan Consulting Projektportfolio-Management, Risk Management, Resource Allocation, Cost, Time
    PLANTA Projektportfoliomanagement (PPPM) Planta Projektmanagement-System, Projektportfoliomanagement, Request Management, Professional Services Automation
    PlanView Enterprise Planview Enterprise Portfolio Management, Project Portfolio Management, Service Portfolio Management, Business Process Manager
    Portfolio Manager GenSight Portfolio Manager
    Primavera P6 Primavera Project Management, Resource Management, Portfolio Management, Planing & Scheduling Management, Cost Management, Time Sheets, Collaboration & Content Management, Reportung & Analystics, Architecture
    Project & Portfolio Management Borland Demand Management, Portfolio Management, Project Management, Resource Management
    Project Portfolio Management Augeo Software Project Portfolio Management
    Project Portfolio Management ITM Software Project Management, Program Management, Portfolio Management, Financial Management
    Project Portfolio Management Software Atlantic Global Project Management, Program Management, Portfolio Management, Timesheet Management, Resource Utilization, Financial Management, Risk Management
    Project.net Project.net Project Portfolio Management
    Projectplace Projectplace Projectportfolio
    PSNext Sciforma Project Management, Portfolio Management, Resource Management
    Rational Portfolio Management IBM Project Management, Portfolio Management, Resource Management, Risk Management, Time & Expense Management
    Serena Mariner Serena Project Management, Portfolio Management
    Suite Cardinis Cardinis Project Portfolio Management
    ValueDriver4 ValueCurve Enterprise Project Portfolio Management
    WorkLenz Metier Project Portfolio Management, Investment Business Cases, Resource Management, Time Keeping
    xRPM SAP Portfolio Management, Resource Management, Program Management, Skills Management

    🇩🇪 Diesen Beitrag auf Deutsch lesen