Joseph Sweeney

Joseph Sweeney

Dr. Joseph Sweeney is an IBRS advisor specialising in the areas of workforce transformation and the future of work, including; workplace strategies, end-user computing, collaboration, workflow and low code development, data-driven strategies, policy, and organisational cultural change. He is the author of IBRS’s Digital Workspaces methodology. Dr Sweeney has a particular focus on Microsoft, Google, AWS, VMWare, and Citrix. He often assists organisations in rationalising their licensing spend while increasing workforce engagement. He is also deeply engaged in the education sector. Joseph was awarded the University of Newcastle Medal in 2007 for his studies in Education, and his doctorate, granted in 2015, was based on research into Australia’s educational ICT policies for student device deployments.

Read latest work...

Connect with Joseph

Have a specific question for Joseph Sweeney?

Email

Conclusion: Creating a lightweight governance framework for mobility is essential in ensuring that mobility applications are developed quickly and effectively, and are aligned to organisational objectives. The ideal mobility governance framework provides an agile environment to enable solutions to be developed using shared architectures, and focuses on "what can be done" rather than "what can't be done.” The key is to ensure that the governance framework remains focused on decision-making, as opposed to restricting mobility “run-away mobility deployments”.


Read more


Related Articles:

"Coping with Mobility - Part 3: aligning generic use cases to application development approaches" IBRS, 2012-04-30 00:00:00

"Coping with Mobility - part 1: mobile architecture and the enterprise" IBRS, 2012-02-28 00:00:00

"Coping with Mobility - Part 2: First steps towards a holistic mobility strategy" IBRS, 2012-03-29 00:00:00

"Coping with mobility - part 5: developing the strategy" IBRS, 2012-10-28 00:00:00

"Coping with mobility Part 6: Work context" IBRS, 2013-06-26 00:00:00

Conclusion: IBRS has found that many organisations’ mobility needs can be covered by just one or two “generic use case” categories, thus many user demands for mobility can be met with just one or two development approaches.


Read more


Related Articles:

"Coping with Mobility - part 1: mobile architecture and the enterprise" IBRS, 2012-02-28 00:00:00

"Coping with Mobility - Part 2: First steps towards a holistic mobility strategy" IBRS, 2012-03-29 00:00:00

"Coping with mobility - part 4: governance" IBRS, 2012-05-31 00:00:00

"Coping with mobility - part 5: developing the strategy" IBRS, 2012-10-28 00:00:00

"Coping with mobility Part 6: Work context" IBRS, 2013-06-26 00:00:00

As discussed in this month’s research note “Microsoft Licensing + Virtualisation = Licensing Confusion” Microsoft’s Licensing model is based on a physical machine model that is increasingly out of touch with the IT industry.

In the past, when computers did not have the processing power of today’s hardware and operating systems, and software was bound to the physical machine, binding licensing to the physical machine made absolute sense. When organisations wanted to get more computing power, they would buy more machines: which would see Microsoft getting more revenue. Consumption of software (arguably the value of IT in the eyes of users) was closely correlated to the physical machine.


Read more


Conclusion: IBRS has observed that many organisations struggle with mobility, implementing fragmented mobility solutions that service narrow areas of the business. This leads to higher complexity and costs, and lower levels of user satisfaction. Instead, organisations should take time to build a holistic mobility strategy, driven and grounded by use-cases, and shaped by a concise set of use-case categories.


Read more


Related Articles:

"Coping with Mobility - Part 3: aligning generic use cases to application development approaches" IBRS, 2012-04-30 00:00:00

"Coping with Mobility - part 1: mobile architecture and the enterprise" IBRS, 2012-02-28 00:00:00

"Coping with mobility - part 4: governance" IBRS, 2012-05-31 00:00:00

"Coping with mobility - part 5: developing the strategy" IBRS, 2012-10-28 00:00:00

"Coping with mobility Part 6: Work context" IBRS, 2013-06-26 00:00:00

Conclusion: Organisations looking to develop and deploy mobile applications must realise that the mobile device market will undergo significant change over the next five years. This creates serious challenges for developers within enterprises, who must either create applications for specific devices and different form factors, or attempt to develop cross-platform applications that will still meet end-user expectations. IBRS has identified four high-level architectures for developing mobile applications, each of which has specific strengths and weaknesses. This research provides an overview of these architectures.


Read more


Related Articles:

"Coping with Mobility - Part 3: aligning generic use cases to application development approaches" IBRS, 2012-04-30 00:00:00

"Coping with Mobility - Part 2: First steps towards a holistic mobility strategy" IBRS, 2012-03-29 00:00:00

