<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Kershen Naidoo on Medium]]></title>
        <description><![CDATA[Stories by Kershen Naidoo on Medium]]></description>
        <link>https://medium.com/@knaidoo?source=rss-b41840db2727------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*oei79cerKOGE4k62.jpg</url>
            <title>Stories by Kershen Naidoo on Medium</title>
            <link>https://medium.com/@knaidoo?source=rss-b41840db2727------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 12:11:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@knaidoo/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What is crucial for a cutting-edge e-commerce platform to be successful?]]></title>
            <link>https://medium.com/@knaidoo/what-is-crucial-for-a-cutting-edge-e-commerce-platform-to-be-successful-ed40cc73f4ee?source=rss-b41840db2727------2</link>
            <guid isPermaLink="false">https://medium.com/p/ed40cc73f4ee</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[scrum-agile]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Kershen Naidoo]]></dc:creator>
            <pubDate>Wed, 17 Apr 2019 11:12:01 GMT</pubDate>
            <atom:updated>2019-04-17T11:12:01.907Z</atom:updated>
            <content:encoded><![CDATA[<p>Many e-commerce projects already have well-defined assumptions and requirements at the start. They are based on market-proven patterns of end users’ activities, e.g. online stores. This complete definition allows project startup to design the entire e-commerce platform as well as create a comprehensive user interface by the CX (Customer Experience) team. The design of this interface is usually a series of mock-ups (often interactive) showing the mutual behavior of the system elements as well as guidelines for programming teams how to “dress” these elements.</p><p>What to do, however, when at the start of the project does not have a list of requirements that are “carved in stone”? What if we create a different platform, the one whose operating pattern is not entirely known?</p><p>Let’s imagine this situation: the overall high-level goals are known. We know that we need an e-commerce platform, but we do not know our customers’ behavior yet and do not know how it works with this tool. A good example would be to create an e-commerce platform in the B2B model for this group of partners who never used this kind of tool before.</p><p>One of the models for solving this challenge is to create a list of requirements iteratively so that small parts of the system are created on each other while supporting the overall goal of the project. These small parts of the system must be runnable and well-tuned so that you can show them to the final customer. Only after communication with the customer will you see how to design the next elements of the system.</p><p>Unfortunately, such a step-by-step approach makes it impossible to perform a coherent project of user interfaces before starting the process of creating the system (up-front). However, you can convert this difficulty into the strong point of the project. How? By including a small group of Customer Experience experts in the project team.</p><p>Contemporary project teams are often multidisciplinary, and they consist of analyst, F/E developers, B/E developers, and testers. The project is implemented in AGILE methodology with Scrum or Kanban elements. Including Customer Experience specialists in such a project team is a better solution but it requires some changes in the creation process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dWMSkrIsLdGSrPo6" /></figure><p>The standard path of software development is slightly changing. It includes defined requirements, analysis, decomposition and processing into user stories, implementation of these stories and implementation of tests for the code, internal tests of the entire requirements and acceptance tests of the entire client’s requirements.</p><p><strong>What should be changed?</strong></p><p>In the path, the analytic process is divided into two streams that are happening simultaneously:</p><ul><li>a stream of standard requirements analysis,</li><li>a stream of analysis and design of user interfaces.</li></ul><p>The result of this change is to enrich each user’s history with information about how it is reflected in the interface. This information is created in the form of a mock-up (often interactive) showing what the designed system elements look like and the basic interaction with them. This mockup is tense with the user’s history and its actual use is entered in the “definition of done”.</p><p>The main benefit of including the Customer Experience specialists in the project team is a quick verification of whether the result of the implementation is consistent with the assumptions. This verification takes place daily, which makes it possible to iterate within a given sprint quickly. Very often processes that already seemed almost finished returns to the drawing board and is modified so that at the end of the sprint you give to the customer in a shape that works appropriately and smoothly in the end user’s sense.</p><p>Last but not least is the essential benefit of including Customer Experience specialists in the project team is to create their User Experience standards for the entire system. At the end of the project, these upgraded and cohesive standards are complete and 100% current at each iteration. Thanks to these standards, the system becomes coherent not only at the stage of its implementation but also maintains this consistency during long-term maintenance and development.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ed40cc73f4ee" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>