0
Completed

Identify supported systems

Oscar Ferne 1 year ago in Framework • updated by Matthew Davis 1 month ago 7

We must identify what systems we will configure alerts/dashboards to work with. Adding systems will require custom scripts, new queries and new reporting graphics. A base stack of configurable systems can be offered that can be modified to fit individual clients needs. Any new proposal for a system must be considered in terms of its re-usability unless its development can be funded directly by a client.

Service Delivery

Answer

Answer
Planned

Thanks for the suggestion, Oscar. This will be addressed when we create documentation for the product, as per Functional description and documentation.

Under review

That depends on what the scope is.  We want to avoid customisation as much as possible - rather make things configuration driven.

Customisation in this sense refers to building out new capabilities within scope. After their development they become configurable items available for resale. And example is Tafe who we actively build reporting for as part of their managed service. Items such as Ping Federation logging that we have built can now be on sold to clients who also use Ping

Yes, at what point is that considered "product"? What characteristics about a feature are required to make it a product feature, as opposed to a customisation

It would become a feature when the scripts, queries and reporting graphics are developed. A customisation would refer to building or altering the latter two items where a client may request a new view or insight on the data. This would stray from the feature offering of a pre-designed dashboard for system that's configurable in a clients purchase of the product.

At a high level, a system acts as a feature that's configurable when it provides data visualisation to the end user.

I'm thinking that's too early to call it a product feature - it's nice to have developed them, but it also needs some way of low-touch deploying them.  We'll see what comes out that - likely to be a trade off between labour costs of manually doing it and automation costs

Answer
Planned

Thanks for the suggestion, Oscar. This will be addressed when we create documentation for the product, as per Functional description and documentation.