
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Self Service Testing</title>
<link>https://itsmfuk.site-ym.com/forums/posts.aspx?topic=1632352</link>
<description></description>
<lastBuildDate>Sat, 6 Jun 2026 23:57:35 GMT</lastBuildDate>
<pubDate>Wed, 22 Sep 2021 08:24:42 GMT</pubDate>
<copyright>Copyright &#xA9; 2021 itSMF UK</copyright>
<atom:link href="https://itsmfuk.site-ym.com/forums/topic_rss.asp?id=1632352" rel="self" type="application/rss+xml"></atom:link>
<item>
<title>Self Service Testing</title>
<link>https://itsmfuk.site-ym.com/forums/posts.aspx?topic=1632352</link>
<guid>https://itsmfuk.site-ym.com/forums/posts.aspx?topic=1632352</guid>
<description><![CDATA[<p>We have a strategy for the increased use of self service on our newly implemented cloud based service management system to improve response times, reduce cost etc.</p><p>Being cloud based the system is updated, automatically, on a quarterly basis and as a result a testing programme is being developed for the processes, services for functionality and performance.&nbsp;</p><p>We recognise that the self service area has not been addressed yet and is now our focus.</p><p>Are other organisations doing this (test approaches), specifically for self service for 'look n feel', functionality, performance etc?</p><p>If so is that something which could be shared?</p><p>Any thoughts, advice, pointers, methodologies would be very much appreciated.</p><p>Many Thanks</p><p>&nbsp;</p><p>Mark</p><p>&nbsp;</p>]]></description>
<pubDate>Wed, 15 Sep 2021 10:13:33 GMT</pubDate>
</item>
<item>
<title></title>
<link>https://itsmfuk.site-ym.com/forums/posts.aspx?topic=1633254</link>
<guid>https://itsmfuk.site-ym.com/forums/posts.aspx?topic=1633254</guid>
<description><![CDATA[Hi Mark, interesting question re self service testing.  Most places I have worked do the initial design of the self service portal, do basic testing and user interface testing and then never repeat it when updates are done as their argument is Users were happy with it initially and we have not really changed that much, however, how often do you get a UI update on your phone that you hate :-).<br /><br />I am sure there are a number of UX designers out there that may have a different opinion especially in the area of .gov websites but again how often they return to review / retest the interfaces I could not say.  I know the .gov.uk website have service design manuals and guidance documents as well as a blog but whether they cover what you are asking I do not know.  Failing that there are other social media platforms  where you could ask this question or we could consider having the topic of cloud based service testing as an itSMF  Management of Service Community of Practice future meeting user self service portal testing could then be raised as one of the questions.  Further details of the Communities can be found on this website under forums.]]></description>
<pubDate>Tue, 21 Sep 2021 14:20:51 GMT</pubDate>
</item>
<item>
<title></title>
<link>https://itsmfuk.site-ym.com/forums/posts.aspx?topic=1633410</link>
<guid>https://itsmfuk.site-ym.com/forums/posts.aspx?topic=1633410</guid>
<description><![CDATA[Hi Richard, thanks for your thoughts on this. As you have done in the past we did do an amount of initial testing as we moved from one ITSM (on premise) to another (cloud based) with major improvements. So from that aspect we were very successful.<br />However the issue is the now continuous updates (which again is good) and we either accept that all will be well or we do an element of basic testing to re-assure ourselves. I prefer the basic testing approach and I will take your advice and have a look at the guidance on the .gov site to see if there is something there we could use.<br />I think this area (self-service) is more concerned with a 'media approach' rather than coming at it from a traditional ITSM 'processy' angle.<br /><br />Many thanks for your advice Richard<br /><br />Mark]]></description>
<pubDate>Wed, 22 Sep 2021 09:24:42 GMT</pubDate>
</item>
</channel>
</rss>
