Agility by Design - eprentise Blog

The Business vs. IT: Can't We All Just Get Along?

PDFPrintE-mail

It is no surprise that IT is not always aligned with business goals.  The conflicts arise because IT is often unaware of how the business uses the systems that IT is responsible for installing and supporting, and the business is often unaware of exactly what is involved in an IT project.  There are several other reasons for the disconnect between IT and the business.

The Fundamental Disconnects

The first of these conflicts occurs because of the way IT projects are often initiated and funded.  The business determines that they need a system to perform a certain function and decides how much they are willing to spend on the system.  IT, with a desire to bring a project in under budget, often selects an enterprise system that meets most of the needs (and is a new technology that they want to learn) without thoroughly identifying the business requirements and performing a gap analysis between the selected system and the identified requirements.  As a result, the selected system needs extensive modification to meet the business needs, or else the business user develops work arounds in the form of spreadsheets or many smaller stand-alone systems that need to be integrated with the enterprise system.  The calculated costs of maintenance and support are often restricted to that required by the enterprise system without consideration for the additional costs of spreadsheets or the stand-alone systems.  Also, the budget may include the initial costs of the license and implementing the system, but may not consider the total cost of ownership over a period of time.

Read more: The Business vs. IT: Can't We All Just Get Along?

 

E-Business Suite Organizations Spend As Much As $19 Million Annually on Finance Operations

PDFPrintE-mail

A few years ago, we conducted a survey among 264 Oracle Applications users in order to get a better idea of how businesses that use Oracle were financially structured, whether they had attempted a restructure in the past, and if so, the reasons, problems, and costs associated with fundamentally changing the underlying financial structure. Some selected results from that survey include: 

   

Getting the CFO to Pick Up His Bottom...Line: Best Practices in Cutting Costs

PDFPrintE-mail

In the past, improving business processes was the primary objective of most ERP implementations, and welcome outcomes were cost savings and productivity improvements. When ERP systems were initially implemented, the opportunities and gains in back office operations were considered significant strategic advantages. But although the strategic advantages of having robust ERP systems persist, today’s economy is forcing companies to look for ways to cut costs rather just improve their systems. The good news is that focusing on cost savings and improving ERP can go hand-in-hand and lead to better business processes if they are managed properly.

Read more: Getting the CFO to Pick Up His Bottom...Line: Best Practices in Cutting Costs

   

Everyone Takes the Hit: What You Can Do About It – 5 Key Business Metrics and Oracle E-Business Suite

PDFPrintE-mail

Before the onset of the recession and the meltdown in the financial sector, for businesses addressing change meant adapting to more cash coming in and what to do with it to keep investors happy or adapting to unprecedented growth – one of those “good problems to have”. Organizations were looking at 3, 5, and 7 year strategic plans with upwards of 20% growth year over year. A company doing $100 million in revenue might have had plans to double in size in four or five years.

As businesses were growing, building their customer base, and hiring, they may also have been planning to implement lean manufacturing or otherwise improve a host of business processes, from financial and R&D to product management, sales, and marketing. Along with the business processes improvements, IT managers were retooling their IT systems, upgrading their infrastructures, improving performance and security, or adding functionality for a host of business users.

Read more: Everyone Takes the Hit: What You Can Do About It – 5 Key Business Metrics and Oracle E-Business Suite

   

Page 1 of 3

Email Newsletter icon, E-mail Newsletter icon, Email List icon, E-mail List icon Enter your email address to sign up for our Newsletter

Sign up now

captcha
TEChanges - Agility by Design

January Puzzle

A traveler gets lost on a deserted island and finds himself surrounded by a group of n cannibals.

Each cannibal wants to eat the traveler but, as each knows, there is a risk. A cannibal that attacks and eats the traveler would become tired and defenseless. After he eats, he would become an easy target for another cannibal (who would also become tired and defenseless after eating).

The cannibals are all hungry, but they cannot trust each other to cooperate. The cannibals happen to be well versed in game theory, so they will think before making a move.

Does the nearest cannibal, or any cannibal in the group, devour the lost traveler?

Show solution...

Solution

The short answer is the traveler’s fate depends on the parity of the group. If there is an odd number of canibals, the traveler will be eaten, but if there is an even number, the traveler will survive.

To prove this, we will consider small groups and use mathematical induction to explain the solution for larger groups.

Case n = 1: this is an obvious case. If there is one cannibal, the traveler will be eaten. It doesn’t matter that the cannibal will get tired because there are no other cannibals around as a threat.

Case n = 2: this is a more interesting case. Each cannibal wishes to each the traveler, but each knows he cannot. If either cannibal eats the traveler, then he will become defenseless and the other one will eat him. So each cannibal uses backwards induction to realize that the only strategy is to not eat the traveler. The hapless traveler finds a bit of luck, therefore, and actually survives.

Case n = 3: this is where the problem gets interesting. The best strategy is for the closest cannibal to make a move and eat the traveler. The cannibal will be defenseless after eating, but ultimately he will be safe. Why is that? The reasoning is due to induction: once the cannibal eats the traveler, the resulting situation has 2 unfed cannibals and the 1 defenseless cannibal. But as we just showed above, when there are 2 unfed cannibals, neither will make a move for fear of being eaten by the other! Thus the first cannibal to make a move will be safe as the remaining 2 cannibals block each other.

We can prove the higher cases using mathematical induction. If the number n is odd, then the closest cannibal can safely eat the traveler because the remaining number of unfed cannibals is even (and by induction, with an even number of unfed cannibals no one makes a move). If the number n is even, then no cannibal will eat the traveler, for if he did, the remaining number of cannibals would be odd, meaning he will get eaten by the induction hypothesis.

Success Tips for Oracle Project Management

  • Create a standard for documentation at the beginning of your project, and hold team members accountable for completing documentation requirements as well as keeping them at and above the standards required.
  • Before promulgating user documentation or training, it’s also a good idea to choose a representative from the among the business users base to review materials first.
  • If you are not sure about the resources and budget required, obtain several estimates from people that have experience with the same size and scope of your project.
  • Be explicit, before beginning the project, what internal resources are required for execution. This includes people, infrastructure, hardware, and software.
  • Help the project champion understand the impact your project will have on the organization and how its successful completion will make him or her an internal hero or heroine for supporting it.
  • Break up your project into smaller projects (try for projects that can be completed in 4-6 months, especially early on) to get success and demonstrate momentum.
  • Make sure that your testing includes reports, upstream and downstream interfaces, customizations, enhancements, and workflows.
  • Ensure that comprehensive transition reports and meetings between departing and incoming personnel are completed.
  • Instead of spending time and resources implementing third-party reporting, consider consolidating multiple instances, moving to a global chart of accounts (CoA), and/or standardizing on a consistent calendar.
  • Include governance, risk, and compliance management as part of the project plan.
  • Finally, celebrate the successes. Too many projects focus on defects, failures, or small cost over-runs without looking at the big picture and what was accomplished.

The Analyst Corner

John Van Decker, Research VP of Gartner, states:

"A single chart of accounts allows consistency in financial reporting across the enterprise by standardizing on common metrics and reporting structures, reduces dependencies on a separate financial consolidation system, and significantly reduces the costs incurred with ongoing, complex conversions and translations."