{"id":2968,"date":"2016-11-15T08:57:42","date_gmt":"2016-11-15T08:57:42","guid":{"rendered":"http:\/\/joapen.com\/blog\/?p=2968"},"modified":"2016-11-15T08:57:42","modified_gmt":"2016-11-15T08:57:42","slug":"poldat-should-be-poldate","status":"publish","type":"post","link":"https:\/\/joapen.com\/blog\/2016\/11\/15\/poldat-should-be-poldate\/","title":{"rendered":"POLDAT should be POLDATE"},"content":{"rendered":"
\n

POLDAT<\/a> contains the basic aspects of a contract, independently of the nature, environment or magnitude.<\/p>\n

It’s an useful tool to enable everybody to work on all aspects of the initiative. For major initiatives, all is included and nobody forgets any of these aspects. For small initiatives, the use of POLDAT as guidance for the definition of an initiative force the person writing it to think about all aspects of the customer needs.<\/p>\n

By this reason and others, I would add “E” from experience to the POLDAT. This will enable to have on the first level of requirements the need to understand the “experience” expected by the user or by any stakeholder. These questions need to be done in the beginning of all these processes. This is key value in the Digital Transformation shift we are working on. And “E” should be always in our minds.<\/p>\n

You probably will argue that “experience” should be defined as part of the “P” process. But to me, right now this is a limitation that does not give the importance of the experience for the customer.<\/p>\n

We should be asking things as:<\/p>\n