{"action":"created","issue":{"url":"https://api.github.com/repos/sahilsk/reading-list/issues/45","repository_url":"https://api.github.com/repos/sahilsk/reading-list","labels_url":"https://api.github.com/repos/sahilsk/reading-list/issues/45/labels{/name}","comments_url":"https://api.github.com/repos/sahilsk/reading-list/issues/45/comments","events_url":"https://api.github.com/repos/sahilsk/reading-list/issues/45/events","html_url":"https://github.com/sahilsk/reading-list/issues/45","id":180570997,"number":45,"title":"RT @InfoQ: Continuous delivery is happening in many government agencies including HMRC. https://t.co/3pdRL4IMQq https://t.co/DprgCLYWba","user":{"login":"sahilsk","id":5857895,"avatar_url":"https://avatars.githubusercontent.com/u/5857895?v=3","gravatar_id":"","url":"https://api.github.com/users/sahilsk","html_url":"https://github.com/sahilsk","followers_url":"https://api.github.com/users/sahilsk/followers","following_url":"https://api.github.com/users/sahilsk/following{/other_user}","gists_url":"https://api.github.com/users/sahilsk/gists{/gist_id}","starred_url":"https://api.github.com/users/sahilsk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sahilsk/subscriptions","organizations_url":"https://api.github.com/users/sahilsk/orgs","repos_url":"https://api.github.com/users/sahilsk/repos","events_url":"https://api.github.com/users/sahilsk/events{/privacy}","received_events_url":"https://api.github.com/users/sahilsk/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-10-03T06:27:09Z","updated_at":"2016-10-09T17:52:59Z","closed_at":"2016-10-09T17:52:59Z","body":"<blockquote class=\"twitter-tweet\">\n<p lang=\"en\" dir=\"ltr\" xml:lang=\"en\">Continuous delivery is happening in many government agencies, including HMRC. <a href=\"https://t.co/3pdRL4IMQq\">https://t.co/3pdRL4IMQq</a> <a href=\"https://t.co/DprgCLYWba\">http://pic.twitter.com/DprgCLYWba</a></p>\n&mdash; InfoQ (@InfoQ) <a href=\"https://twitter.com/InfoQ/status/782681823868358656\">October 2, 2016</a>\n</blockquote>\n\n<br><br>\nOctober 03, 2016 at 11:53AM<br>\nvia Twitter"},"comment":{"url":"https://api.github.com/repos/sahilsk/reading-list/issues/comments/252501268","html_url":"https://github.com/sahilsk/reading-list/issues/45#issuecomment-252501268","issue_url":"https://api.github.com/repos/sahilsk/reading-list/issues/45","id":252501268,"user":{"login":"sahilsk","id":5857895,"avatar_url":"https://avatars.githubusercontent.com/u/5857895?v=3","gravatar_id":"","url":"https://api.github.com/users/sahilsk","html_url":"https://github.com/sahilsk","followers_url":"https://api.github.com/users/sahilsk/followers","following_url":"https://api.github.com/users/sahilsk/following{/other_user}","gists_url":"https://api.github.com/users/sahilsk/gists{/gist_id}","starred_url":"https://api.github.com/users/sahilsk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sahilsk/subscriptions","organizations_url":"https://api.github.com/users/sahilsk/orgs","repos_url":"https://api.github.com/users/sahilsk/repos","events_url":"https://api.github.com/users/sahilsk/events{/privacy}","received_events_url":"https://api.github.com/users/sahilsk/received_events","type":"User","site_admin":false},"created_at":"2016-10-09T17:52:59Z","updated_at":"2016-10-09T17:52:59Z","body":"![image](https://cloud.githubusercontent.com/assets/5857895/19222479/0abb95ca-8e77-11e6-8927-484261ff382c.png)\r\n\r\n\r\n\r\n\r\nUK Digital Service Standard\r\n---------\r\n\r\nThe Digital Service Standard is a set of 18 criteria to help government create and run good digital services.\r\n\r\nAll public facing transactional services must meet the standard. It’s used by departments and the Government Digital Service to check whether a service is good enough for public use.\r\n\r\n1. Understand user needs\r\n\r\nUnderstand user needs. Research to develop a deep knowledge of who the service users are and what that means for the design of the service.\r\n\r\nRead more about point 1\r\n\r\n2. Do ongoing user research\r\n\r\nPut a plan in place for ongoing user research and usability testing to continuously seek feedback from users to improve the service.\r\n\r\nRead more about point 2\r\n\r\n3. Have a multidisciplinary team\r\n\r\nPut in place a sustainable multidisciplinary team that can design, build and operate the service, led by a suitably skilled and senior service manager with decision-making responsibility.\r\n\r\nRead more about point 3\r\n\r\n4. Use agile methods\r\n\r\nBuild your service using the agile, iterative and user-centred methods set out in the manual.\r\n\r\nRead more about point 4\r\n\r\n5. Iterate and improve frequently\r\n\r\nBuild a service that can be iterated and improved on a frequent basis and make sure that you have the capacity, resources and technical flexibility to do so.\r\n\r\nRead more about point 5\r\n\r\n6. Evaluate tools and systems\r\n\r\nEvaluate what tools and systems will be used to build, host, operate and measure the service, and how to procure them.\r\n\r\nRead more about point 6\r\n\r\n7. Understand security and privacy issues\r\n\r\nEvaluate what user data and information the digital service will be providing or storing and address the security level, legal responsibilities, privacy issues and risks associated with the service (consulting with experts where appropriate).\r\n\r\nRead more about point 7\r\n\r\n8. Make all new source code open\r\n\r\nMake all new source code open and reusable, and publish it under appropriate licences (or provide a convincing explanation as to why this can't be done for specific subsets of the source code).\r\n\r\nRead more about point 8\r\n\r\n9. Use open standards and common platforms\r\n\r\nUse open standards and common government platforms where available.\r\n\r\nRead more about point 9\r\n\r\n10. Test the end-to-end service\r\n\r\nBe able to test the end-to-end service in an environment identical to that of the live version, including on all common browsers and devices, and using dummy accounts and a representative sample of users.\r\n\r\nRead more about point 10\r\n\r\n11. Make a plan for being offline\r\n\r\nMake a plan for the event of the digital service being taken temporarily offline.\r\n\r\nRead more about point 11\r\n\r\n12. Make sure users succeed first time\r\n\r\nCreate a service which is simple to use and intuitive enough that users succeed the first time.\r\n\r\nRead more about point 12\r\n\r\n13. Make the user experience consistent with GOV.UK\r\n\r\nBuild a service consistent with the user experience of the rest of GOV.UK including using the design patterns and style guide.\r\n\r\nRead more about point 13\r\n\r\n14. Encourage everyone to use the digital service\r\n\r\nEncourage all users to use the digital service (with assisted digital support if required) alongside an appropriate plan to phase out non-digital channels and services.\r\n\r\nRead more about point 14\r\n\r\n15. Collect performance data\r\n\r\nUse tools for analysis that collect performance data. Use this data to analyse the success of the service and to translate this into features and tasks for the next phase of development.\r\n\r\nRead more about point 15\r\n\r\n16. Identify performance indicators\r\n\r\nIdentify performance indicators for the service, including the 4 mandatory key performance indicators (KPIs) defined in the manual. Establish a benchmark for each metric and make a plan to enable improvements.\r\n\r\nRead more about point 16\r\n\r\n17. Report performance data on the Performance Platform\r\n\r\nWhy you should report data and how you'll be assessed.\r\n\r\nRead more about point 17\r\n\r\n18. Test with the minister\r\n\r\nTest the service from beginning to end with the minister responsible for it.\r\n\r\nRead more about point 18\r\n\r\n"}}
{"actor":{"display_login":"sahilsk"}}