{"id":230,"date":"2010-12-27T10:45:00","date_gmt":"2010-12-27T18:45:00","guid":{"rendered":"http:\/\/35.225.155.113\/blog\/index.php\/2010\/12\/27\/web_development_before_and_after_the_client\/"},"modified":"2019-10-13T12:52:59","modified_gmt":"2019-10-13T19:52:59","slug":"web-development-before-and-after-the-client","status":"publish","type":"post","link":"https:\/\/www.weinstein.org\/blog\/index.php\/2010\/12\/web-development-before-and-after-the-client.html","title":{"rendered":"Web Development: Before and After the Client"},"content":{"rendered":"

First published: 17th of Dec 2010<\/a> for Orbit Media Studios<\/a><\/p>\n

For someone looking for a web design firm,<\/a> how a website is developed might seem meaningless. Who cares, so long as it works?<\/p>\n

Yet how well a website works can be measured in part by the costs associated with it. The direct cost is the total price for the initial project. The indirect costs consist of secondary expenses related to ongoing marketing and support during the lifetime of the website.<\/p>\n

At Orbit we have two development processes. Both are designed to reduce costs and improve quality. The first is an internal process that starts before the client ever arrives. The second process begins at the first client meeting as we discover the project’s specific requirements.<\/p>\n

Internal Development<\/strong><\/p>\n

First, what do we mean by develop? Development usually refers to the programming of the website, whereas design refers to the look and feel.<\/p>\n

With development, we need to consider a few basic questions. What features are required to make an ecommerce website work, for example? Regardless of the item being sold or the company selling the item, the basic logic can be described in a few steps:<\/p>\n

    \n
  1. A customer selects an item to purchase<\/li>\n
  2. The selected item is placed into a shopping cart<\/li>\n
  3. The customer decides to checkout, continue shopping or abandon their cart<\/li>\n
  4. To checkout, the customer initiates the process of purchasing what is in their cart<\/li>\n
  5. The store presents a total bill for the item(s) desired by the customer<\/li>\n
  6. The customer presents a method of payment<\/li>\n
  7. The payment is verified and the transaction is completed<\/li>\n<\/ol>\n

    To be sure, this purchasing feature isn’t complete and plenty of questions can remain. However, this generalized logic provides a starting point.<\/p>\n

    This is where web development at Orbit begins, identifying basic features of a potential website.<\/p>\n

    Developer Day<\/strong><\/p>\n

    Roughly once a month, all of Orbit’s developers spend the day working on such questions, analyzing and programing with various sandboxes.<\/p>\n

    A sandbox is simply a generic website in which the development team can create, test and improve different features and find the best approach for virtually any type of website. It’s a play area for programmers.<\/p>\n

    The focus is on breaking down the feature into workable steps and rapidly building them. In doing so we consider what has worked for clients in the past along with growing trends such as social media integration.<\/p>\n

    Each Developer Day represents the repeating of a cycle of planning, analyzing, coding and acceptance testing in order to get the feature built right.<\/p>\n

    But, as we mentioned, plenty of questions can remain. Not all features will work perfectly “out of the box” for all clients.<\/p>\n

    Developing with the Client<\/strong><\/p>\n

    This brings us to the second process of web development at Orbit: developing with the client. Now the concern is on completion of a particular website. Thus the focus for the developer changes from generalized concepts to specific implementation.<\/p>\n

    But before a developer can customize the code for a client, a new process of discovery and planning must begin. The phases of this process break down into the following, with direct client involvement at each step:<\/p>\n

      \n
    1. A Kick-Off Meeting where initial questions about goals and scope are answered<\/li>\n
    2. Discovery of the layout and flow for the proposed website<\/li>\n
    3. Designing the look of the website and expressing the client’s brand<\/li>\n
    4. Development, implementing and testing<\/li>\n
    5. Deploing the website for public use<\/li>\n<\/ol>\n

      In this sequential development process each step follows from the last. There is a specific beginning and ending. One step cannot be started until the previous step is completed and approved.<\/p>\n

      The Big Payoff<\/strong><\/p>\n

      Understanding the development process for a custom website is important. How many hours a developer works on a client’s website and the dependability of the underlying code affects its ultimate cost.<\/p>\n

      Both direct and indirect costs impact the client’s ability to market their website and can limit the overall return of the website.<\/p>\n

      Rather than starting from scratch, Orbit takes the pieces we have built and improved earlier and applies them to the client’s project, customizing the features to the needs of the website. In doing so we execute different development processes in order to keep our client’s costs manageable while adding value to their business.<\/p>\n","protected":false},"excerpt":{"rendered":"

      First published: 17th of Dec 2010 for Orbit Media Studios For someone looking for a web design firm, how a website is developed might seem meaningless. Who cares, so long as it works? Yet how well a website works can be measured in part by the costs associated with it. The direct cost is the […]<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[92,82],"tags":[205,314,43,315],"_links":{"self":[{"href":"https:\/\/www.weinstein.org\/blog\/index.php\/wp-json\/wp\/v2\/posts\/230"}],"collection":[{"href":"https:\/\/www.weinstein.org\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.weinstein.org\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.weinstein.org\/blog\/index.php\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.weinstein.org\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=230"}],"version-history":[{"count":2,"href":"https:\/\/www.weinstein.org\/blog\/index.php\/wp-json\/wp\/v2\/posts\/230\/revisions"}],"predecessor-version":[{"id":709,"href":"https:\/\/www.weinstein.org\/blog\/index.php\/wp-json\/wp\/v2\/posts\/230\/revisions\/709"}],"wp:attachment":[{"href":"https:\/\/www.weinstein.org\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=230"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.weinstein.org\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=230"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.weinstein.org\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=230"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}