Optimising webproject flows

Written by Peter Vejrum Terp on . Posted in Peters Blog

At the moment Im started optimising the flow on projects, programming and similar where I work. First you need to know that my job position is “Development specialist”, “Project manager” and daily technical manager for on a travel website.

Well back to where I started –  the case is that we need to improve the quality and the speed of how fast things is done. Therfore I tried to create a list of rules that each of us developers and project managers should follow to make the flow more effective.

When receiving a project / task – before startup 

  1. When receiving a project, walk through the tasks/subtasks of the project and determine if you understand every part of the project. If you don’t then ask the the project manager about the different parts until you fully understand.
  2. Retell about how you have understood the project.
  3. Always review The project when you get it, assess what 20% takes most of the project time and give information to your project manager. It is very likely that the 20% is less important than the value of the hours to make it work.
  4. Create a note or a short list of who(m) can assist you on the project if you have problems.

When recieving a project / task – in action

  1. Create a daily check list with small tasks, and with only 3 must do today tasks. The rest has to be a lower priority. Of course you will do more tasks thant that on a day, but you need to have a focus on the most important things, and the top 3 needs to be done. Each task must not exceed 2 hours – 1 hour is better than 2 hours.
  2. Create a test scheme on how to test the full project, and part of the project.
  3. When you are run into problems you can’t solve or just problems which takes a lot longer to fix than expected, then call for assitance – remember who can help you!

Remember

  1. Many requests on a page = slower page, therefore try to elminate the amount of requests. Meaning that JavaScript and stylesheet needs to be loaded from as few files as possible.
  2. Images which is too large = slower page, therefore insure that all images is in the right size. This is of course the graphic designers job, but it’s better to check – just to be sure. Recommendation is 80% compression for a jpg image.
  3. Spriting of images/icons – check if it’s possible to sprite images and icons in one file. This lower the amount of requests, and can also lower the amount of Kilobytes used for images.

Tags: , ,

Trackback from your site.

Peter Vejrum Terp

My name is Peter Vejrum Terp, I am a travel geek, and tech hippie . I've been working as a professional Internet programmer, project manager and more since 2000. At the moment I work with SEO, and I've been doing it full time the last couple of years. I am cofounder of www.backpackerplanet.dk and www.backpackers-online.dk

Posts from my blog