"Coping with mobility - part 4: governance" IBRS, 2012-05-31 00:00:00

"Coping with mobility - part 5: developing the strategy" IBRS, 2012-10-28 00:00:00

"Coping with mobility Part 6: Work context" IBRS, 2013-06-26 00:00:00

Conclusion: A common mistake when engaging third-parties for ‘Agile software development services’ is to use a contract or procurement approach that is at odds with the tenets of Agile software development. In cases where contract and payment terms follow the more traditional ‘fixed price and scope’ statements of work, organisations do not get true Agile development services, and more likely than not, will be frustrated and dissatisfied with results of the project. Instead, organisations should consider using specific styles of Master Service contracting agreements with Agile developers, or accept that the best than can be achieved will be a hybrid “Watergility” approach by the developers.


Read more


Conclusion: Organisations that are still running Windows XP fleets are debating holding off a desktop refresh (to Windows 7) until Windows 8 becomes available. There are three key considerations to this discussion: product functionality, management, and licensing. In each of these three categories, IBRS concludes that there is no compelling reason to wait for Windows 8.


Read more


Conclusion: IT executives are increasingly being pressured to adopt Windows 64-bit operating systems as a foundation for the next generation of desktop environment. Vendors – and in many cases IT engineers – are touting a range of technical benefits of Windows 64-bit operating systems over 32-bit operating systems. However, these technical benefits do not equate to business benefits.

Unfortunately, market movements and vendor strategies will force enterprises to adopt Windows 64-bit desktops sometime in the next two desktop refresh cycles. As such, the move to a Windows 64-bit environment should be viewed as conceding to market pressures and adopted only within the context of moving to a new Dynamic Desktop architecture, which is where the real business benefits are to be found.


Read more


Conclusion: SharePoint is well known as a platform for small-scale knowledge management, team collaboration, and Web applications. However, some organisations have begun experimenting with SharePoint as an alternative to large-scale Enterprise Content Management (ECM) solutions, handling more than 100 million documents. The lessons learned from these initiatives indicate that while SharePoint can deliver ECM, such projects require a great many technical and planning skills that are foreign to most SharePoint implementation teams in Australia. It is almost certain you will need to hire short-term project specialists to be successful.


Read more


Conclusion: With the recent announcement regarding availability of Microsoft Windows 8, desktop managers are once again finding themselves with the challenge of building a business case for a desktop refresh. However, IBRS proposes that operating system upgrades should no longer be the centrepiece of the desktop refresh process. It is time to radically change how desktop refresh decisions are made. Instead, organisations should be creating an applications deployment strategy that looks not at devices and operating systems, but at ways in which to get the right applications in the right hands, no matter the device or OS.


Read more


This month Microsoft unveiled aspects of its new Windows 8 operating system at the Build developers’ conference. A significant change in the new OS is the use of the “Metro” style user interface, which will be familiar to anyone who has used Windows Phone 7. Metro involves extensive use of multi-touch and “tiles” that represent both applications and live data, instead of icons and menus. The Metro user interface metaphor is arguably one of the most creative and context aware on the market, and is well suited for mobile devices and tablets. However, will Microsoft be able to bring this new User Interface to the traditional desktop space? To answer this question, we need examine three issues.


Read more


Conclusion: Mature Unified Communications (MUC) is more than a blending of messaging, voice, and presence information. The coming wave of unified communications will be executed as part of a larger ’worker mobility’ strategy and be more closely coupled with business processes. This type of unified communications allows significant organisational structural change. Thus, planning for MUC begins with an examination of organisational processes and discovery of where knowledge is located within the organisation, and then evolves into a discussion regarding how to restructure teams to gain a competitive advantage.


Read more


Conclusion: Market and technological forces are minimising the value of the Microsoft Office client, and pushing the true value proposition for productivity services to backend services. Microsoft’s evolving product, marketing and licensing strategies to support this trend. Understanding Microsoft’s strategy is important when planning future desktop deployments, as well as collaboration and mobility strategies.


Read more


Conclusion: Google’s recent announcement that it was depreciating its Translation APIs (application program interfaces) with minimal notice sent shock waves through the world of translation services and developers of mobile, consumer and even enterprise software. After the initial announcement, Google changed its position and stated API services would be offered on a pay-per-use basis. Google’s moves highlights risks associated with public APIs that are provided under ‘terms of use’ rather than firm contractual agreements. As cloud services evolve, the use of free API services allow vendors to effectively hold enterprises and developers to ransom. Organisations must consider carefully the risks of free APIs, and create risk mitigation strategies while still reaping the considerable benefits these services deliver.


Read more