6 Steps To a Successful Web Design & Mobile App Development Project

Google Figures it out with Google Drive Storage
June 3, 2013
A day in the life of a Web Designer
June 10, 2013
Show all

6 Steps To a Successful Web Design & Mobile App Development Project

I’ve always been intrigued by the Agile methodology and its effectiveness. Unfortunately this process has never appealed to the creative types very much because it seems so technical of a process, but it really isn’t, and I can dig it.

The Agile Methodology is actually a Godsend for any who deals with clients at any level especially in todays design and development market for Web sites & Mobile Apps.

The process really focuses on documentation, prioritization, flexibility and effectiveness, not to mention time saving and higher profitability. It’s been try, tested and proven, and we at brandhorse Creative Agency are now proud to be part of the elite group of companies who adhere to this method.

Here is a breakdown of our Design infused Agile methodology for a successful Web Design and Mobile App Design & Development project.

  1. Gathering Requirements
    1. Collect Section requirements
    2. Gather features
    3. Organize into a backlog
  2. Scenario Break Down
    1. Identify every section of the product
    2. Identify every feature in each section
  3. Scenario Estimation
    1. Estimate effort for each Scenario using a point system
      1. 1 point   = Easy
      2. 2 points = Medium
      3. 4 points = Hard
      4. 8 points = So big / needs to be broken down more
  4. Prioritization
    1. Prioritize each scenario into order of importance in the backlog
    2. Top of backlog gets worked on first
  5. Design/Build Software
    1. Designers/Developers work on Scenarios in order
      1. Design/Developer Environment
        1. Start Design/Writing Code
        2. Finish Design/Writing code
      2. Staging Environment
        1. Deliver for review/testing
      3. Production Environment
        1. Push to developer/user
        2. Only AFTER acceptance
  • Acceptance
    1. Product Owner/Client
      1. Verify features Using Mouse & Keyboard
      2. Verify it does what the Scenario specifies
      3. Accept or Reject
        1. If accepted Scenario is closed
        2. If rejected Scenario returns to the top of the backlog