Conclusion: In the early 1990s software vendors spoke lyrically of capturing the corporate memory through use of the new products they were launching into the then emerging Knowledge Management (KM) market. Fuelled by success with document and image management solutions, then later by collaboration software such as Lotus Notes, vendors considered KM as the next blockbuster application.
- Details
- Rob Mackinnon
- Details
- Brian Bowman
- Details
- Kevin McIsaac
Conclusion: One of the dilemmas facing senior managers is whether to allocate IT expenses to a service type or absorb them as a corporate overhead. The problem is compounded when a direct expense, attributable to Cost of Sales for a service or product, is involved. If it is absorbed as a corporate overhead unit costs needed to determine pricing will be hard to identify.
When issues, such as the one above arise, managers have to wrestle with options for chargeback systems for IT services and whether the effort is justified. There is no right or wrong answer, only the preferred option.
- Details
- Alan Hansell
Conclusions: Due to a lack of transparency in the relationship between the demand for IT services and the cost of service delivery, most IT departments find themselves constantly justifying their IT budget to the CFO while simultaneously fighting with business units about additional demand for services. The major source of this dysfunction is the typical IT cost allocation, e.g., overhead or chargeback based on technical measures, which do not create the sufficient transparency to show the real cost drivers and incents undesirable behaviours.
Leading IT organisations are resolving this by recreating IT as an internal service provider with a formal IT Services Catalogue. This makes clear the relationship between demand and cost and uses economic incentives to drive the desired behaviours. It also has the benefit of aligning the service delivery expectations of the business unit and the IT organisation, thus reducing frustration.
- Details
- Kevin McIsaac
Conclusion: Stories of late and failed projects are legion within information technology. Whilst there are may be many reasons for project failure, a key root cause, largely overlooked in the literature, is failure to correctly enunciate user requirements. A less than satisfactory outcome at the requirements definition stage can only become magnified as the project proceeds.
- Details
- Rob Mackinnon
- Details
- Kevin McIsaac
- Details
- Irene Pimentel
Conclusion: Astute managers know that by developing comprehensive requirements for an RFP for IT hardware or services and engaging potential providers so they understand them, the probability they will get the best deal for their organisation is high.
- Details
- Alan Hansell
Marketing is a sometimes crude means of meeting new people and businesses must invest in it, or they wither. For instance there are many brands that have loyal customers, who have used the brand for up to 40 years; but customers don’t live for ever, and the brands inevitably suffer declining sales.
- Details
- Guy Cranswick
Conclusion: Benefit management should be an integral part of every organisation’s project management methodology. Its application provides organisations with a clear view of the benefits being realised by their IT projects. It also ensures there is a continuing focus on benefit realisation during the project lifecycle and issues that arise are highlighted and addressed.
- Details
- Terry Dargan
Conclusion: It is time for a major stock-take of model driven software development approaches within software intensive industries. Progress in the last few years in terms of developing interoperability standards for model driven tooling has not been spectacular. The term "Model Driven Architecture" has gone through the usual hype cycle, and the dust is in the process of settling. Model Driven Software Development is about breaking the 1-fits-all approach to implementation languages when needed, and entails the use of small, domain specific languages.Only in some cases can domain specific languages be bought off-the-shelf. Model driven approaches have come a long way, and enable the incremental creation of strategic software assets that can be used across a large number of applications.
- Details
- Jorn Bettin
Conclusion: Marketing can seem the very opposite of IT: lots of look and feel and rather intangible when compared with systems that must deliver on time. Yet IT can inject ideas and methods into marketing across an organisation, and an organisation that harnesses the expertise of its distinct and specialised divisions can realise positive results.
The product of greater cooperation may be several and various in the role of marketing. IT specialists may offer knowledge and expertise with practical effect for marketing strategies. Many marketing solutions involve technology solutions, and coupled with a thorough understanding of processes and the implementation of technologies, an IT manager can play an influential role to a marketing team.
- Details
- Guy Cranswick
- Details
- Brian Bowman
Conclusion: The literature is replete with reasons why projects fail but strangely one that rarely gets mentioned is, ‘appointment of an inappropriate project manager’ or equivalent. Picking the right person for the right project is not difficult providing some guidelines, related to identifying the skills, attributes and personality type preference of the person, are followed and the type of the project is clear.
- Details
- Alan Hansell
Conclusion: An ongoing process of Project Portfolio Management, managed by a Project Management Office (PMO), can lead to significant improvements in the returns achieved on funds being invested in your IT projects.
- Details
- Terry Dargan
Conclusion: The CIO organisation can be considered as the CEO organisation in microcosm. Both domains encounter similar issues: strategy, market penetration and credibility, cost reductions and so on.
As with last month’s article, this one draws on insights gained from studies of major corporations and is intended to provide inspiration to CIOs keen to improve practices and lift performance within their domain.
- Details
- Rob Mackinnon
- Details
- Brian Bowman
Conclusion: By the end of this decade, blade servers will have become the standard form factor within most datacentres. Driven by convenience, manageability and price/performance, most IT organisations will choose blades over rack-optimised to build out a low cost, highly flexible computing infrastructure. Over 90% of these systems will be based on industry standard servers (i.e. x32/64 based systems) running Windows or Linux.
As the existing IT infrastructure begins to reach the end of its economic life IT organisations should re-examine their architectural standards and evaluate the benefits of bladed based computing. They should start by first understanding the new trends in server infrastructure (see, “Refreshing IT Infrastructure? First Break All the Rules!” Feb-2006) and then comparing the value proposition of blades compared to traditional rack-optimised servers.
- Details
- Kevin McIsaac
With the release of Microsoft Vista and Microsoft Office 2007 early next year IT organisations should take this opportunity to review their desktop strategy. Early indications are that both products are significantly different from the current versions and, as with the prior major releases, will involve significant time, effort and money to implement.
While Microsoft assures us there is significant new value in these new products, particularly from “integrated innovation”, none of the IT managers I’ve spoken to were able to translate this into business value. In a recent interview with Peter Quinn, former CIO of the State of Massachusetts, he said when they looked at how staff actually used their desktops “most of the people don’t use all those advanced features [of MS Office] so it begs the question as to why I would spend all that money”. With the trend to web services (i.e., services delivered over the internet) and the availability of MS Office alternatives such as OpenOffice, he seriously questioned the value of remaining on the Microsoft upgrade treadmill.
- Details
- Kevin McIsaac
- Details
- Kevin McIsaac
Conclusion: Over the last five years agile software development approaches have become more popular, and are increasingly replacing heavy-handed methodologies. At the same time there is a growing interest in benchmarking the productivity of software projects, and in achieving process maturity that can be measured against certification standards such as CMMI. At first sight it would seem that these two trends represent two mutually exclusive philosophies. When taking a closer look it becomes clear that both trends can indeed complement each other.
- Details
- Jorn Bettin
Conclusion: Five years ago portals were essential to any worthy online strategy; without one, an organisation was not serious about the Web. That sentiment dissipated as portals were seen as symptomatic of the cyber land grab that failed. In the last two years they have quietly reasserted themselves – or perhaps never went away: Which begs the question: How does an organisation plot a course for its portal?
A portal ought to be created with a business objective, not because it’s fashionable, or competitors have one, or it’s possible with a large amount of content that is underutilised elsewhere in the organisation. From inception the portal should be planned to provide value to users, and in this context focusing on their requirements will produce a portal users keep using.
- Details
- Guy Cranswick
- Details
- Irene Pimentel
Conclusion: Some of the lessons from corporate management literature can be applied to the successful running of an IT shop. This article contains insights gained from studies of some of the world’s most admired companies and provides new ways to think about planning for the future through the application of the ‘three horizons’ technique.
- Details
- Rob Mackinnon
Conclusion: A Project Management Office (PMO) built to a model that is in sync with the organisation’s culture can, over time, have a major impact on project outcomes. To achieve this, the role and responsibilities of the PMO must be defined so that it addresses priority project related issues within the organisation. The office must then be resourced with personnel who have the skills and experience capable of undertaking the role allocated to the PMO.
- Details
- Terry Dargan
Conclusion: The emphasis on marketing eGovernment has dropped in priority. There was a Community of Practice on Marketing E-government run by Australian Government Information Management Office (AGIMO) but that government-only group is no longer meeting. In addition there is no specific area in AGIMO responsible for marketing e-government, yet marketing activity is critical to building usage, adoption and education of a product or service.
As the government is committed to delivering services on the Web, it should, as a business would, create the necessary structures for professionals to market the services. To ignore marketing wastes investments in the websites. Currently, the so-called 'operational' areas have some marketing inbuilt into their projects but there is no overall responsibility to oversee standards and market online services.
In addition a complete review of all government website usability should be undertaken to assess weaknesses and client usage. Such a review may entail revising sites. Thirdly the definition and application of “access’’ through the sites ought to be clarified: is it published information; transaction for payment, or email contact with government officers. The fulfilment of any one of these actions should be measured to report if the objective of access has been successful.
- Details
- Guy Cranswick
- Details
- Irene Pimentel
Conclusion: After 5 years of tight IT budgets many IT infrastructure components are reaching the end of their economic life and recent surveys suggest IT organisations intend to begin refreshing key systems this year. The path of least resistance is to replace these components with new items, staying with the “status quo”. However this may not be the best strategy!
Due to significant changes in technologies over the last 7 years we recommend IT organisations challenge their existing infrastructure assumptions (formal or informal) and create new rules to guide construction for the next 7 years. The greatest obstacle is not changing technologies but overcoming people’s resistance to changes in their environment.
- Details
- Kevin McIsaac
- Details
- Kevin McIsaac
Conclusion: Organisations, which enable customers to transact business over the phone must continually re-evaluate the effectiveness of their business model and exploit emerging technologies to enhance the customer’s experience. Failure to do so will put them at a competitive disadvantage.
- Details
- Alan Hansell
Conclusion: Open Source Software Development Tools are becoming mainstream. In the Java space, the number of available tools is mindboggling, and keeping up with the latest developments is becoming more and more a matter of being well-connected to the Open Source community and receiving tips and suggestions from trusted colleagues about the best and latest tools. It is no longer true that it is sufficient to keep monitoring the developments of the five largest tool vendors. Amongst the best tools some are being produced by small teams and individuals. The use of Open Source tools is also becoming established practice within traditionally conservative organisations in industries such as banking1.
- Details
- Jorn Bettin
- Details
- Brian Bowman
2006 marks a significant 50 year anniversary for computing in Australia. On July 4th 1956 it is claimed that the first program was run on SILLIAC, a valve computer that was assembled and housed at the Physics Department of the University of Sydney. Over the years much political mileage has been made on both sides of politics, about how Australians have often been at the forefront in pioneering new technologies, but have been slow in exploiting and commercialising them. However, these assertions need to be tested, certainly as far as information technology is concerned.
- Details
- Rob Mackinnon
Conclusion: Providing it has strong management support and is resourced with the right mix of personnel, a project management office can produce major benefits around:
-
management of your organisations IT project portfolio; and
-
the outcomes from these projects.
- Details
- Terry Dargan
- Details
- Kevin McIsaac
Conclusion:Government websites are not reaching the public as effectively as they might. This phenomenon is common around the world and while some sites have functional value to the public, research shows that people are confused, ignorant or unable to find what they need from many government sites.
To improve their usability government should examine practical steps to reach citizens, firstly by marketing the sites in conjunction with improved navigation and, if required, re-designing sites for users to know what they can find on them.
Secondly, refine the execution of the sites, with special reference to improving the quality of sophisticated interaction that is possible between citizens and the administration. This process of should be conducted in the context of the strategic objectives of e-government policy if they are to achieve that particular policy target.
- Details
- Guy Cranswick
Conclusion: 2006 will be the year that server virtualisation technology becomes mainstream on x86 based servers. IT Organisations are combining commodity x86 based servers with virtual machines and Storage Area Networks (SANs) to build agile, low cost server infrastructure. They are reporting many benefits including excellent TCO, rapid provisioning, increased resource utilisation and simple, low cost high-availability and disaster recovery.
Of the three core technologies used to build this infrastructure, virtual machines are the newest and most rapidly evolving. In 2006, IT organisations must understand this technology, and the vendor landscape, to ensure they make the right strategic choice for the next 5 years.
- Details
- Kevin McIsaac
Conclusion: Within the software engineering community only few people fully understand the difference between the traditional use of models in software engineering, and newer so called "model-driven" approaches. In particular the discipline of Enterprise Architecture makes extensive use of modeling techniques, and mainstream practice has not yet caught up with the model-driven approaches that are possible with today's leading edge software tools.
The problem is largely educational, and is compounded by a reluctance to step out of the comfort zone and rise to the challenge of producing precise and unambiguous models that can be used to power a highly automated software production facility. In model-driven approaches models and model transformations take on the same role as traditional source code - requiring a mindshift comparable to the one that was required in the transition from assembler programming to modern 3rd generation programming languages.
- Details
- Jorn Bettin
- Details
- Irene Pimentel