Biomedical Engineering Reference
In-Depth Information
What are the shortcomings of the solution/capability? What adoption
patterns do we observe?, etc. In order to answer these questions we
needed to perform safe-fail experiments, that is small-scale deployments
that do not build critical business dependencies on the capability.
This was a more detailed exploration of the capability than the previous
research phase but still did not involve signifi cant development or
modifi cation of the chosen software. However, it was recognised very
early on that LDAP integration, that is enabling users to use their
corporate Windows network ID and password, was critical for getting
adoption beyond members of the alpha testing community. In practice,
this modifi cation was generally very simple and had the added benefi t
that it signifi cantly simplifi ed the effort associated with migrating and
merging user's content between test instances. Further, a consistent user
ID across tools later allowed us to experiment with lightweight
integration/cross surfacing of content between tools without the
complexity of mapping user accounts, that is creating activity streams.
The data generated in this phase are used to build the business case for
funding of a production capability and the requirements that service
needs to meet. The purpose is not to promote the solution used during
this phase but to enable an accurate assessment of the capability.
13.2.4 Proof of Concept phase use-cases:
microblogging and social bookmarking
Pfollow - microblogging
Having identifi ed Status.net as our solution for exploring microblogging
(see previous section), the fi nal step was to obtain the Pfollow internal
domain name. At this point the new service was advertised to prospective
users via existing social media and emails to relevant networks within the
company. These users were invited to take part, but were made aware of
the experimental nature of the software through a set of terms and
conditions related to its use. The primarily underlining fact being that
due to the nature of our deployment we needed to reserve the right to
switch Pfollow off at any point once our experiment had reached a logical
conclusion. Consequently, users needed to be made aware that they
should not build business critical dependencies on this service.
The new Pfollow community was fast growing and over a matter of
weeks we started to see both individual contributors making an impact
and a large number of online groups coming into existence. Initial posts
Search WWH ::
Custom Search