{"id":12841,"date":"2023-12-19T11:46:06","date_gmt":"2023-12-19T10:46:06","guid":{"rendered":"https:\/\/www.betterchange-consulting.com\/?p=12841"},"modified":"2024-03-20T16:14:31","modified_gmt":"2024-03-20T15:14:31","slug":"misforstaelser-i-softwarespecifikationer","status":"publish","type":"post","link":"https:\/\/www.betterchange-consulting.com\/da\/product-owner\/miscommunication-in-software-specifications\/","title":{"rendered":"Misforst\u00e5elser i softwarespecifikationer."},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

<\/p>\n

An experience I recently had<\/h3>\n

<\/p>\n

I was waiting online to chat with a service representative. Of course I ended up chatting to a bot for a while which wasn’t very helpful in my case. After a while I was transferred to a real human being. While I was waiting this was my experience in WhatsApp (see image). Waiting time in these messages should have been the time you still have to wait, according to the text. The developer has seemingly implemented it as the time you are already waiting\u2026..<\/span><\/p>\n

That makes for a pretty bad customer experience:<\/p>\n

<\/p>\n

<\/p>\n

    \n
  1. \n
      <\/ol>\n<\/li>\n<\/ol>\n
        \n
      1. \n
          \n
        1. The customer expects to be answered very quickly<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n

          <\/p>\n

          <\/p>\n

            \n
          1. \n
              \n
            1. The customer receives a WhatsApp message every minute<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n

              <\/p>\n

              <\/p>\n

              <\/p>\n

               <\/h3>\n

              Origin of User Stories<\/h3>\n

              <\/p>\n

              In my Product Owner training<\/a> I always emphasize that the job of a Product Owner<\/a> is not to write<\/em> better User Stories<\/a>, but to tell<\/em> better stories from users.<\/span><\/p>\n

              User Stories originated when Kent Beck<\/a>, the founder of eXtreme Programming (XP)<\/a>, received feedback from a user who was so excited to receive new functionality that the idea arose to try to predefine the user’s response. What is the response you hope to get from the user when they are able to use the new functionality?<\/span><\/p>\n

              To make it easier, Ron Jeffries<\/a> has created a template for it. If you work with Agile<\/a> or Scrum<\/a>, you have probably seen it.<\/span><\/p>\n

               <\/p>\n\n

              As a <type of user>
              I want <some function>
              So that <some value><\/code><\/p>\n

              <\/p>\n

              <\/p>\n

               <\/p>\n

              They describe WHO<\/strong>, WHAT<\/strong> and WHY<\/strong> (please note; not HOW<\/strong>).<\/p>\n

              <\/p>\n

              <\/p>\n

               <\/h3>\n

              Misuse of User Stories<\/h3>\n

              <\/p>\n

              <\/p>\n

              The mistake that is often made is that this template is seen as the new way to record requirement specifications. By trying to capture requirements in the template that have no relation to the user at all. For example:<\/p>\n

               <\/p>\n

              <\/p>\n

              <\/p>\n

              As a Developer I want a Database so that I can store my data.
              As a Product Owner I need a report so that I can show it to the CEO.<\/code><\/p>\n

              <\/p>\n

              <\/p>\n

               <\/p>\n

              Entire documents and blocks of text are also attached to items in Jira, TFS, etc.<\/p>\n

              <\/p>\n

              <\/p>\n

              That is not what User Stories are intended for, they are the basis for Social Requirements gathering, or having better conversations with each other about the users and functionality between developers and users. As an alternative to users, you can also use representatives or also called stakeholders for this, but they must really understand and be able to represent the users.<\/p>\n

              <\/p>\n

              <\/p>\n

              As Coach of the first XP team, Ron Jeffries introduced the 3 C’s: Card, Conversation, and Confirmation.<\/p>\n

              <\/p>\n

              <\/p>\n