A Proof of Concept (PoC) is a crucial step when evaluating new technology. In addition to testing a vendor’s core capabilities, a PoC is an opportunity to confirm the system’s functionality, efficiency, and compatibility with unique business requirements. In previous articles, we’ve discussed the importance of a well-defined PoC scope and documenting the results. InRead Full Article
In the current technology landscape, where successful digital transformation leads to more efficient operations, the choice of vendor can often be the defining factor between success and failure. “Implementation Handbook: Capturing PoC Insights for Future Implementation” emphasizes the importance of thoroughly documenting each facet of a vendor Proof of Concept (PoC) facet to assist with analyzing findings and provide a comprehensive and organization-specific guide for implementation. This guide will increase a firm’s odds of successful implementation.
by Nicol O’ConnorRead Full Article
Entering a large-scale transformation project can be a daunting task. But does it need to be? What separates a successful project from one that is fraught with delays and cost overruns? While the execution of any large-scale implementation project is critical, equally so is the planning phase. It is here, during planning, before the vendor even lands in your office, that the foundation of a successful project is formed. Consider the following three principles as keys to your success.
by Christopher Dyer, ManagerRead Full Article
The most effective system implementations start by running a Proof of Concept (PoC) to validate a vendor’s ability to support your requirements and highlight areas where custom solution design may be required. A key component of a successful PoC is a clearly defined scope that identifies the types of scenarios, goals, and criteria for completion. Yet we see time and time again firms overlook this element.
by Nicol O’Connor, ManagerRead Full Article
The most effective system implementations start by establishing a proof of concept (POC) to validate a vendor’s ability to support your requirements and highlight areas where custom solution design may be required. A key component of a successful POC is a clearly defined scope that identifies the types of scenarios, number of portfolios, goals and criteria for completion. Yet we see time and time again firms overlook this element. Here are four key steps to establish a thoughtful POC scope that will allow your implementation to go off without a hitch.
by Nicol S. O’Connor, Senior ConsultantRead Full Article
Picture this: The monthly performance report has just been received, but it’s missing some data. No errors were generated, yet the blank section on the output indicates something went wrong. The analyst sends a message to IT to report the error, and this starts the Easter egg hunt for the issue.
How many times has this happened to you or your colleagues? Whether you rely on a large single vendor, multi-purpose platform or multiple integrated systems, I’d be willing to speculate it’s a common occurrence. Beyond tracking down today’s Easter egg, how can we avoid the problem in the future or remedy our existing platforms?
by Christopher D. Sadala, Senior ConsultantRead Full Article
The two main approaches to project management, Waterfall and Agile, are often viewed as mutually exclusive. Though it’s true they may have little reusable overlap, each is helpful in setting expectations and tracking iterative development and nuanced progress updates. But what happens when you are managing an Agile team and the executive committee wants Waterfall-style reporting? Let’s explore how to unite the teams that work and view progress differently.
by Elizabeth M. Colebrooke, Principal…Read Full Article
Technology transformation projects are inherently challenging – from determining how a specific firm compiles their data and technology, to innumerable decisions to be made, data files to validate, functionality to configure and test, to go-live events. When technology transformation projects impact front office teams, a highly specialized project management approach must be employed to minimize disruptions to uber time-sensitive front office revenue-generating productivity while keeping the project on schedule.
While the definition of ‘front office’ differs among organizations, here within the front office references a few distinct groups: Portfolio Management, Trading, Quantitative Analysts and Risk Managers. These front office groups fulfill critical roles involving time-sensitive initiatives. They represent investment management firms’ strategy and intellectual capital, and directly generate revenue for investment management firms. Their skills are the costliest; therefore, their time is at a premium. This paper shares the keys to executing this specialized, non-disruptive approach to managing front office technology transformation projects.
by Elizabeth M. Colebrooke, PrincipalRead Full Article